What problem does it solve? Keeping a documentation site accurate after code changes is hard: pages drift from behaviour, dead links slip into CI, and Mermaid diagrams or icons silently render broken. This Skill encodes the project's docs conventions so edits to docs/ and mkdocs.yml stay consistent and pass the strict build. ## Core Features & Use Cases - Page authoring and nav wiring: Add a page in docs/, place it in the mkdocs.yml nav at the right position, and cross-link it from CLAUDE.md's topic table. - Rendering pitfall prevention: Covers the three known silent failures — Mermaid needing custom_fences, icons needing pymdownx.emoji, and --strict not validating anchors. - mkdocstrings constraints: Explains that the static collector cannot traverse app/services/, app/api/, or app/worker/ (no init.py), so those must be referenced from prose with source links. - Use Case: After changing how a budget check behaves, update the docstring that generates the API reference, fix the affected prose page, run make docs-build, and verify anchors before CI fails. ## Quick Start Update the docs page describing the feature I just changed, wire any new page into the mkdocs.yml nav, and run make docs-build to confirm the strict build passes.