configure-ecc

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Configure Everything Claude Code (ECC)

配置 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.

这是Everything Claude Code项目的交互式分步安装向导。通过

AskUserQuestion

引导用户选择性安装技能和规则，随后验证正确性并提供优化选项。

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

用户说出"configure ecc"、"install ecc"、"setup everything claude code"或类似指令时
用户想要选择性安装本项目中的技能或规则时
用户想要验证或修复现有ECC安装时
用户想要为其项目优化已安装的技能或规则时

Prerequisites

前置条件

This skill must be accessible to Claude Code before activation. Two ways to bootstrap:

Via Plugin:
```
/plugin install everything-claude-code
```
— the plugin loads this skill automatically
Manual: Copy only this skill to
```
~/.claude/skills/configure-ecc/SKILL.md
```
, then activate by saying "configure ecc"

激活前，Claude Code必须能访问此技能。有两种引导方式：

通过插件：
```
/plugin install everything-claude-code
```
—— 插件会自动加载此技能
手动方式：仅将此技能复制到
```
~/.claude/skills/configure-ecc/SKILL.md
```
，然后说出"configure ecc"激活

Step 0: Clone ECC Repository

步骤0：克隆ECC仓库

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.

在进行任何安装前，将最新的ECC源码克隆到

/tmp

bash

rm -rf /tmp/everything-claude-code
git clone https://github.com/affaan-m/everything-claude-code.git /tmp/everything-claude-code

设置

ECC_ROOT=/tmp/everything-claude-code

作为后续所有复制操作的源目录。

如果克隆失败（如网络问题等），使用

AskUserQuestion

询问用户提供现有ECC克隆的本地路径。

Step 1: Choose Installation Level

步骤1：选择安装级别

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

使用

AskUserQuestion

询问用户安装位置：

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

将选择结果存储为

INSTALL_LEVEL

。设置目标目录：

用户级：
```
TARGET=~/.claude
```
项目级：
```
TARGET=.claude
```
（相对于当前项目根目录）

两者都装：

TARGET_USER=~/.claude

，

TARGET_PROJECT=.claude

如果目标目录不存在则创建：

bash

mkdir -p $TARGET/skills $TARGET/rules

Step 2: Select & Install Skills

步骤2：选择并安装技能

2a: Choose Skill Categories

2a：选择技能类别

There are 27 skills organized into 4 categories. Use

AskUserQuestion

with

multiSelect: true

Question: "Which skill categories do you want to install?"
Options:
  - "Framework & Language" — "Django, Spring Boot, Go, Python, Java, Frontend, Backend patterns"
  - "Database" — "PostgreSQL, ClickHouse, JPA/Hibernate patterns"
  - "Workflow & Quality" — "TDD, verification, learning, security review, compaction"
  - "All skills" — "Install every available skill"

现有27个技能，分为4个类别。使用支持

multiSelect: true

的

AskUserQuestion

：

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

2b: Confirm Individual Skills

2b：确认单个技能

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 (16 skills)

Skill	Description
`backend-patterns`	Backend architecture, API design, server-side best practices for Node.js/Express/Next.js
`coding-standards`	Universal coding standards for TypeScript, JavaScript, React, Node.js
`django-patterns`	Django architecture, REST API with DRF, ORM, caching, signals, middleware
`django-security`	Django security: auth, CSRF, SQL injection, XSS prevention
`django-tdd`	Django testing with pytest-django, factory_boy, mocking, coverage
`django-verification`	Django verification loop: migrations, linting, tests, security scans
`frontend-patterns`	React, Next.js, state management, performance, UI patterns
`golang-patterns`	Idiomatic Go patterns, conventions for robust Go applications
`golang-testing`	Go testing: table-driven tests, subtests, benchmarks, fuzzing
`java-coding-standards`	Java coding standards for Spring Boot: naming, immutability, Optional, streams
`python-patterns`	Pythonic idioms, PEP 8, type hints, best practices
`python-testing`	Python testing with pytest, TDD, fixtures, mocking, parametrization
`springboot-patterns`	Spring Boot architecture, REST API, layered services, caching, async
`springboot-security`	Spring Security: authn/authz, validation, CSRF, secrets, rate limiting
`springboot-tdd`	Spring Boot TDD with JUnit 5, Mockito, MockMvc, Testcontainers
`springboot-verification`	Spring Boot verification: build, static analysis, tests, security scans

Category: Database (3 skills)

Skill	Description
`clickhouse-io`	ClickHouse patterns, 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 & Quality (8 skills)

