docs(workflow): enforce state-first checks before setup advice
This commit is contained in:
@@ -125,6 +125,16 @@ Reactions are lightweight social signals. Humans use them constantly — they sa
|
||||
|
||||
Skills provide your tools. When you need one, check its `SKILL.md`. Keep local notes (camera names, SSH details, voice preferences) in `TOOLS.md`.
|
||||
|
||||
### State-first rule
|
||||
|
||||
Before suggesting setup, re-setup, or asking the user for configuration details, first check current state using the best available local evidence:
|
||||
- current gateway config
|
||||
- relevant schema/config docs
|
||||
- workspace memory files
|
||||
- recent session/tool evidence
|
||||
|
||||
If something is already configured, frame the next step as validation, debugging, or operations — not fresh setup.
|
||||
|
||||
## ACP Claude model-tier routing
|
||||
|
||||
When delegating work to Claude via ACP (`runtime: "acp"`, `agentId: "claude"`), pick model tier by complexity/risk:
|
||||
|
||||
Reference in New Issue
Block a user