mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-06-11 18:53:11 +08:00
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
48 lines
1.1 KiB
Markdown
48 lines
1.1 KiB
Markdown
# 效能優化
|
||
|
||
## 模型選擇策略
|
||
|
||
**Haiku 4.5**(Sonnet 90% 能力,3 倍成本節省):
|
||
- 頻繁呼叫的輕量 agents
|
||
- 配對程式設計和程式碼產生
|
||
- 多 agent 系統中的 worker agents
|
||
|
||
**Sonnet 4.6**(最佳程式碼模型):
|
||
- 主要開發工作
|
||
- 協調多 agent 工作流程
|
||
- 複雜程式碼任務
|
||
|
||
**Opus 4.6**(最深度推理):
|
||
- 複雜架構決策
|
||
- 最大推理需求
|
||
- 研究和分析任務
|
||
|
||
## 上下文視窗管理
|
||
|
||
避免在上下文視窗的最後 20% 進行:
|
||
- 大規模重構
|
||
- 跨多個檔案的功能實作
|
||
- 除錯複雜互動
|
||
|
||
較低上下文敏感度任務:
|
||
- 單檔案編輯
|
||
- 獨立工具建立
|
||
- 文件更新
|
||
- 簡單 Bug 修復
|
||
|
||
## Ultrathink + Plan 模式
|
||
|
||
對於需要深度推理的複雜任務:
|
||
1. 使用 `ultrathink` 增強思考
|
||
2. 啟用 **Plan 模式** 以結構化方法
|
||
3. 用多輪批評「預熱引擎」
|
||
4. 使用分角色子 agents 進行多元分析
|
||
|
||
## 建置疑難排解
|
||
|
||
如果建置失敗:
|
||
1. 使用 **build-error-resolver** Agent
|
||
2. 分析錯誤訊息
|
||
3. 增量修復
|
||
4. 每次修復後驗證
|