Back to Details

ecc-guide

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

ECC Guide

ECC Guide

Use this skill when a user needs help understanding, navigating, installing, or choosing parts of Everything Claude Code.
当用户需要帮助理解、导航、安装或选择Everything Claude Code（ECC）的相关部分时，使用此skill。

When To Use

使用场景

Use this skill when the user:
  • asks what ECC includes
  • wants help finding a skill, command, agent, hook, rule, or install profile
  • is new to the repository and needs a guided path
  • asks "how do I do X with ECC?"
  • asks which ECC components fit a project
  • needs a lightweight explanation of how commands, skills, agents, hooks, and rules relate
  • is confused by install paths, duplicate installs, reset/uninstall, or selective install options
当用户出现以下情况时使用此skill：
  • 询问ECC包含哪些内容
  • 需要帮助查找某个skill、command、agent、hook、rule或安装配置文件
  • 是仓库新用户，需要引导路径
  • 询问“我如何用ECC完成X操作？”
  • 询问哪些ECC组件适合自己的项目
  • 需要对commands、skills、agents、hooks和rules之间的关系进行简洁解释
  • 对安装路径、重复安装、重置/卸载或选择性安装选项感到困惑

Core Principle

核心原则

Answer from current files, not memory. ECC changes quickly, so hard-coded catalog counts, feature lists, and install instructions go stale.
When the ECC repository is available, inspect the relevant files before giving a concrete answer:
bash
node scripts/ci/catalog.js --json
find skills -maxdepth 2 -name SKILL.md | sort
find commands -maxdepth 1 -name '*.md' | sort
find agents -maxdepth 1 -name '*.md' | sort
node scripts/install-plan.js --list-profiles
node scripts/install-plan.js --list-components --json
Use the smallest set of reads needed for the user's question.
根据当前文件回答，而非依赖记忆。ECC更新迅速，因此硬编码的目录数量、功能列表和安装说明会很快过时。
当可以访问ECC仓库时，在给出具体答案前先检查相关文件：
bash
node scripts/ci/catalog.js --json
find skills -maxdepth 2 -name SKILL.md | sort
find commands -maxdepth 1 -name '*.md' | sort
find agents -maxdepth 1 -name '*.md' | sort
node scripts/install-plan.js --list-profiles
node scripts/install-plan.js --list-components --json
使用满足用户问题所需的最少文件读取操作。

Repository Map

