Model benchmark
Prompts
- prompt to keep output concise authoring a skill (cursor repo)
Documentation Principles for AI tools
Add it for AGENTS.md, CLAUDE.md, etc.
- Keep it concise
- Use the fewest words that preserve the meaning
- Delete any sentence whose removal does not change the meaning or make the text harder to follow
- When in doubt, delete
- Write for readers who are not native English speakers
- Use direct and unambiguous language
- Avoid idioms and overly poetic expressions
- Use consistent terminology
- Write for the intended audience
- Ask who the audience is if unclear
- Omit information the audience already knows
- Keep only content the reader needs to understand, decide, or act
- Explain a rule only when needed for clarity
- State each point once
- Omit summaries that only repeat earlier content
- Refer to authoritative sources instead of duplicating their content
- Start directly
- Omit sentences that announce what the text will explain
- Remove empty emphasis
- Match the tone of existing documentation
- Use a professional tone if there is none
- Stay within scope
- Omit adjacent advice and unsolicited next steps.
- Use examples selectively
- Add them only to resolve a likely misunderstanding
- Review concision at the section level and then the entire document level
- Prefer a short summary over exhaustive narrative when it preserves the decision, contracts, invariants, and necessary exceptions.
- If a section can be reduced to a few direct bullets without losing meaning, use the shorter form.
- Do not retain a detail only because it is true or relevant to the code.