Flows workflow logoFlows
Tool Descriptions That Steer the Model
0/3 steps0%

Step 1 of 3

Collect misroutes and map overlaps

Fix the confusions you actually have, not hypothetical ones.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Gather the evidence. From recent transcripts, collect every tool misroute: cases where the model used tool A when tool B was correct (shell grep instead of the search tool, full-file write instead of targeted edit, web search for local questions). Then map the overlap structure of my toolset: which tools can plausibly handle the same request? For each overlapping pair, write the one-sentence boundary rule (e.g. 'edit for changes within a file; write only for new files or full regenerations'). Deliver the misroute list and the boundary rules - these drive every rewrite.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A misroute inventory plus boundary rules for every overlapping pair.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent