Skip to main content
Start with a selected project and the commands recorded in EMBEDDER.md. Treat implementation, build, programming, and runtime behavior as separate checks.

​
Set up the project

Run /project to select or create a project. Choose the target platform, review fitted peripherals with /peripheral, and add schematics when you need board connections. Run /init and confirm the detected commands and hardware. See Quickstart for the full setup flow.

​
Plan an uncertain change

Run /plan, then describe the behavior and constraints:
Review affected files, assumptions, error handling, and verification. Approve the plan to start implementation in Act mode. For a focused fix, use Act directly:

​
Build and test

Check that the output belongs to the current build. Resolve the first useful error before continuing to hardware.

​
Flash and observe

Identify the board, probe or bridge, power setup, and serial connection. Then ask:
Use history when the message may already be captured. Use live monitoring when you need to wait for it. An open Monitor tab alone does not establish that the expected message appeared.

​
Investigate a failure

Use /debug for GDB state inspection or bounded instruction and coverage captures. Begin with existing output and preserve the target when its current state matters.
For electrical or timing questions, request a bounded instrument capture with channel assignments and an expected result. Use hardware scripts to repeat the check.

​
Review the outcome

Ask for the changed behavior, files, checks run, and any unresolved limits. A build proves compilation; a flash verifies programming; the runtime test establishes the requested board behavior. Keep reusable commands in EMBEDDER.md and confirmed constraints in project memory.

​
Continue or change direction

Send a follow-up in the same conversation for related work. During a run it steers the active turn at the next step boundary. Messages not yet absorbed wait in the queue; review or remove obsolete queued messages before switching tasks. Use /btw for a side question and /new in VS Code for unrelated work. See Sessions and context.
Last modified on September 18, 2026