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:

• Via Plugin: /plugin install ecc@ecc — the plugin loads this skill automatically

• 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:

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:

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, Claude API patterns"

  - "Social & Content Distribution" — "X/Twitter API, crossposting alongside content-engine"

  - "Media Generation" — "fal.ai image/video/audio alongside VideoDB"

  - "Orchestration" — "dmux multi-agent workflows"

  - "All skills" — "Install every available skill"

2c: Confirm Individual Skills

For each selected category, print the full list of skills below and ask the user to confirm or deselect specific ones. If the list exceeds 4 items, print the list as text and use AskUserQuestion with an "Install all listed" option plus "Other" for the user to paste specific names.

Category: Framework & Language (25 skills)

Category: Database (3 skills)

Category: Workflow & Quality (8 skills)

Category: Business & Content (5 skills)

Category: Research & APIs (2 skills)

claude-api is an Anthropic canonical skill. Install it from anthropics/skills when you want the official Claude API workflow instead of an ECC-bundled copy.

Category: Social & Content Distribution (2 skills)

Category: Media Generation (2 skills)

Category: Orchestration (1 skill)

Standalone

2d: Execute Installation

For each selected skill, copy the entire skill directory from the correct source root:

# Core skills live under .agents/skills/

cp -R "$ECC_ROOT/.agents/skills/<skill-name>" "$TARGET/skills/"

# Niche skills live under skills/

cp -R "$ECC_ROOT/skills/<skill-name>" "$TARGET/skills/"

When iterating over globbed source directories, never pass a trailing-slash source directly to cp. Use the directory path as the destination name explicitly:

cp -R "${src%/}" "$TARGET/skills/$(basename "${src%/}")"

Note: continuous-learning and continuous-learning-v2 have extra files (config.json, hooks, scripts) — ensure the entire directory is copied, not just SKILL.md.

Step 3: Select & Install Rules

Use AskUserQuestion with multiSelect: true:

Question: "Which rule sets do you want to install?"

Options:

  - "Common rules (Recommended)" — "Language-agnostic principles: coding style, git workflow, testing, security, etc. (8 files)"

  - "TypeScript/JavaScript" — "TS/JS patterns, hooks, testing with Playwright (5 files)"

  - "Python" — "Python patterns, pytest, black/ruff formatting (5 files)"

  - "Go" — "Go patterns, table-driven tests, gofmt/staticcheck (5 files)"

Execute installation:

# Common rules

cp -r $ECC_ROOT/rules/common $TARGET/rules/common

# Language-specific rules (preserve per-language directories)

cp -r $ECC_ROOT/rules/typescript $TARGET/rules/typescript   # if selected

cp -r $ECC_ROOT/rules/python $TARGET/rules/python            # if selected

cp -r $ECC_ROOT/rules/golang $TARGET/rules/golang            # if selected

Important: If the user selects any language-specific rules but NOT common rules, warn them:

"Language-specific rules extend the common rules. Installing without common rules may result in incomplete coverage. Install common rules too?"

Step 4: Post-Installation Verification

After installation, perform these automated checks:

4a: Verify File Existence

List all installed files and confirm they exist at the target location:

ls -la $TARGET/skills/

ls -la $TARGET/rules/

4b: Check Path References

Scan all installed .md files for path references:

grep -rn "~/.claude/" $TARGET/skills/ $TARGET/rules/

grep -rn "../common/" $TARGET/rules/

grep -rn "skills/" $TARGET/skills/

For project-level installs, flag any references to ~/.claude/ paths:

• If a skill references ~/.claude/settings.json — this is usually fine (settings are always user-level)

• If a skill references ~/.claude/skills/ or ~/.claude/rules/ — this may be broken if installed only at project level

• If a skill references another skill by name — check that the referenced skill was also installed

4c: Check Cross-References Between Skills

Some skills reference others. Verify these dependencies:

• django-tdd may reference django-patterns

• laravel-tdd may reference laravel-patterns

• quarkus-tdd may reference quarkus-patterns

• springboot-tdd may reference springboot-patterns

• continuous-learning-v2 references ~/.claude/homunculus/ directory

• python-testing may reference python-patterns

• golang-testing may reference golang-patterns

• crosspost references content-engine and x-api

• deep-research references exa-search (complementary MCP tools)

• fal-ai-media references videodb (complementary media skill)

• x-api references content-engine and crosspost

• Language-specific rules reference common/ counterparts

4d: Report Issues

For each issue found, report:

• File: The file containing the problematic reference

• Line: The line number

• Issue: What's wrong (e.g., "references ~/.claude/skills/python-patterns but python-patterns was not installed")

• Suggested fix: What to do (e.g., "install python-patterns skill" or "update path to .claude/skills/")

Step 5: Optimize Installed Files (Optional)

Use AskUserQuestion:

Question: "Would you like to optimize the installed files for your project?"

Options:

  - "Optimize skills" — "Remove irrelevant sections, adjust paths, tailor to your tech stack"

  - "Optimize rules" — "Adjust coverage targets, add project-specific patterns, customize tool configs"

  - "Optimize both" — "Full optimization of all installed files"

  - "Skip" — "Keep everything as-is"

If optimizing skills:

• Read each installed SKILL.md

• Ask the user what their project's tech stack is (if not already known)

• For each skill, suggest removals of irrelevant sections

• Edit the SKILL.md files in-place at the installation target (NOT the source repo)

• Fix any path issues found in Step 4

If optimizing rules:

• Read each installed rule .md file

• Ask the user about their preferences:

• Test coverage target (default 80%)

• Preferred formatting tools

• Git workflow conventions

• Security requirements

• Edit the rule files in-place at the installation target

Critical: Only modify files in the installation target ($TARGET/), NEVER modify files in the source ECC repository ($ECC_ROOT/).

Step 6: Installation Summary

Clean up the cloned repository from /tmp:

rm -rf /tmp/everything-claude-code

Then print a summary report:

## ECC Installation Complete

### Installation Target

- Level: [user-level / project-level / both]

- Path: [target path]

### Skills Installed ([count])

- skill-1, skill-2, skill-3, ...

### Rules Installed ([count])

- common (8 files)

- typescript (5 files)

- ...

### Verification Results

- [count] issues found, [count] fixed

- [list any remaining issues]

### Optimizations Applied

- [list changes made, or "None"]

Troubleshooting

"Skills not being picked up by Claude Code"

• Verify the skill directory contains a SKILL.md file (not just loose .md files)

• For user-level: check ~/.claude/skills/<skill-name>/SKILL.md exists

• For project-level: check .claude/skills/<skill-name>/SKILL.md exists

"Rules not working"

• Rules are flat files, not in subdirectories: $TARGET/rules/coding-style.md (correct) vs $TARGET/rules/common/coding-style.md (incorrect for flat install)

• Restart Claude Code after installing rules

"Path reference errors after project-level install"

• Some skills assume ~/.claude/ paths. Run Step 4 verification to find and fix these.

• For continuous-learning-v2, the ~/.claude/homunculus/ directory is always user-level — this is expected and not an error.