Skill	Description
`continuous-learning`	Auto-extract reusable patterns from sessions as learned skills
`continuous-learning-v2`	Instinct-based learning with confidence scoring, evolves into skills/commands/agents
`eval-harness`	Formal evaluation framework for eval-driven development (EDD)
`iterative-retrieval`	Progressive context refinement for subagent context problem
`security-review`	Security checklist: auth, input, secrets, API, payment features
`strategic-compact`	Suggests manual context compaction at logical intervals
`tdd-workflow`	Enforces TDD with 80%+ coverage: unit, integration, E2E
`verification-loop`	Verification and quality loop patterns

Standalone

Skill	Description
`project-guidelines-example`	Template for creating project-specific skills

对于每个选中的类别，打印下方完整技能列表，询问用户确认或取消选择特定技能。如果列表超过4项，将列表以文本形式打印，并使用

AskUserQuestion

提供“安装所有列出技能”选项，以及“其他”选项供用户粘贴特定技能名称。

类别：框架与语言（16个技能）

技能	描述
`backend-patterns`	后端架构、API设计、Node.js/Express/Next.js服务端最佳实践
`coding-standards`	TypeScript、JavaScript、React、Node.js通用编码规范
`django-patterns`	Django架构、DRF REST API、ORM、缓存、信号、中间件
`django-security`	Django安全：认证、CSRF、SQL注入、XSS防护
`django-tdd`	使用pytest-django、factory_boy、Mocking、覆盖率工具进行Django测试
`django-verification`	Django验证循环：迁移、代码检查、测试、安全扫描
`frontend-patterns`	React、Next.js、状态管理、性能、UI模式
`golang-patterns`	地道的Go模式、健壮Go应用的约定
`golang-testing`	Go测试：表驱动测试、子测试、基准测试、模糊测试
`java-coding-standards`	Spring Boot Java编码规范：命名、不可变性、Optional、流
`python-patterns`	Python化 idiom、PEP 8、类型提示、最佳实践
`python-testing`	使用pytest、TDD、fixtures、Mocking、参数化进行Python测试
`springboot-patterns`	Spring Boot架构、REST API、分层服务、缓存、异步
`springboot-security`	Spring Security：认证/授权、验证、CSRF、密钥、速率限制
`springboot-tdd`	使用JUnit 5、Mockito、MockMvc、Testcontainers进行Spring Boot TDD
`springboot-verification`	Spring Boot验证：构建、静态分析、测试、安全扫描

类别：数据库（3个技能）

技能	描述
`clickhouse-io`	ClickHouse模式、查询优化、分析、数据工程
`jpa-patterns`	JPA/Hibernate实体设计、关系、查询优化、事务
`postgres-patterns`	PostgreSQL查询优化、 schema设计、索引、安全

类别：工作流与质量（8个技能）

技能	描述
`continuous-learning`	从会话中自动提取可复用模式作为习得技能
`continuous-learning-v2`	基于直觉的学习，带置信度评分，可演变为技能/命令/代理
`eval-harness`	用于评估驱动开发（EDD）的正式评估框架
`iterative-retrieval`	针对子代理上下文问题的渐进式上下文优化
`security-review`	安全检查清单：认证、输入、密钥、API、支付功能
`strategic-compact`	建议在逻辑间隔处手动压缩上下文
`tdd-workflow`	强制执行覆盖率80%+的TDD：单元测试、集成测试、端到端测试
`verification-loop`	验证与质量循环模式

独立技能

技能	描述
`project-guidelines-example`	创建项目特定技能的模板

2c: Execute Installation

2c：执行安装

For each selected skill, copy the entire skill directory:

bash

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

Note:

continuous-learning

and

continuous-learning-v2

have extra files (config.json, hooks, scripts) — ensure the entire directory is copied, not just SKILL.md.

对于每个选中的技能，复制整个技能目录：

bash

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

注意：

continuous-learning

和

continuous-learning-v2

包含额外文件（config.json、hooks、scripts）——确保复制整个目录，而不仅仅是SKILL.md。

Step 3: Select & Install Rules

步骤3：选择并安装规则

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:

bash

undefined

使用支持

multiSelect: true

的

AskUserQuestion

：

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

执行安装：

bash

undefined

Common rules (flat copy into rules/)

通用规则（直接复制到rules/目录）

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

Language-specific rules (flat copy into rules/)

特定语言规则（直接复制到rules/目录）

