generate-rules

To generate path-scoped CLAUDE rules, run the rule-generation workflow to read project manifests, inventory directories, and write modular .claude/rules/* frontmatter files with precise paths. It then updates CLAUDE.md to reference these new scoped instruction files.

Splitting long CLAUDE.md instructions involves reading existing rules and reorganizing them into modular rule files. This preserves universal principles while producing focused, context-light .claude/rules entries that keep project-specific instructions separated by directory paths.

Yes, the rule generation workflow operates without external dependencies. It analyzes your project structure and manifest files directly to identify domains and relevant rule scopes, requiring only the existing codebase and CLAUDE.md file to execute.

Reorganizing an existing CLAUDE.md file uses a phase-driven workflow from discovery to writing rules. It verifies current instructions, extracts them into path-scoped .claude/rules files, and updates CLAUDE.md references to maintain organized, context-light project guidance.

You need modular path-scoped rules when onboarding new projects or refactoring large rule sets. This approach keeps instructions focused and context-light by generating .claude/rules entries that apply precise directory paths to specific codebase domains.