Step 1
Define goals & context
Give AI the goal, relevant files, and constraints before work begins.
Link the workspace files, note what must stay unchanged, and write a clear outcome so the agent knows what “done” looks like before any edit starts.
Describe the outcome, watch the plan take shape, and keep every edit visible before you ship.
Describe the change…
Coding & Development lifecycle
The same coding loop as the homepage, ordered so model choice and analysis happen before execution, and review always comes before handoff.
Step 1
Give AI the goal, relevant files, and constraints before work begins.
Link the workspace files, note what must stay unchanged, and write a clear outcome so the agent knows what “done” looks like before any edit starts.
Step 2
Choose a model for the task, from an initial draft to a focused review.
Route to a faster model for drafts, a balanced one for implementation, or a deeper one for review. The choice sits next to the task so you always know what is running.
Step 3
Read the relevant code and connect the proposed edit to your goal.
The agent reads linked context, surfaces goals and constraints, and outlines the smallest safe plan — still before anything is applied to your branch.
Step 4
Keep code edits, debugging, and test feedback in the same workflow.
Follow the draft as it lands: file reads, edits, and focused tests stay in one thread so you can interrupt, redirect, or continue without losing the trail.
Step 5
Inspect the changes and results, then refine what needs another pass.
Inspect the diff at the review gate. Nothing merges or applies until you accept, request changes, or roll back to a recoverable checkpoint.
Step 6
Leave a clear summary of the changes, results, and next step.
Leave a clear handoff: what changed, what passed, and what still needs a human eye — so the next person (or the next step) can pick up without rebuilding context.
Concrete scenarios
Start from the goal, generate the first structure, then refine with context in view.
Keep the failing path, the hypothesis, and the fix attempt in one thread.
Summarize what changed and why — then pause for your judgment before handoff.
Add empty-cart copy and keep the CTA reachable.
FAQ