update-refs
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseUpdate References
更新引用
Ensure naming and documentation consistency across all codebase locations.
确保代码库所有位置的命名与文档一致性。
Checklist
检查清单
When updating terminology, feature names, descriptions, or counts, check ALL locations:
在更新术语、功能名称、描述或数量时,需检查所有以下位置:
1. User-Facing Messages
1. 用户可见消息
| Location | What to Check |
|---|---|
| Welcome banner text, feature descriptions |
| Pilot CLI help text and messages |
| Installer CLI help text, prompts |
| Post-install instructions |
| UI banner and status messages |
| 位置 | 检查内容 |
|---|---|
| 欢迎横幅文本、功能描述 |
| Pilot CLI帮助文本与提示消息 |
| 安装器CLI帮助文本、提示信息 |
| 安装后说明文档 |
| UI横幅与状态消息 |
2. Documentation & Website
2. 文档与网站
| Location | What to Check |
|---|---|
| Feature descriptions, usage examples, counts (rules, hooks, skills, commands) |
| SEO meta tags, page title, structured data |
| SEO description, structured data counts |
| Stats bar counts (rules, hooks, skills, LSPs, MCP) |
| Feature cards, descriptions, item counts |
| Under the Hood subtitle counts, hooks pipeline, rules categories |
| /spec workflow details, All Commands grid |
| Before & After comparison table |
| Standard plan feature counts, value proposition |
| Installation instructions |
| Footer links |
| Navigation links |
| 位置 | 检查内容 |
|---|---|
| 功能描述、使用示例、数量统计(规则、钩子、Skill、命令) |
| SEO元标签、页面标题、结构化数据 |
| SEO描述、结构化数据统计 |
| 统计栏数据(规则、钩子、Skill、LSP、MCP) |
| 功能卡片、描述、项目数量 |
| 底层原理副标题统计、钩子流水线、规则分类 |
| /spec工作流详情、全命令网格 |
| 前后对比表格 |
| 标准版功能数量、价值主张 |
| 安装说明 |
| 页脚链接 |
| 导航链接 |
3. Package & Install
3. 包与安装
| Location | What to Check |
|---|---|
| Package name, description, metadata |
| Shell installer script messages |
| Package docstring |
| 位置 | 检查内容 |
|---|---|
| 包名称、描述、元数据 |
| Shell安装脚本消息 |
| 包文档字符串 |
4. Claude Configuration (Plugin Source)
4. Claude配置(插件源)
| Location | What to Check |
|---|---|
| Command descriptions in frontmatter ( |
| Skill descriptions in frontmatter |
| Standard rules content |
| Hook configuration and event triggers |
| Hook script messages and logic |
| Sub-agent definitions (plan-verifier, spec-verifier) |
| LSP server configuration |
| Language mode definitions |
| 位置 | 检查内容 |
|---|---|
| 命令描述前置内容( |
| Skill描述前置内容 |
| 标准规则内容 |
| 钩子配置与事件触发器 |
| 钩子脚本消息与逻辑 |
| 子Agent定义(plan-verifier、spec-verifier) |
| LSP服务器配置 |
| 语言模式定义 |
5. Project-Level Claude Config
5. 项目级Claude配置
| Location | What to Check |
|---|---|
| Project-specific rules (git-commits.md, project.md) |
| Project-specific skills (lsp-cleaner, pr-review, update-refs) |
| 位置 | 检查内容 |
|---|---|
| 项目特定规则(git-commits.md、project.md) |
| 项目特定Skill(lsp-cleaner、pr-review、update-refs) |
No Hardcoded Counts
禁止硬编码数量
Do NOT add specific counts (e.g., "22 rules", "7 hooks", "14 skills") to user-facing text.
The project deliberately avoids quantity-focused messaging. Use qualitative descriptions instead:
| ❌ Don't | ✅ Do |
|---|---|
| "22 rules loaded every session" | "Production-tested rules loaded every session" |
| "7 hooks auto-lint on every edit" | "Hooks auto-lint, format, type-check on every edit" |
| "14 coding skills" | "Coding skills activated dynamically" |
| "5 MCP servers + 3 LSP servers" | "MCP servers + language servers pre-configured" |
| "2,900+ lines of best practices" | "Production-tested best practices" |
Why: Quality over quantity. Counts become stale and create maintenance burden across many files. The value is in what the system does, not how many components it has.
请勿在用户可见文本中添加具体数量(如“22条规则”、“7个钩子”、“14个Skill”)。
本项目刻意避免以数量为导向的表述,应改用定性描述:
| ❌ 错误示例 | ✅ 正确示例 |
|---|---|
| “每次会话加载22条规则” | “每次会话加载经过生产环境验证的规则” |
| “7个钩子在每次编辑时自动 lint” | “钩子在每次编辑时自动lint、格式化、类型检查” |
| “14个编码Skill” | “编码Skill动态激活” |
| “5个MCP服务器 + 3个LSP服务器” | “预配置MCP服务器 + 语言服务器” |
| “2900+行最佳实践” | “经过生产环境验证的最佳实践” |
原因: 质量优先于数量。具体数量会随时间过时,并增加多文件维护负担。系统的价值在于其功能,而非组件数量。
Workflow
工作流
-
Search first - Use Grep to find all occurrences:
Grep pattern="old term" glob="*.{md,py,tsx,json,ts}" -
Update systematically - Work through checklist above, section by section
-
Verify consistency - Search again to confirm no misses:
Grep pattern="old term" glob="*.{md,py,tsx,json,ts}" -
Build website - Verify site compiles after changes:bash
cd docs/site && npm run build
-
先搜索 - 使用Grep查找所有匹配项:
Grep pattern="旧术语" glob="*.{md,py,tsx,json,ts}" -
系统化更新 - 按上述清单逐部分处理
-
验证一致性 - 再次搜索确认无遗漏:
Grep pattern="旧术语" glob="*.{md,py,tsx,json,ts}" -
构建网站 - 修改后验证站点可正常编译:bash
cd docs/site && npm run build
Common Updates
常见更新场景
| Change Type | Key Locations |
|---|---|
| Command rename/add | pilot/commands/*.md, README.md, WorkflowSteps.tsx, WhatsInside.tsx, counts table |
| Skill rename | pilot/skills/*/SKILL.md, README.md, WhatsInside.tsx, DeepDiveSection.tsx |
| Rule add/remove | pilot/rules/*.md, README.md, all count locations (see table above) |
| Hook change | pilot/hooks/hooks.json, pilot/hooks/*.py, DeepDiveSection.tsx, README.md |
| Feature description | launcher/banner.py, README.md, site components, Index.tsx structured data |
| Workflow change | pilot/commands/.md, pilot/rules/.md, README.md, WorkflowSteps.tsx |
| Package rename | pyproject.toml, install.sh, launcher/init.py, README.md |
| Installer message | installer/.py, installer/steps/.py |
| Terminology change | Search all locations in checklist above — grep for old term, replace everywhere |
| 变更类型 | 关键位置 |
|---|---|
| 命令重命名/新增 | pilot/commands/*.md、README.md、WorkflowSteps.tsx、WhatsInside.tsx、统计表格 |
| Skill重命名 | pilot/skills/*/SKILL.md、README.md、WhatsInside.tsx、DeepDiveSection.tsx |
| 规则新增/移除 | pilot/rules/*.md、README.md、所有统计位置(见上表) |
| 钩子变更 | pilot/hooks/hooks.json、pilot/hooks/*.py、DeepDiveSection.tsx、README.md |
| 功能描述更新 | launcher/banner.py、README.md、站点组件、Index.tsx结构化数据 |
| 工作流变更 | pilot/commands/.md、pilot/rules/.md、README.md、WorkflowSteps.tsx |
| 包重命名 | pyproject.toml、install.sh、launcher/init.py、README.md |
| 安装器消息更新 | installer/.py、installer/steps/.py |
| 术语变更 | 搜索清单中所有位置 —— 用grep查找旧术语并全局替换 |