cp -r $ECC_ROOT/rules/typescript/* $TARGET/rules/ # if selected cp -r $ECC_ROOT/rules/python/* $TARGET/rules/ # if selected cp -r $ECC_ROOT/rules/golang/* $TARGET/rules/ # 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?"

---

cp -r $ECC_ROOT/rules/typescript/* $TARGET/rules/ # 如果选中 cp -r $ECC_ROOT/rules/python/* $TARGET/rules/ # 如果选中 cp -r $ECC_ROOT/rules/golang/* $TARGET/rules/ # 如果选中


**重要提示**：如果用户选择了任何特定语言规则但未选择通用规则，需发出警告：
> "特定语言规则是对通用规则的扩展。不安装通用规则可能导致覆盖不完整。是否也要安装通用规则？"

---

Step 4: Post-Installation Verification

步骤4：安装后验证

After installation, perform these automated checks:

安装完成后，执行以下自动检查：

4a: Verify File Existence

4a：验证文件存在性

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

bash

ls -la $TARGET/skills/
ls -la $TARGET/rules/

列出所有已安装文件，确认它们存在于目标位置：

bash

ls -la $TARGET/skills/
ls -la $TARGET/rules/

4b: Check Path References

4b：检查路径引用

Scan all installed

.md

files for path references:

bash

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

扫描所有已安装的

.md

文件中的路径引用：

bash

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

对于项目级安装，标记所有指向

~/.claude/

路径的引用：

如果技能引用
```
~/.claude/settings.json
```
—— 通常没问题（设置始终是用户级的）
如果技能引用
```
~/.claude/skills/
```
或
```
~/.claude/rules/
```
—— 如果仅安装在项目级，这可能会失效
如果技能按名称引用其他技能 —— 检查被引用的技能是否也已安装

4c: Check Cross-References Between Skills

4c：检查技能间的交叉引用

Some skills reference others. Verify these dependencies:

```
django-tdd
```
may reference
```
django-patterns
```
```
springboot-tdd
```
may reference
```
springboot-patterns
```

continuous-learning-v2

references

~/.claude/homunculus/

4d: Report Issues

4d：报告问题

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/")

对于发现的每个问题，报告：

文件：包含问题引用的文件
行号：问题所在行号
问题：具体问题（例如："引用~/.claude/skills/python-patterns但python-patterns未安装"）
建议修复方案：解决方法（例如："安装python-patterns技能"或"将路径更新为.claude/skills/"）

Step 5: Optimize Installed Files (Optional)

步骤5：优化已安装文件（可选）

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"

使用

AskUserQuestion

：

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

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

读取每个已安装的SKILL.md
询问用户其项目的技术栈（如果未知）
针对每个技能，建议移除无关章节
在安装目标位置（而非源仓库）直接编辑SKILL.md文件
修复步骤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/

读取每个已安装的规则.md文件
询问用户偏好：
- 测试覆盖率目标（默认80%）
- 首选格式化工具
- Git工作流约定
- 安全要求
在安装目标位置直接编辑规则文件

关键注意事项：仅修改安装目标目录（

$TARGET/

）中的文件，绝不要修改源ECC仓库（

$ECC_ROOT/

）中的文件。

Step 6: Installation Summary

步骤6：安装总结

Clean up the cloned repository from

/tmp

bash

rm -rf /tmp/everything-claude-code

Then print a summary report:

undefined

清理

/tmp

目录中的克隆仓库：

bash

rm -rf /tmp/everything-claude-code

然后打印总结报告：

undefined

ECC Installation Complete

ECC安装完成

Installation Target

安装目标

Level: [user-level / project-level / both]
Path: [target path]

级别：[用户级 / 项目级 / 两者都装]
路径：[目标路径]

Skills Installed ([count])

已安装技能（[数量]个）

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

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

Rules Installed ([count])

已安装规则（[数量]个）

common (8 files)
typescript (5 files)
...

common（8个文件）
typescript（5个文件）
...

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"

"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

验证技能目录包含
```
SKILL.md
```
文件（不能是零散的.md文件）
对于用户级：检查
```
~/.claude/skills/<skill-name>/SKILL.md
```
是否存在
对于项目级：检查
```
.claude/skills/<skill-name>/SKILL.md
```
是否存在

"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

规则是扁平文件，不能放在子目录中：
```
$TARGET/rules/coding-style.md
```
（正确） vs
```
$TARGET/rules/common/coding-style.md
```
（扁平安装时错误）
安装规则后重启Claude Code

"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.

部分技能假设使用
```
~/.claude/
```
路径。运行步骤4的验证来查找并修复这些问题。
对于
```
continuous-learning-v2
```
，
```
~/.claude/homunculus/
```
目录始终是用户级的——这是预期行为，并非错误。