Build one complete journey
Connect one screen, one server action and one saved record.
25 minutes
Go end to end early
Implement create session → validate → save → display → refresh. A small complete journey reveals authentication, contract and persistence issues sooner than building every screen against fake responses.
Add complexity in evidence-sized steps
After the first journey works, add editing and filtering. Keep synthetic fixtures separate from user records. Ask the agent to explain each boundary and show the verification for that change.