Define the smallest useful build
Start with one user and one task. Write the inputs, outputs, empty state, and three acceptance checks. Choose a small project such as a reading-list page. Leave authentication, payments, and real personal data out of the first exercise.
Your activity
Write a brief for a reading list with add, mark-read, and delete actions. Decide whether the list is temporary or stored locally and make that visible to the user.
A one-page build brief with three testable acceptance criteria.
Check your work
Can you explain the decisions you made? What did you verify? Identify one remaining uncertainty and one improvement before moving on.
Build one behavior at a time
Ask the coding assistant to explain its plan and the files it will touch. Have it implement one behavior, then inspect the change. Ask for plain-language explanations of unfamiliar code. Keep a working version in version control before continuing.
Your activity
Build the add-book action first. Try an empty title, a very long title, and a normal title. Fix the concrete failures before adding the next behavior.
A small working prototype and a record of changes you understand.
Check your work
Can you explain the decisions you made? What did you verify? Identify one remaining uncertainty and one improvement before moving on.
Test, fix, and explain
Generated code needs review. Check user-visible behavior, keyboard access, mobile layout, error states, and data handling. Ask the assistant to diagnose from actual error messages. Never paste private credentials into prompts or put server secrets in browser code.
Your activity
Work through your acceptance checks. Record actual results, fix one issue at a time, and write how to run the project from a clean checkout.
A tested prototype with setup instructions and known limitations.
Check your work
Can you explain the decisions you made? What did you verify? Identify one remaining uncertainty and one improvement before moving on.