setup-rules

# /setup-rules - Set Up Project Rules **Set up and audit project rules.** Reads your codebase, generates modular rules, and documents MCP servers. **Flow:** Read existing → Migrate → Quality audit → Explore → Compare → Sync rules → Sync MCP → Discover rules → Cross-check → Summary **Skill creation:** Use `/create-skill` to create workflow skills — `/setup-rules` focuses exclusively on rules and MCP documentation. --- ## Phase 0: Reference ### Guidelines - **Always use AskUserQuestion** when asking the user anything - **Read before writing** — check existing rules before creating - **Write concise rules** — every word costs tokens in context - **Idempotent** — running multiple times produces consistent results ### Project Slug Derive the project slug from the git repo or directory name. Use it as a prefix for ALL created rules and skills to avoid name collisions across repositories. ```bash # Derive slug: git repo name (preferred) or directory basename SLUG=$(basename "$(git remote get-url origin 2>/dev/null | sed 's/\.git$//')" 2>/dev/null || basename "$PWD") # Result: "pilot-shell", "my-api", "acme-backend" ``` Use `{slug}-` prefix on everything: `{slug}-project.md`, `{slug}-mcp-servers.md`, `{slug}-{topic}.md`. ### Output Locations **Custom rules** in `.claude/rules/`: `{slug}-project.md` (tech stack, structure), `{slug}-mcp-servers.md` (custom MCP servers), `{slug}-{pattern-name}.md` (tribal knowledge). Use unique names (not `plan`, `implement`, `verify`, `st...