Configure Ecc
Run the interactive Everything Claude Code installer to copy selected skills and rules into user- or project-level Claude directories, verify paths, and optionally optimize them.
Overview
Configure ECC is an agent skill most often used in Build (also Validate, Ship) that interactively installs and verifies selected Everything Claude Code skills and rules.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill configure-eccWhat is this skill?
- Interactive wizard driven by AskUserQuestion for selective skill and rule installs
- Bootstraps via `/plugin install ecc@ecc` or manual copy of configure-ecc to `~/.claude/skills/`
- Step 0 clones ECC from GitHub into `/tmp/everything-claude-code` before file copies
- Supports user-level vs project-level destination directories with post-install verification
- Offers optional optimization pass on installed skills and rules for the current repo
- Bootstraps with git clone to /tmp/everything-claude-code
- Documents plugin path: /plugin install ecc@ecc
Adoption & trust: 5k installs on skills.sh; 210k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have the ECC repo but no clear, verified way to install only the skills and rules you need into Claude’s directories.
Who is it for?
Solo builders adopting Everything Claude Code who want a selective, verified install instead of manual folder copying.
Skip if: Teams not using Claude Code/ECC, or users who already have a frozen, audited skill set and do not want an installer mutating agent config.
When should I use this skill?
User says configure ecc, install ecc, setup everything claude code, or wants to verify, fix, or optimize an ECC installation.
What do I get? / Deliverables
Selected ECC skills and rules land in the correct user or project paths with verification and optional optimization so you can invoke the rest of the ECC stack immediately.
- Installed ECC skills and rules in chosen scope
- Verified directory layout
- Optional optimized skill/rule files
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build/agent-tooling is the first moment solo builders bootstrap Claude Code capabilities before coding workflows in later phases. Agent-tooling matches installing and verifying SKILL.md assets rather than application runtime code.
Where it fits
Clone ECC to /tmp and install only review and planning skills into ~/.claude/skills.
Add project-level rules before locking MVP scope so the agent respects repo conventions.
Re-run the wizard to verify paths after upgrading ECC from GitHub.
How it compares
Interactive ECC packager—not a single feature skill like code review or brainstorming.
Common Questions / FAQ
Who is configure-ecc for?
Claude Code users bringing in the Everything Claude Code project who want guided, selective installation and path checks.
When should I use configure-ecc?
At project kickoff in Build when wiring agent tooling; during Validate when tightening rules before a prototype push; during Ship when fixing a broken or partial ECC install before release prep.
Is configure-ecc safe to install?
Review the Security Audits panel on this Prism page; the skill clones a remote repo and copies files into agent config directories on your machine.
SKILL.md
READMESKILL.md - 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 or core + niche, continue to category selection below and only include those niche skills they pick. ### 2b: Choose Skill Categories There are 7 selectable category groups below. The detailed confirmation lists that follow cover 45 skills across 8 categories, plus 1 standalone template. Use `AskUserQuestion` with `multiSelect: true`: ``` Question: "Which skill categories do you want to install?" Options: - "Framework & Language" — "Django, Laravel, Spring Boot, Quarkus, Go, Python, Java, Frontend, Backend patterns" - "Database" — "PostgreSQL, ClickHouse, JPA/Hibernate patterns" - "Workflow & Quality" — "TDD, verification, learning, security review, compaction" - "Research & APIs" — "Deep research, Exa search, C