SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsconfigure-ecc

configure-ecc

General & other

View repository

Updated 10-16 06:52

About this skill

Configure Everything Claude Code (ECC)

An interactive step-by-step installation wizard for the Everything Claude Code project. Use AskUserQuestion to guide the user through selectively installing Skills and Rules, then validate correctness and provide optimization suggestions.

When to Activate

  • When the user says "configure ecc", "install ecc", "setup everything claude code", or similar instructions
  • When the user wants to selectively install Skills or Rules from this project
  • When the user wants to validate or repair an existing ECC installation
  • When the user wants to optimize installed Skills or Rules for their project

Prerequisites

This Skill must be accessible to Claude Code before activation. There are two bootstrap methods:

  1. Via plugin：/plugin install everything-claude-code — the plugin loads this Skill automatically
  2. Manual method: copy only this Skill to ~/.claude/skills/configure-ecc/SKILL.md, then activate it by saying "configure ecc"

Step 0: Clone the 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 path for all subsequent copy operations.

If the clone fails (network issues, etc.), use AskUserQuestion to ask the user for the local path of an existing ECC clone.

Step 1: Choose the installation level

Use AskUserQuestion to ask the user where to install:

问题："ECC 组件应该安装在哪里？"
选项：
  - "用户级 (~/.claude/)" —— "适用于你所有的 Claude Code 项目"
  - "项目级 (.claude/)" —— "仅适用于当前项目"
  - "两者皆有" —— "通用/共享项安装在用户级，项目特定项安装在项目级"

Store the selection result as INSTALL_LEVEL. Set the target directory:

  • User level:TARGET=~/.claude
  • Project level:TARGET=.claude(relative to the current project root)
  • Both:TARGET_USER=~/.claude，TARGET_PROJECT=.claude

If the target directories do not exist, create them:

mkdir -p $TARGET/skills $TARGET/rules

Step 2: Select and install Skills

2a: Choose the scope (core vs niche)

