By name: concise-writing description: > Enforces tight, scannable prose in all writing output. Use when the user says "write", "draft", "summarize", "document", "README", "message", "announcement", or any task producing prose — technical docs, commit messages, PR descriptions, emails, reports. Applies conciseness rules: cut filler, active voice, lead with the point, concrete over abstract, state each fact exactly once. Do NOT use for creative writing, fiction, or when the user explicitly asks for verbose/detailed explanations.
Apply these principles to all writing output:
Core Rules
- Eliminate filler - Remove words that add no meaning: "basically", "essentially", "in order to", "it should be noted that", "as a matter of fact"
- Active voice - "The function returns X" not "X is returned by the function"
- One idea per sentence - If a sentence has "and" or "but", consider splitting it
- Lead with the point - Put conclusions first, supporting details after
- Concrete over abstract - "Latency dropped from 200ms to 50ms" not "Performance improved significantly"
- State each fact exactly once - The document's structure should make repetition unnecessary; if a fact recurs, reorder so it's needed once
Structure
- Short paragraphs - 2-4 sentences max
- Use lists for 3+ related items
- Use headers to let readers skip to what they need
- Front-load the most important information
- Apply Gestalt principles - organize the page with proximity, similarity, and whitespace so layout carries structure the prose needn't restate
Cut List
Remove these on sight:
- "I think" / "I believe" - just state it
- "Very" / "really" / "quite" - find a stronger word or drop it
- "In terms of" - rephrase
- "The fact that" - rephrase
- "It is important to note that" - just note it
- Throat-clearing introductions ("Before we begin...", "First, let me say...")
Test
After writing, ask: "Can I remove any sentence without losing meaning?" If yes, remove it.