context-synclisted

# Context Sync Detect and fix documentation role overlaps, stale content, and missing context files across your project. Ensures every piece of project knowledge lives in exactly one place with a clear purpose. ## Why This Matters In LLM-driven development, organizing concepts _is_ implementation. Markdown carries the same weight as executable code — a stale number in CLAUDE.md or a misplaced design rationale silently degrades every AI-assisted session that reads it. Context consistency is not housekeeping; it is a prerequisite for core concepts to reach the system without noise. ## When to Use - After a major refactoring or architecture change - When CLAUDE.md / .cursorrules has grown large and feels cluttered - When you suspect docs are out of date with the code - When starting a new project and want proper doc structure from the beginning - When design decisions are buried in context files instead of formal records - Periodically (monthly or per milestone) as documentation hygiene ## Core Concept: Four Documentation Roles Every project document should serve exactly one of these four roles. Overlap causes drift and contradiction. | Role | Purpose | What belongs here | Examples | |------|---------|-------------------|---------| | **Context** | How to work in this project | Conventions, build/test commands, policies | CLAUDE.md, .cursorrules, AGENTS.md | | **Architecture** | What the code looks like now (file-level) AND what concepts it defines (concept-level) | Modul