configure-ecc

# Configure Everything Claude Code (ECC) An interactive, step-by-step installation wizard for the Everything Claude Code project. Uses `AskUserQuestion` to guide users through selective installation of skills and rules, then verifies correctness and offers optimization. ## When to Activate - User says "configure ecc", "install ecc", "setup everything claude code", or similar - User wants to selectively install skills or rules from this project - User wants to verify or fix an existing ECC installation - User wants to optimize installed skills or rules for their project ## Prerequisites This skill must be accessible to Claude Code before activation. Two ways to bootstrap: 1. **Via Plugin**: `/plugin install ecc@ecc` — the plugin loads this skill automatically 2. **Manual**: Copy only this skill to `~/.claude/skills/configure-ecc/SKILL.md`, then activate by saying "configure ecc" --- ## Step 0: Clone ECC Repository Before any installation, clone the latest ECC source to `/tmp`: ```bash rm -rf /tmp/everything-claude-code git clone https://github.com/affaan-m/everything-claude-code.git /tmp/everything-claude-code ``` Set `ECC_ROOT=/tmp/everything-claude-code` as the source for all subsequent copy operations. If the clone fails (network issues, etc.), use `AskUserQuestion` to ask the user to provide a local path to an existing ECC clone. --- ## Step 1: Choose Installation Level Use `AskUserQuestion` to ask the user where to install: ``` Question: "Where should ECC components be installed?" Options: - "User-level (~/.claude/)" — "Applies to all your Claude Code projects" - "Project-level (.claude/)" — "Applies only to the current project" - "Both" — "Common/shared items user-level, project-specific items project-level" ``` Store the choice as `INSTALL_LEVEL`. Set the target directory: - User-level: `TARGET=~/.claude` - Project-level: `TARGET=.claude` (relative to current project root) - Both: `TARGET_USER=~/.claude`, `TARGET_PROJECT=.claude` Create the target directories if they don't exist: ```bash mkdir -p $TARGET/skills $TARGET/rules ``` --- ## Step 2: Select & Install Skills ### 2a: Choose Scope (Core vs Niche) Default to **Core (recommended for new users)** — copy `.agents/skills/*` plus `skills/search-first/` for research-first workflows. This bundle covers engineering, evals, verification, security, strategic compaction, frontend design, and Anthropic cross-functional skills (article-writing, content-engine, market-research, frontend-slides). Use `AskUserQuestion` (single select): ``` Question: "Install core skills only, or include niche/framework packs?" Options: - "Core only (recommended)" — "tdd, e2e, evals, verification, research-first, security, frontend patterns, compacting, cross-functional Anthropic skills" - "Core + selected niche" — "Add framework/domain-specific skills after core" - "Niche only" — "Skip core, install specific framework/domain skills" Default: Core only ``` If the user chooses niche o