What problem does it solve? Writing Claude Code rules by hand often produces files that never load (globs matching nothing), conflict with CLAUDE.md or neighboring rules, or contain unenforceable instructions. This Skill guides the creation and editing of rules in .claude/rules/ through repository exploration, a structured interview, glob verification, and an independent subagent review. ## Core Features & Use Cases - Convention extraction and interview: Mines existing linter configs, representative source files, and folder structure, then confirms scope, rules, and filename with the user before writing. - Glob design and verification: Proposes paths globs and validates each one against the real repository structure so the rule actually loads where intended. - CLAUDE.md decomposition: Splits a bloated CLAUDE.md into path-scoped rules via a confirmed block-to-target table, without rewriting the instructions being moved. - Independent review loop: Sends every touched file to a fresh-context review subagent and iterates until approval, with defined escalation rules. - Use Case: Ask to add a rule for API conventions; the Skill inspects the codebase, confirms enforceable rules with you, writes api-design.md with verified globs, and gets it independently reviewed. ## Quick Start Ask the assistant to create a rule for your project's testing conventions and let it interview you about scope and enforceable rules.
