filelisted

# Rules Linter — Structural Formatting Reformat Claude Code rule files using four structural transforms: split multi-concept bullets into one-concept-per-bullet, add blank-line separation between bullets, restructure long single-directive rules into sub-lists, and unwrap space-indented continuation lines into single-line bullets. This skill NEVER changes rule content — structure only. For quality improvements and example injection, use the assay skill. For new rules, use the forge skill. If arguments are provided, treat them as a scope path restriction: $ARGUMENTS ## `AskUserQuestion` shape constraints — apply to every invocation in this skill Every decision point with a fixed, enumerable answer space MUST use `AskUserQuestion` — plain-text questions break the button-driven flow. - Every invocation MUST pass `{ questions: [{ question, header, multiSelect, options }] }`. The `questions: [...]` array wrapper is required. - `header` MUST be ≤12 characters. - `options` MUST contain 2–4 entries. Never add a 5th manually. - Every option MUST have `label` and `description`. ## Task tracking MUST invoke `TaskCreate` for each task below before any other work, capturing each returned `taskId`. In non-interactive / SDK sessions, fall back to `TodoWrite`. Every task MUST carry paired `content` (imperative) and `activeForm` (progressive) fields — they are NOT interchangeable. Initial tasks (create all up front, with both forms): 1. `{ content: "Resolve scope", activeForm: "Res