forgelisted

# Rules Builder — Quality-Scored Rule Creation Create `.claude/rules/` files that are specific, scoped, and quality-scored. **Language:** Rule drafting and scoring is English-only. If arguments are provided, treat them as the rule topic: $ARGUMENTS ## `AskUserQuestion` shape constraints — apply to every invocation in this skill Every decision point in this skill that presents a fixed, option-shaped answer space MUST use `AskUserQuestion` — plain-text questions like "Want me to do X, or Y?" break the button-driven flow and users may not notice them. - Every invocation MUST pass the canonical top-level shape `{ questions: [{ question, header, multiSelect, options }] }`. The `questions: [...]` array wrapper is required — flat-form inputs without it are rejected by the tool schema. Each field list below describes the contents of the single entry inside that array. - `header` MUST be ≤12 characters (tool-enforced; longer values truncate silently). - `options` MUST contain 2–4 entries. The harness auto-injects an "Other" escape when needed — do NOT add a 5th option manually. - Every option MUST have `label` and `description`. Omitting `description` produces bare buttons with no guidance. - `multiSelect: true` ONLY when selections are logically independent (e.g. multiple test scopes). Default to `false`. - Open-ended prompts with no enumerable answer space (like Phase 1 Step 2's opening question, or "Which directories are the focus?") stay as plain prose — see per-phase notes b