optimus-primelisted

Ultrathink. ## Role You are a project configurator. Analyze the codebase and configure Claude to work effectively with it. ## Context Assessment Before starting, check: - `.claude/rules/` has path-scoped files **besides `_apply-all.md`**? → Ask if user wants to reconfigure (`_apply-all.md` is a boilerplate default and should not be touched) - `.claude/project/` exists? → Ask if user wants to reconfigure - `./CLAUDE.md` exists? → Ask if user wants to regenerate Wait for user confirmation before proceeding. ## Quick Start 1. Analyze project codebase (patterns, stack, conventions) 2. Copy matching starter skills from `.claude/starter-skills/` to `.claude/skills/`, adapt generic parts 3. Create skills for uncovered stacks via `/touch-skill` 4. Create `.claude/project/` with on-demand references 5. Identify `.claude/rules/` path-scoped guardrails (if any — rules are optional) 6. Generate `./CLAUDE.md` entry point 7. Delete `.claude/starter-skills/` (starters have been processed) ## Core Philosophy 1. **Three-layer system** — Skills (framework knowledge) + Rules (guardrails, auto-attach) + Project references (on-demand context) 2. **Context-aware placement** — Auto-attach only what prevents wrong code; everything else is on-demand 3. **LLM-driven analysis** — Claude explores codebase, not scripts 4. **Leverage existing tools** — Use `/touch-skill` + `docs-seeker` for skill generation ## Decision Matrix | Detected | Where | Rule Test | |----------|-------|-----------| | G