<!-- AUTO-GENERATED FILE - DO NOT EDIT DIRECTLY -->
<!-- Edit source frontmatter, then run 'erk docs sync' to regenerate. -->

# Documentation Documentation

- **[canonical-authority-declarations.md](canonical-authority-declarations.md)** — writing documentation that could conflict with other sources, clarifying which doc is authoritative for a pattern, organizing documentation to prevent duplication
- **[divio-documentation-system.md](divio-documentation-system.md)** — structuring documentation, deciding what type of doc to write, creating tutorials, how-to guides, or reference material, understanding why docs feel disorganized
- **[language-scope-auditing.md](language-scope-auditing.md)** — writing documentation that includes code examples, reviewing learned-docs for verbatim code violations, understanding what code blocks are forbidden in docs/learned/
- **[markdown-and-prettier.md](markdown-and-prettier.md)** — writing or editing markdown documentation, understanding prettier's markdown formatting rules, resolving prettier violations in documentation
- **[passive-context-vs-retrieval.md](passive-context-vs-retrieval.md)** — deciding whether to put knowledge in AGENTS.md or a skill, structuring documentation for agent consumption, designing how agents discover and use project knowledge, evaluating why an agent isn't using available documentation
- **[skill-scope.md](skill-scope.md)** — Creating or modifying skills in .claude/skills/, Deciding where to document a pattern, Reviewing skill content for project-specific leakage
- **[source-pointers.md](source-pointers.md)** — writing or updating documentation with code examples, deciding whether to include a code block in docs, addressing verbatim code violations in PRs
- **[stale-code-blocks-are-silent-bugs.md](stale-code-blocks-are-silent-bugs.md)** — documenting implementation patterns with code examples, deciding whether to include verbatim code in docs, understanding documentation maintenance trade-offs
- **[two-option-template.md](two-option-template.md)** — documenting a decision point with two valid options, writing docs about when to choose between approaches, creating comparison documentation
- **[when-to-switch-pattern.md](when-to-switch-pattern.md)** — deciding whether to plan or start coding, realizing mid-task that you should have planned, choosing between erk wt create and plan mode