仓库结构映射

  • README.md
    : install paths, uninstall/reset guidance, public positioning, FAQs
  • AGENTS.md
    : contributor guidance and project structure
  • agent.yaml
    : exported gitagent surface and command list
  • commands/
    : maintained slash-command compatibility shims
  • skills/*/SKILL.md
    : reusable workflows and domain playbooks
  • agents/*.md
    : delegated subagent role prompts
  • rules/
    : language and harness rules
  • hooks/README.md
    , 
    hooks/hooks.json
    , 
    scripts/hooks/
    : hook behavior and safety gates
  • manifests/install-*.json
    : selective install modules, components, profiles, and target support
  • docs/
    : harness guides, architecture notes, translated docs, release docs
  • README.md
    ：安装路径、卸载/重置指南、公开定位、常见问题解答
  • AGENTS.md
    ：贡献者指南和项目结构说明
  • agent.yaml
    ：导出的gitagent界面和命令列表
  • commands/
    ：维护的斜杠命令兼容性垫片
  • skills/*/SKILL.md
    ：可复用工作流和领域手册
  • agents/*.md
    ：委托子agent的角色提示
  • rules/
    ：语言和工具规则
  • hooks/README.md
    , 
    hooks/hooks.json
    , 
    scripts/hooks/
    ：hook行为和安全网关
  • manifests/install-*.json
    ：选择性安装模块、组件、配置文件和目标支持说明
  • docs/
    ：工具指南、架构说明、翻译文档、发布文档

Response Style

响应风格

Lead with the answer, then give the next action. Most users do not need a full catalog dump.
Good first response shape:
  1. what to use
  2. why it fits
  3. exact file or command to inspect
  4. one next command or question
Avoid:
  • listing every skill or command by default
  • repeating large README sections
  • recommending retired command shims when a skill-first path exists
  • claiming a component exists without checking the filesystem
  • replacing install guidance with manual copy commands when the managed installer supports the target
先给出答案，再说明下一步操作。大多数用户不需要完整的目录内容。
良好的初始响应结构：
  1. 应该使用什么组件
  2. 为什么它适合
  3. 要检查的具体文件或命令
  4. 一个具体的下一步命令或问题
需要避免：
  • 默认列出所有skill或command
  • 重复大段README内容
  • 当存在skill优先路径时，推荐已废弃的命令垫片
  • 在未检查文件系统的情况下声称某个组件存在
  • 当托管安装程序支持目标时，用手动复制命令替代安装指南

Common Tasks

常见任务

New User Onboarding

新用户入门

Give a short menu:
  • install or reset ECC
  • pick skills for a project
  • understand commands vs skills
  • inspect hooks and safety behavior
  • run a harness audit
  • find a specific workflow
Point to 
README.md
for install/reset and 
/project-init
for project-specific onboarding.
提供简短菜单：
  • 安装或重置ECC
  • 为项目选择合适的skills
  • 理解commands与skills的区别
  • 检查hooks和安全行为
  • 运行工具审计
  • 查找特定工作流
引导用户查看
README.md
获取安装/重置说明，查看
/project-init
获取项目专属入门指导。

Feature Discovery

功能发现

For "what should I use for X?":
  1. Search 
    skills/
    , 
    commands/
    , and 
    agents/
    .
  2. Prefer skills as the primary workflow surface.
  3. Use commands only when they are a maintained compatibility shim or a user explicitly wants slash-command behavior.
  4. Mention agents when delegation is useful.
Useful searches:
bash
rg -n "<query>" skills commands agents docs
find skills -maxdepth 2 -name SKILL.md | sort
对于“我应该用什么来完成X？”这类问题：
  1. 搜索
    skills/
    , 
    commands/
    , 和 
    agents/
    目录。
  2. 优先将skills作为主要工作流界面。
  3. 仅当commands是维护的兼容性垫片，或用户明确需要斜杠命令行为时才使用commands。
  4. 当需要委托任务时提及agents。
实用搜索命令：
bash
rg -n "<query>" skills commands agents docs
find skills -maxdepth 2 -name SKILL.md | sort

Install Guidance

安装指导

Use managed install paths:
bash
node scripts/install-plan.js --list-profiles
node scripts/install-plan.js --profile minimal --target claude --json
node scripts/install-apply.js --profile minimal --target claude --dry-run
For specific skill installs:
bash
node scripts/install-plan.js --skills <skill-id> --target claude --json
node scripts/install-apply.js --skills <skill-id> --target claude --dry-run
Warn users not to stack plugin installs and full manual/profile installs unless they intentionally want duplicate surfaces.
使用托管安装路径：
bash
node scripts/install-plan.js --list-profiles
node scripts/install-plan.js --profile minimal --target claude --json
node scripts/install-apply.js --profile minimal --target claude --dry-run
针对特定skill的安装：
bash
node scripts/install-plan.js --skills <skill-id> --target claude --json
node scripts/install-apply.js --skills <skill-id> --target claude --dry-run
提醒用户不要同时进行插件安装和完整手动/配置文件安装，除非他们故意想要重复的界面。

Project Onboarding

项目入门

Use 
/project-init
when the user wants ECC configured for a target repo. The expected sequence is:
  1. detect the stack from project files
  2. resolve a dry-run install plan
  3. inspect existing 
    CLAUDE.md
    and settings files
  4. ask before applying changes
  5. keep generated guidance minimal and repo-specific
当用户希望为目标仓库配置ECC时，使用
/project-init
。预期流程为：
  1. 从项目文件中检测技术栈
  2. 生成试运行安装计划
  3. 检查现有的
    CLAUDE.md
    和设置文件
  4. 在应用更改前询问用户
  5. 保持生成的指导内容简洁且针对仓库定制

Troubleshooting

故障排除

Ask for the target harness and install path first, then inspect:
  • plugin install metadata
  • .claude/
    , 
    .cursor/
    , 
    .codex/
    , 
    .gemini/
    , 
    .opencode/
    , 
    .codebuddy/
    , 
    .joycode/
    , or 
    .qwen/
  • hooks/hooks.json
  • install-state files
  • relevant command/skill files
For repo health, suggest:
bash
npm run harness:audit -- --format text
npm run observability:ready
npm test
首先询问用户目标工具和安装路径，然后检查：
  • 插件安装元数据
  • .claude/
    , 
    .cursor/
    , 
    .codex/
    , 
    .gemini/
    , 
    .opencode/
    , 
    .codebuddy/
    , 
    .joycode/
    , 或 
    .qwen/
    目录
  • hooks/hooks.json
    文件
  • 安装状态文件
  • 相关的command/skill文件
对于仓库健康检查，建议使用：
bash
npm run harness:audit -- --format text
npm run observability:ready
npm test

Output Templates

输出模板

Short Recommendation

简短推荐

text
Use <skill-or-command>. It fits because <reason>.

Canonical file: <path>
Verify with: <command>
Next: <one concrete action>
text
使用<skill或command>。它适合的原因是<理由>。

标准文件：<路径>
验证命令：<命令>
下一步：<一个具体操作>

Search Results

搜索结果

text
Best matches:
- <path>: <why it matters>
- <path>: <why it matters>

Recommendation: <which one to use first and why>
text
最佳匹配：
- <路径>：<它的重要性>
- <路径>：<它的重要性>

推荐：<优先使用哪一个及原因>

Install Plan Summary

安装计划摘要

text
Detected: <stack evidence>
Target: <harness>
Plan: <profile/modules/skills>
Dry run: <command>
Would change: <paths>
Needs approval before apply: <yes/no>
text
检测到：<技术栈依据>
目标：<工具>
计划：<配置文件/模块/skills>
试运行：<命令>
将更改：<路径>
应用前需要确认：<是/否>

Related Surfaces

相关界面

  • /project-init
    : stack-aware onboarding plan for a target repo
  • /harness-audit
    : deterministic readiness scorecard
  • /skill-health
    : skill quality review
  • /skill-create
    : generate a new skill from local git history
  • /security-scan
    : inspect Claude/OpenCode configuration security
  • /project-init
    ：针对目标仓库的技术栈感知入门计划
  • /harness-audit
    ：确定性就绪度评分卡
  • /skill-health
    ：skill质量审查
  • /skill-create
    ：从本地git历史生成新skill
  • /security-scan
    ：检查Claude/OpenCode配置安全性