Default to Core (recommended for new users) — copy .agents/skills/* and skills/search-first/ to support a research-first workflow. This bundle covers engineering, Evals, validation, security, strategic compression, frontend design, and Anthropic cross-functional skills (article writing, content engine, market research, frontend presentations).

Use AskUserQuestion(single select):

问题："仅安装核心技能，还是包含小众/框架扩展包？"
选项：
  - "仅核心（推荐）" —— "tdd, e2e, evals, verification, research-first, security, frontend patterns, compacting, 跨职能 Anthropic 技能"
  - "核心 + 选定的小众技能" —— "在核心技能之后添加框架/领域特定技能"
  - "仅小众技能" —— "跳过核心，安装特定的框架/领域技能"
默认：仅核心

If the user selects niche skills or core + niche skills, continue with the category selection below and include only the niche skills they pick.

2b: Choose skill categories

There are 27 skills organized into 4 categories. Use AskUserQuestion and set multiSelect: true：

问题："你想安装哪些技能类别？"
选项：
  - "框架与语言" —— "Django, Spring Boot, Go, Python, Java, 前端, 后端模式"
  - "数据库" —— "PostgreSQL, ClickHouse, JPA/Hibernate 模式"
  - "工作流与质量" —— "TDD, 验证, 学习, 安全审查, 压缩"
  - "所有技能" —— "安装所有可用技能"

2c: Confirm individual skills

For each selected category, print the full skill list below and ask the user to confirm or deselect specific skills. If the list has more than 4 items, print the list as text and use AskUserQuestion to provide an "install all listed items" option, plus an "Other" option for the user to paste specific names.

Category: Frameworks and Languages (17 skills)

Skill Description
backend-patterns Backend architecture, API design, server-side best practices for Node.js/Express/Next.js
coding-standards General code standards for TypeScript, JavaScript, React, Node.js
django-patterns Django architecture, REST APIs with DRF, ORM, caching, signals, middleware
django-security Django security: authentication, CSRF, SQL injection, XSS protection
django-tdd Django testing with pytest-django, factory_boy, mocking, coverage
django-verification Django validation loop: migrations, lint checks, tests, security scans
frontend-patterns React, Next.js, state management, performance, UI patterns
frontend-slides Zero-dependency HTML presentations, style previews, and PPTX-to-Web functionality
golang-patterns Idiomatic Go patterns, conventions for building robust Go applications
golang-testing Go testing: table-driven tests, subtests, benchmarks, fuzzing
java-coding-standards Java code standards for Spring Boot: naming, immutability, Optional, streams
python-patterns Pythonic idioms, PEP 8, type hints, best practices
python-testing Python testing with pytest, including TDD, fixtures, mocking, parametrization
springboot-patterns Spring Boot architecture, REST APIs, layered services, caching, async
springboot-security Spring Security: authentication/authorization, validation, CSRF, secrets, rate limiting
springboot-tdd Spring Boot TDD with JUnit 5, Mockito, MockMvc, Testcontainers
springboot-verification Spring Boot validation: build, static analysis, tests, security scans

Category: Databases (3 skills)

Skill Description
clickhouse-io ClickHouse schemas, query optimization, analytics, data engineering
jpa-patterns JPA/Hibernate entity design, relationships, query optimization, transactions
postgres-patterns PostgreSQL query optimization, schema design, indexing, security

Category: Workflow and Quality (8 skills)

Skill Description
continuous-learning Automatically extract reusable patterns from sessions as learned skills
continuous-learning-v2 Instinct-based learning with confidence scoring that can evolve into skills/commands/agents
eval-harness Formal evaluation framework for evaluation-driven development (EDD)
iterative-retrieval Progressive context refinement for subagent context issues
security-review Security checklist: authentication, input, secrets, APIs, payment functionality
strategic-compact Suggest manual context compaction at logical intervals
tdd-workflow Enforce TDD with 80%+ coverage: unit tests, integration tests, E2E
verification-loop Validation and quality loop patterns

Category: Business and Content (5 skills)

Skill Description
article-writing Long-form writing in a provided tone using notes, examples, or source documents
content-engine Multi-platform social content, scripts, and content repurposing workflows
market-research Market, competitor, fund, and technical research with source attribution
investor-materials Fundraising pitch decks, one-pagers, investor memos, and financial models
investor-outreach Personalized investor cold emails, warm intros, and follow-up emails

Standalone items

Skill Description
project-guidelines-example Create project-specific skill templates

2d: Perform installation

For each selected skill, copy the entire skill directory:

cp -r $ECC_ROOT/skills/<skill-name> $TARGET/skills/

Note:continuous-learning and continuous-learning-v2 contain additional files (config.json, hooks, scripts) — make sure to copy the entire directory, not just SKILL.md.

Step 3: Select and install rules (Rules)

Use AskUserQuestion and set multiSelect: true：

问题："你想安装哪些规则集？"
选项：
  - "通用规则（推荐）" —— "与语言无关的原则：代码风格、git 工作流、测试、安全等（8 个文件）"
  - "TypeScript/JavaScript" —— "TS/JS 模式、Hooks、使用 Playwright 的测试（5 个文件）"
  - "Python" —— "Python 模式、pytest、black/ruff 格式化（5 个文件）"
  - "Go" —— "Go 模式、表格驱动测试、gofmt/staticcheck（5 个文件）"

Perform installation:

# 通用规则（扁平复制到 rules/）
cp -r $ECC_ROOT/rules/common/* $TARGET/rules/

# 语言特定规则（扁平复制到 rules/）
cp -r $ECC_ROOT/rules/typescript/* $TARGET/rules/   # 如果选中
cp -r $ECC_ROOT/rules/python/* $TARGET/rules/        # 如果选中
cp -r $ECC_ROOT/rules/golang/* $TARGET/rules/        # 如果选中

Important note: If the user selected any language-specific rules but did not select the general rules, remind them:

"Language-specific rules are extensions of the general rules. Installing without the general rules may result in incomplete coverage. Do you also want to install the general rules?"

Step 4: Post-installation verification

After installation is complete, perform the following automatic checks:

4a: Verify that files exist

List all installed files and confirm they exist in 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 installations, flag any references pointing 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 fail if installed only at the project level
  • If a skill references another skill by name — check whether the referenced skill is also installed

4c: Check cross-references between skills

Some skills reference other skills. Verify these dependencies:

  • django-tdd may reference django-patterns
  • springboot-tdd may reference springboot-patterns
  • continuous-learning-v2 references the ~/.claude/homunculus/ directory
  • python-testing may reference python-patterns
  • golang-testing may reference golang-patterns
  • Language-specific rules reference the common/ corresponding rules

4d: Report issues

For each issue found, report the following:

  1. File: The file containing the problematic reference
  2. Line number: The line number where it is located
  3. Issue description: What went wrong (e.g., "references ~/.claude/skills/python-patterns but python-patterns is not installed")
  4. Suggested fix: What to do (e.g., "install the python-patterns skill" or "update the path to .claude/skills/")

Step 5: Optimize installed files (optional)

Use AskUserQuestion：

问题："你想为你的项目优化已安装的文件吗？"
选项：
  - "优化技能（Skills）" —— "移除无关章节，调整路径，适配你的技术栈"
  - "优化规则（Rules）" —— "调整覆盖率目标，添加项目特定模式，自定义工具配置"
  - "优化两者" —— "对所有安装文件进行全面优化"
  - "跳过" —— "保持原样"

If optimizing skills:

  1. Read each installed SKILL.md
  2. Ask the user about their project tech stack (if not already clear)
  3. For each skill, suggest removing irrelevant sections
  4. Edit the SKILL.md files in place at the installation target location (not the source repository)
  5. Fix any path issues found in step 4

If optimizing rules:

  1. Read each installed rule .md file
  2. Ask the user for their preferences:
    • Test coverage target (default 80%)
    • Preferred formatting tool
    • Git workflow conventions
    • Security requirements
  3. Edit rule files in place at the installation target location

Key reminder: Only modify files in the installation target ($TARGET/), never modify files in the source ECC repository ($ECC_ROOT/).

Step 6: Installation summary

From /tmp clean up the cloned repository:

rm -rf /tmp/everything-claude-code

Then print a summary report:

## ECC 安装完成

### 安装目标
- 层级：[用户级 / 项目级 / 两者皆有]
- 路径：[目标路径]

### 已安装技能 ([数量])
- skill-1, skill-2, skill-3, ...

### 已安装规则 ([数量])
- 通用规则 (8 个文件)
- typescript (5 个文件)
- ...

### 验证结果
- 发现 [数量] 个问题，已修复 [数量] 个
- [列出任何剩余问题]

### 已应用的优化
- [列出所做的更改，或 "无"]

Troubleshooting

"Skill not recognized by Claude Code"

  • Verify that the skill directory contains the SKILL.md file (not just scattered .md files)
  • For user-level: check whether ~/.claude/skills/<skill-name>/SKILL.md exists
  • For project-level: check whether .claude/skills/<skill-name>/SKILL.md exists

"Rules not taking effect"

  • Rules should be flat files and should not be placed in subdirectories:$TARGET/rules/coding-style.md(correct) vs $TARGET/rules/common/coding-style.md(incorrect for a flat installation)
  • Restart Claude Code after installing the rules

"Path reference errors after project-level installation"

  • Some skills assume the path is ~/.claude/. Run the verification from Step 4 to find and fix these issues.
  • For continuous-learning-v2，~/.claude/homunculus/ the directory is always user-level — this is expected, not an error.