rules-optimizer

Claude Rules files are Markdown documents stored in .claude/rules/ that define coding standards and AI behavior guidelines. Create one rule per file with a front matter header listing applicable paths, structure it with BAD/GOOD code examples, and keep it to 150-200 lines following framework-specific conventions for your tech stack.

Organize rules under .claude/rules/ with separate files for TypeScript, frontend, and backend concerns—one topic per file for maintainability. Use Markdown front matter to specify which paths each rule applies to, include concrete BAD/GOOD examples, and follow framework conventions to enforce consistent AI-guided behavior across your codebase.

Yes. Each rule file should include one BAD example showing the anti-pattern to avoid and one GOOD example showing the correct approach. This structure helps Claude understand both what not to do and the preferred pattern, making your rules actionable and concrete.

Yes. Use a defined output format with Markdown front matter containing paths, maintain one topic per file, target 150-200 lines, include one BAD/GOOD example pair per rule, and apply framework-specific conventions for TypeScript, frontend, or backend contexts to ensure consistency and clarity.

Optimize by restructuring files to cover one topic each, adding clear BAD/GOOD code examples if missing, ensuring front matter headers list correct paths, removing redundancy, and applying framework-specific best practices. Aim for 150-200 lines per file with concrete, actionable patterns.

Use migration mappings provided for version upgrades to update your .claude/rules/ files. Review each rule's front matter paths, verify BAD/GOOD examples still reflect current best practices, and restructure as needed to maintain the one-topic-per-file standard and defined output format.