claude-md-optimizer

To reduce token usage in a bloated CLAUDE.md, this Skill audits the file and extracts accumulated rules and references into organized sub-documents, replacing them with focused pointers to preserve essential guidance while cutting token waste.

The best way to organize large project documentation is to maintain a lean main CLAUDE.md containing core rules and mandatory pointers, while moving detailed references into structured sub-docs like DEV_SETUP or TESTING_GUIDE to enable a clean doc chain.

Cross-document reference validation works by enforcing a token-budget-aware workflow that ensures pointers in the main CLAUDE.md correctly link to extracted sub-docs, maintaining a clean documentation chain without broken references across team projects.

Yes, you can audit CLAUDE.md for teams without losing mandatory rules because the restructuring process specifically preserves essential operational guardrails while identifying only the accumulated content that should be extracted into sub-documents.

You should extract documentation into sub-docs when your CLAUDE.md becomes bloated with accumulated rules, references, and workflow guidance, causing token waste during repeated turns and reducing clarity for team operations.