seedlisted

Concrete rules enforce. Abstract principles don't. Every rule in a CLAUDE.md must be a situation→action pair that Claude either follows or visibly violates — no interpretation required. This was empirically validated: situation-keyed rules score 10.2% higher on compliance than named principles. ## Principles - Every rule starts with "When [situation]:" followed by a concrete action. No principle names, no abstract descriptions. - Anti-examples enforce better than positive instructions. "Do NOT suggest X, Y, Z" beats "Keep it focused." - Explicit ordering words make sequencing stick. "BEFORE any code" and "Then and only then" are enforcement language. - Concrete output formats enforce themselves. "Write three sections: 1. What I know 2. What I assume 3. What I need" — Claude either follows the format or visibly doesn't. - The output is a CLAUDE.md file, not a conversation. No explanations, no rationale — just rules. ## Presentation - One AskUserQuestion per step. Label = the choice. Description = what it means for the generated rules. - No preamble between questions. One bold sentence framing the decision, then the question. - Final output is the raw CLAUDE.md content — no wrapping, no commentary. ## Workflow ### Step 1: Detect project context Read the project to understand what rules apply. No text output — go straight to Step 2. 1. Read package.json / Cargo.toml / pyproject.toml / go.mod — detect stack 2. Read existing CLAUDE.md if present — note what to preserve 3.