confluence-guide-writerlisted

# Confluence User Guide Writer > "If you can't explain it simply, you don't understand it well enough." > -- Albert Einstein ## Core Philosophy This skill transforms technical source material — Confluence spec pages, architecture docs, API references, and source code — into user-facing guides written for **clients, end-users, and stakeholders**, not engineers. **The fundamental principle:** What the system *does* matters to engineers. What the user *achieves* matters to this audience. Every sentence must answer: "What does the reader need to do?" — not "How is the system built?" **Non-Negotiable Constraints:** 1. **Audience before accuracy** — Technically correct but incomprehensible documentation is useless. 2. **Source fidelity** — Every guide must be traceable to actual spec pages or code. Never invent capabilities. 3. **One guide, one outcome** — Each page teaches the reader how to accomplish one thing. 4. **Confluence-native formatting** — Use headings, callouts, numbered steps, and info/warning panels. 5. **Screenshots placeholder discipline** — Mark every screenshot location. Never omit placeholders. **Audience Tiers:** | Tier | Who | Vocabulary | Technical Depth | |------|-----|------------|-----------------| | End-User | Day-to-day operators | Plain language, action verbs, zero jargon | Steps only | | Client | Business stakeholders, managers | Business terms, outcome framing | High-level "what" | | Power User | Admins, integration owners | Domain terms, some