three-tier-docs

To automatically sync CLAUDE.md and CONTEXT.md after code changes, you can automate cross-tier documentation synchronization to align these files and docs. This enforces a 3-tier structure and maintains size constraints.

A 3-tier documentation structure organizes AI context by aligning the Tier 1 entry file (CLAUDE.md) with Tier 2 (CONTEXT.md) and Tier 3 docs. This keeps project documentation in lockstep with code.

To keep AI context documentation under 200 lines per file, use automated cross-tier synchronization to maintain size constraints. This encourages consistent organization across all generated context files.

Yes, documentation synchronization works for both feature development and refactoring workflows. After implementing features, refactoring code, or creating new components, running a sync updates all relevant docs.

The best way to update docs/ai-context files when refactoring components is to run an automated cross-tier documentation synchronization. This aligns all relevant docs and provides automated references to templates.