chore: add gstack skill routing rules to CLAUDE.md
This commit is contained in:
35
CLAUDE.md
Normal file
35
CLAUDE.md
Normal file
@@ -0,0 +1,35 @@
|
|||||||
|
# ATM — Automated Trading Monitor
|
||||||
|
|
||||||
|
Personal Faza-1 tool for the M2D strategy. Python 3.11+.
|
||||||
|
|
||||||
|
## Quick Reference
|
||||||
|
|
||||||
|
```bash
|
||||||
|
pip install -e ".[windows]" # Windows: live capture
|
||||||
|
pip install -e . # Linux/macOS: dev/dryrun only
|
||||||
|
atm calibrate # Tk wizard
|
||||||
|
atm debug --delay 5 # one-shot capture + detect
|
||||||
|
atm run --start-at 16:30 --stop-at 23:00 # live session
|
||||||
|
atm dryrun samples # corpus gate
|
||||||
|
pytest # run 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
|
||||||
Reference in New Issue
Block a user