One feature, tested, reviewed and merged in a night.
How you do anything is how you do everything.

Tonight we change it without breaking it.
AI ExchangeBuilding Phoenix's AI community, together. Workuity hosts tonight, and we present Founder Weekend side by side.
What's in your fridge?
Favorites · 3 saved
"I had to scroll my history to find it."
Keep the dinners I'd make again one tap away.
Saved dinner shows at the top of Favorites
Saving twice keeps one copy
Another account can't see mine
Vitest for the logic, Playwright for the flow.
youHere are eleven notes from testers.
claudeThree ask to save dinners. One asks for meal plans.
claudeFavorites fits the one job. Meal plans can wait.
✓ Pick: Favorites
Read SPEC.md and FEEDBACK.md, group the notes, check each group against the one job, and recommend one feature. No code yet.
claudeShould saving twice keep two copies?
youNo. One copy.
claudeCan someone favorite from their history?
youYes, every card gets a heart.
✓ Added Feature: Favorites to SPEC.md
Interview me about Favorites, then add a Feature section to SPEC.md with acceptance criteria and a test plan. Wait for my OK.
Two runners, one for logic and one for the whole flow.
Fast checks for the logic in lib/.
A real browser, sized like an iPhone.
Tests run after every edit Claude makes.
Install Vitest, have me run npm init playwright@latest, add an iPhone 13 project, then add a hook that runs the tests after every edit.
code.claude.com/docs/en/hooks-guide
claudeSeams: lib/favorites.ts and the Favorites screen. OK?
youOK.
✗ toggles a favorite on (not implemented)
claudeRed. Ready to write the code?
Install mattpocock-skills if needed, use the tdd skill, agree the seams with me, then write one failing Vitest test and one failing Playwright test.
github.com/mattpocock/skills
✓ favorites table created
✓ toggles a favorite on and off
✓ saving twice keeps one copy
claudeSlice 2 of 4: the heart on each card.
On a feature/favorites branch, list the slices, then build each one red to green, commit, and wait for me before the next.
Run Playwright on iPhone 13, map every acceptance criterion to a test, then give me a short list to check by hand at phone width.
claudeStarting a fresh subagent with only the spec and the diff.
! DELETE /api/favorites/[id] doesn't check the owner
✓ Fixed, with a test for it
Start a fresh subagent with only SPEC.md and the diff, review it against the feature, then verify and fix each real finding test first.
code.claude.com/docs/en/sub-agents · or type /code-review
✓ PR #4 Favorites opened
✓ Vercel preview ready
claudeChecks green. Open the preview on your phone, then say merge.
Set preview env vars and Better Auth origins, run Vitest and Playwright in GitHub Actions, open the PR, check the preview, ask before merging.
Next talk: Digital Presence, a public face for What's for Dinner.
An Arizona AI hackathon. Teams of 1-4.
See the hackathon ↗