documentation-writinglisted

# Documentation Management Maintain project documentation in `.claude/skills/project-knowledge/references/`. Audit for bloat, edit files, check consistency, track status. ## Documentation Principles These rules apply to ALL documentation operations (audit, edit, create). **Goal: open docs → understand the project without reading code.** Describe what exists, what it does, and why: high-level component overview, decisions made (why this stack, why this architecture), operational details (server addresses, deploy procedures, log locations, env var names). Skip what's obvious from reading the code itself — function signatures, implementation details, generic framework behavior. **No code blocks, no pseudocode.** Link to source files: `[auth.ts:45-67](src/auth/jwt.ts#L45-L67)`. Code in docs gets outdated and bloats context. **No duplication between files.** Information lives in ONE place. Cross-reference: "See deployment.md for env vars." **patterns.md: only project-specific patterns.** Universal coding standards live in `~/.claude/skills/code-writing/references/universal-patterns.md`. Project patterns.md contains only what's unique to THIS project. ## File Structure **4 core files** in `.claude/skills/project-knowledge/references/`: | File | Contains | |------|----------| | project.md | Overview, audience, problem, 3-5 key features, out of scope | | architecture.md | Tech stack (with WHY), project structure, dependencies, integrations, data model | | patterns.md | Proj