What problem does it solve? AI agents and contributors tend to proliferate standing Markdown files (SUMMARY.md, NOTES.md, IMPLEMENTATION.md) that duplicate content, drift out of sync, and bury the real state of a project. This Skill enforces a bounded, canonical documentation set so every fact has exactly one home. ## Core Features & Use Cases - Canonical doc set: Defines exactly four standing documents — PLAN.md (decisions and next steps), LOG.md (prepend-only run/result log), CONTEXT.md (glossary), and README.md (outward-facing snapshot) — each created lazily on first real content. - notes/ vocabulary: Reserves main.html and claims.md as single-owner files and restricts all other notes to a closed prefix set (deriv-, design-, lit-, review-, draft-, probe_*.py), with one-note-per-topic rewrite rules and no dates in filenames. - HTML note template: Ships a theme-aware notes-template.html with MathJax, tables, and callout boxes so working notes render consistently across projects and color schemes. - Use Case: Before an agent writes a new SUMMARY.md after a research run, this Skill redirects the result into a prepend-only LOG.md entry with a pointer to a prefixed note in notes/, keeping the doc inventory bounded. ## Quick Start Before creating or editing any project Markdown file, apply the context-project-docs rules to decide whether the content belongs in PLAN.md, LOG.md, CONTEXT.md, README.md, or a prefixed note under notes/.
