new-rulelisted

# /new-rule Scaffold a new workflow rule. Use when you (or Claude) discover a behavior worth standardizing across projects. ## Usage ``` /new-rule <kebab-name> ``` E.g.: `/new-rule no-emoji-in-prose` ## Pre-flight - Verify `rules/<kebab-name>/` does not already exist (don't clobber) - Confirm the rule isn't redundant with an existing one (check `INVENTORY.md` table) ## Steps 1. **Create directory**: ```bash mkdir -p rules/<kebab-name> ``` 2. **Ask the user** for: - One-line description (becomes `description:` frontmatter) - Scope: `universal | personal | ui-project | research-pkg | static-site | optional` - Rationale: 1-2 sentences on what bug this rule prevents / time it saves - Trigger condition: when does this rule kick in? 3. **Write `rules/<kebab-name>/RULE.md`**: ```markdown --- name: <kebab-name> description: <one-line> scope: <scope> rationale: <why-this-rule-exists> --- # <kebab-name> > <one-line summary> ## Master TOC - [Rule](#rule) - [Why](#why) - [How to apply](#how-to-apply) - [Examples](#examples) - [Exceptions](#exceptions) ## Rule <imperative statement of the rule, with bullet points for clarity> ## Why <full rationale — what problem this prevents, what time it saves> ## How to apply <when this rule kicks in; edge cases; companion rules> ## Examples ✅ Good: <concrete scenario> ❌ Bad: <contrast scenario> ## Exceptions <when the ru