<✦>aicodedesign.Start building

LESSON 02 OF 03 · WRITTEN GUIDE

Work in small, reviewable steps

Small changes are easier to inspect and reverse. Ask for one complete user outcome rather than a large list of unrelated improvements. Keep a recoverable version before changing behavior, and review the changes before accepting them.

Make it practical

Create a checkpoint in version control. Ask for one task, inspect the changed files, run the relevant checks, and try the interaction. Write down what changed and why before moving to the next task.

TRY THIS PROMPT

Implement the editable note using the existing conventions. Keep this change limited to the note flow. Summarize the files changed, assumptions made, and checks performed. Flag any unverified behavior.

Check your work

Can you explain the change in one sentence? Are unrelated files untouched? Does the original add-book flow still work?

Keep the human in the loop.

Use the output as a draft. Compare it with the brief, inspect the work, and keep the decisions you can explain.

Next lesson