Files
everything-claude-code/docs/zh-CN/rules/common/performance.md
konstapukarifastnetfi 8b24f63ede fix: refresh stale technical content in agents, rules, and skills (#2168)
Several published examples contained APIs that no longer exist, code that
does not run, or model versions that drifted from reality:

- agents/performance-optimizer.md used the web-vitals v3 API
  (getCLS/getFID/getLCP/getFCP/getTTFB) and reported FID. web-vitals v4
  renamed the imports to onCLS/onINP/onLCP/onFCP/onTTFB and FID was
  replaced by INP (target < 200ms)
- rules/common/performance.md pinned stale model versions in the
  model-selection guidance; refresh to the versions the repo itself uses
  (agent.yaml pins claude-opus-4-6) and add the PowerShell variant for
  MAX_THINKING_TOKENS next to the bash export
- skills/python-patterns/SKILL.md: both get_value examples referenced
  default_value without declaring the parameter (NameError); add
  default_value: Any = None to the EAFP and LBYL signatures
- skills/frontend-patterns/SKILL.md: the custom useQuery example rebuilt
  refetch whenever callers passed inline fetchers/options, re-triggering
  the effect after every state update (infinite fetch loop). Keep the
  latest fetcher/options in refs so refetch stays referentially stable.
  The PASS-labelled useMemo example mutated its input with in-place sort;
  copy before sorting
- skills/coding-standards/SKILL.md repeated the same PASS-labelled
  in-place-sort-in-useMemo example; same fix
- rules/typescript/security.md used a vendor-specific OPENAI_API_KEY in
  generic guidance; switch to a neutral API_KEY

Every hand-maintained copy of the affected content is synced in the same
change: locale mirrors (ja-JP, ko-KR, pt-BR, tr, zh-CN, zh-TW - each only
where it carries the affected file) and the .agents/.kiro/.cursor harness
mirrors. Two structural divergences are left alone and noted here:
.kiro/steering/performance.md has no extended-thinking control list to
carry the PowerShell variant, and docs/zh-TW/rules/performance.md keeps an
older condensed thinking section without the budget-cap line.
rules/zh/performance.md is intentionally untouched - the rules/zh tree is
being retired in a separate change
2026-06-07 13:26:01 +08:00

1.5 KiB
Raw Blame History

性能优化

模型选择策略

Haiku 4.5 (具备 Sonnet 90% 的能力,节省 3 倍成本):

  • 频繁调用的轻量级智能体
  • 结对编程和代码生成
  • 多智能体系统中的工作智能体

Sonnet 4.6 (最佳编码模型):

  • 主要的开发工作
  • 编排多智能体工作流
  • 复杂的编码任务

Opus 4.6 (最深的推理能力):

  • 复杂的架构决策
  • 最高级别的推理需求
  • 研究和分析任务

上下文窗口管理

避免使用上下文窗口的最后 20% 进行:

  • 大规模重构
  • 跨多个文件的功能实现
  • 调试复杂的交互

上下文敏感性较低的任务:

  • 单文件编辑
  • 创建独立的实用工具
  • 文档更新
  • 简单的错误修复

扩展思考 + 计划模式

扩展思考默认启用,最多保留 31,999 个令牌用于内部推理。

通过以下方式控制扩展思考:

  • 切换Option+T (macOS) / Alt+T (Windows/Linux)
  • 配置:在 ~/.claude/settings.json 中设置 alwaysThinkingEnabled
  • 预算上限export MAX_THINKING_TOKENS=10000bash$env:MAX_THINKING_TOKENS = "10000"PowerShell
  • 详细模式Ctrl+O 查看思考输出

对于需要深度推理的复杂任务:

  1. 确保扩展思考已启用(默认开启)
  2. 启用 计划模式 以获得结构化方法
  3. 使用多轮批判进行彻底分析
  4. 使用分割角色子代理以获得多元视角

构建故障排除

如果构建失败:

  1. 使用 build-error-resolver 智能体
  2. 分析错误信息
  3. 逐步修复
  4. 每次修复后进行验证