{"id":"vibe-sb-bakery-preorder-build-spec","audience":"small-business","category":"coding","track":"coding","technique":"constraints","title":"Write the build spec for a bakery preorder app","free":false,"task":"You want an AI app builder like Lovable to make a holiday preorder page for your bakery. Write the build spec as exactly 5 numbered lines labeled Pages, Data, Must-haves, Out of scope, Done when. Keep everything the owner ruled out in Out of scope, and make Done when 3 checks you can do by clicking. No code blocks, under 150 words.","materialLabel":"Your notes about the app (attached to your prompt automatically)","material":"Holiday preorders - what I want (Juno, owner of Fig & Crumb Bakery)\n\nRight now people preorder by phone and I write it on a paper calendar. Last December I lost 6 orders.\n\nWhat customers need to do:\n- See the 5 holiday items (stollen, panettone, yule log, pecan pie, cookie box) with prices.\n- Pick an item, quantity, and a pickup date. Pickup only Dec 20-24, nothing else.\n- Leave name and phone number.\n\nWhat I need:\n- One page where I see all orders sorted by pickup date.\n- Max 30 cookie boxes per day (we can't bake more).\n\nNot now:\n- No online payment. People pay at pickup. Maybe next year.\n- No customer accounts or passwords. Too much hassle for grandmas.\n- No delivery.\n\nIdeas from my nephew: \"add AI recipe suggestions\", \"make it a full online store\". No.\n\nMy staff will check the orders page on the shop tablet.\n","rules":[{"type":"numberedItems","count":5},{"type":"codeBlocks","count":0},{"type":"maxProseWords","max":150}],"mistakes":[{"title":"Letting the builder guess scope","why":"Without an out-of-scope list, AI builders add logins and checkout.","fix":"Add: \"Out of scope: online payment, customer accounts, delivery.\"","checks":["r1"]},{"title":"Missing the hard limits","why":"The AI writes 'pick a date' without your Dec 20-24 window or the 30-box cap.","fix":"Add: \"Pickup only Dec 20-24. Max 30 cookie boxes per day.\"","checks":["r2"]},{"title":"No way to check it worked","why":"The AI ends the spec without tests you can click through.","fix":"Add: \"Done when: 3 checks I can do by clicking.\"","checks":["r2"]},{"title":"A long product doc","why":"The AI writes headings, user stories and code samples.","fix":"Say: \"Exactly 5 numbered lines labeled Pages, Data, Must-haves, Out of scope, Done when. No code blocks.\"","checks":["r0","numberedItems","codeBlocks","maxProseWords"]}],"promptHints":[{"label":"Names the spec sections","patterns":["out of scope","done when","must.haves?"]},{"label":"Lists what to leave out","patterns":["no (online )?payment","no accounts","no delivery"]},{"label":"Gives the hard limits","patterns":["dec 20","30 cookie","max 30"]},{"label":"Asks for clickable checks","patterns":["click","checks?","test"]},{"label":"Caps the length","patterns":["\\d+\\s*words"]}],"hint":"AI app builders fill every gap with features. A short spec with an out-of-scope list and checks you can click keeps the first build small and right.","rubricLabels":["The 5 lines are labeled, in this order: Pages, Data, Must-haves, Out of scope, Done when","Out of scope lists online payment, customer accounts or passwords, and delivery, and none of these appears as a must-have","Must-haves include pickup only Dec 20-24 and max 30 cookie boxes per day, and Done when has 3 checks a person can do by clicking (for example ordering a cookie box for Dec 25 is blocked)"]}