chore: add gstack skill routing rules to CLAUDE.md

This commit is contained in:
陈少杰 2026-04-16 19:57:22 +08:00
parent 9753635370
commit a5fd95af82
1 changed files with 20 additions and 0 deletions

View File

@ -122,3 +122,23 @@ QUANT_BACKTEST_PATH=/path/to/quant_backtest python orchestrator/examples/run_liv
- `orchestrator/tests/` - Orchestrator 单元测试
- `tests/` - TradingAgents 核心测试
- 使用 pytest 运行:`python -m pytest orchestrator/tests/`
## Skill routing
When the user's request matches an available skill, ALWAYS invoke it using the Skill
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
The skill has specialized workflows that produce better results than ad-hoc answers.
Key routing rules:
- Product ideas, "is this worth building", brainstorming → invoke office-hours
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
- Ship, deploy, push, create PR → invoke ship
- QA, test the site, find bugs → invoke qa
- Code review, check my diff → invoke review
- Update docs after shipping → invoke document-release
- Weekly retro → invoke retro
- Design system, brand → invoke design-consultation
- Visual audit, design polish → invoke design-review
- Architecture review → invoke plan-eng-review
- Save progress, checkpoint, resume → invoke checkpoint
- Code quality, health check → invoke health