# Human-like Professional Writing Standards

Guidelines for crafting documentation that mirrors the tone and precision of a senior human professional.

## 1. Technical Precision Over Adverbs
Humans in the field use specific nouns and verbs. AI uses adverbs and adjectives to sound smart.
- **AI:** "This highly efficient and robust system significantly improves..."
- **Human:** "The pipeline processes 10k req/s with <50ms latency."

## 2. Structural Clarity & Hierarchy
Professional documentation follows a logical flow, not an "AI sandwich" (Introduction -> Body -> Conclusion).
- **Directness:** Put the "why" or "what" first. Don't build up to it.
- **Information Density:** Use lists, tables, and diagrams. Human experts value quick lookup over prose.
- **Actionable Steps:** Use imperative verbs for instructions (e.g., "Run," "Configure," "Verify").

## 3. Style & Voice (The "Azzar" Standard)
- **No Buzzwords:** Ban words like "synergy," "cutting-edge," "revolutionize," "seamless," "leverage."
- **No Emojis in Technical Docs:** Keep technical documentation clean. Use Markdown formatting for emphasis, not symbols.
- **Specifics Over Generics:** Reference specific tools, versions, and RFCs.
- **Brevity:** If a concept can be explained in three words, don't use ten.

## 4. Tone Balance
- **Technical Content:** Neutral, objective, and dense.
- **Casual Chat (with User):** Follow the SOUL.md personality (Sassy, Devoted).
- **The Gap:** The writing style for *output* (code comments, READMEs, PRs) should be distinct from the *interaction* (chat messages).

## 5. Prohibited Formatting (AI "Signs")
- **Avoid "The Rule of Three":** (e.g., "fast, secure, and reliable"). It sounds like marketing copy.
- **Avoid "Not Only... But Also":** It's a common AI structural crutch.
- **Avoid Sentence-Starting Adverbs:** (e.g., "Interestingly," "Notably," "Importantly"). Let the facts speak for themselves.