Build my first project: Bouquet Recipe Card What: I run Stem Room, a wedding flower studio. I design the bouquets, my assistant packs them, and we buy roses in whole bunches from the morning market. When: We added two bouquets before a Saturday wedding. I counted the extra roses in stems but forgot the grower sells by the bunch, so the assistant had to make another trip. Where: The trouble shows up at the worktable when the recipe card, the buckets we already have and the handwritten market list all show different quantities. Why: Roses are expensive and perishable. I want the buyer to have the right market order and the maker to see exactly how many stems are left after the bouquets. How: I would trust a flower order when changing the bouquet count updates both the stem total and the number of whole bunches to buy. I'd like it to feel like a studio recipe card. The project I chose: Bouquet Recipe Card What I want to prove: For the rose recipe use five stems per bouquet, eight usable stems on hand and ten stems per market bunch. Six bouquets need three new bunches. Eight bouquets need four. Show required stems, whole bunches to buy and leftovers after making the bouquets. Interview me before building Read my original interview, chosen project, business rules and acceptance checks. Review the report, app files and examples I have supplied. Start from what you already know about my business and carry my decisions forward. Open our conversation with the business or design decision that would most improve the result. Handle installation and publishing when we reach those steps. Interview me to get everything you need to build the best result for my business. Explore who will use it, what they need to accomplish, what happens in practice, which decisions and exceptions matter, how the app should look and feel, and what a successful outcome looks like. Explore data, permissions, devices and integrations where they affect the work. Follow my answers wherever they reveal something important. Ask for concrete examples, discuss trade-offs in my language, and resolve gaps or conflicting requirements with me. Continue the interview for as many rounds as the project needs. Use fictional or redacted examples when discussing actual work. Once you understand the outcome, summarize how the app will work in a representative case and what will count as success. Carry my answers into the design, business rules and acceptance checks, then build and test that workflow. Getting started I am starting from scratch. If this workspace can build and run the app, start here. If setup is needed, ask which device I use if you cannot tell, and guide me one step at a time. Build instructions To create the Bouquet Recipe Card project, start by designing the first screen around the object the business already works with, which is the recipe card. The user of this object is the owner of Stem Room, the wedding flower studio. The fields on this object include the number of bouquets, stems per bouquet, usable stems on hand, and stems per market bunch. The action that changes the state of this object is when the owner updates the number of bouquets, which then calculates the required stems, whole bunches to buy, and leftovers. Use the approved brand colour #AD3651 and create a typographic identity for the sample business. Pick typography, spacing, materials, and imagery that suit the trade. Include a second working view when there is a genuine handoff or saved record to reopen. Keep engineering checks, the sales pitch, and build instructions outside the operator interface. The initial screen should display the current recipe card with the number of bouquets, stems per bouquet, usable stems on hand, and stems per market bunch. The owner can then update the number of bouquets, and the system will calculate the required stems, whole bunches to buy, and leftovers. For example, if the owner updates the number of bouquets to 6, the system will calculate that 3 new bunches are needed. If the owner updates the number of bouquets to 8, the system will calculate that 4 new bunches are needed. The system should also show the required stems, whole bunches to buy, and leftovers after making the bouquets. For instance, for 6 bouquets, the required stems are 30, whole bunches to buy are 3, and leftovers are 8. The system should be able to handle different scenarios, such as when the owner wants to add or remove ingredients from the recipe card, and update the quantities accordingly. The system should also be able to handle exceptions, such as when the owner wants to make a bouquet with a different number of stems per bouquet. In terms of accessibility, the system should be easy to use and navigate, with clear and concise instructions and feedback. The system should also be able to handle different devices and screen sizes, and be compatible with different browsers and operating systems. Overall, the Bouquet Recipe Card project should be designed to make it easier for the owner to update and manage their bouquet designs, and to ensure that the buyer has the right market order and the maker sees exactly how many stems are left after the bouquets. Workflow examples that must pass Enter the number of bouquets, stems per bouquet, usable stems on hand, and stems per market bunch → Calculate required stems, whole bunches to buy, and leftovers (stage = Before calculation, bouquets = 6, stems_per_bouquet = 5, usable_stems_on_hand = 8, stems_per_market_bunch = 10) Calculate the required stems, whole bunches to buy, and leftovers for 6 bouquets → 3 new bunches are needed (stage = After calculation, bouquets = 6, stems_per_bouquet = 5, usable_stems_on_hand = 8, stems_per_market_bunch = 10) Calculate the required stems, whole bunches to buy, and leftovers for 8 bouquets → 4 new bunches are needed (stage = After calculation, bouquets = 8, stems_per_bouquet = 5, usable_stems_on_hand = 8, stems_per_market_bunch = 10) Show the required stems, whole bunches to buy, and leftovers after making the bouquets → Required stems: 30, whole bunches to buy: 3, leftovers: 8 (stage = After calculation, bouquets = 6, stems_per_bouquet = 5, usable_stems_on_hand = 8, stems_per_market_bunch = 10) Design My chosen brand colour is #AD3651. Use it consistently as an accent, provide a readable foreground on every surface, and keep important status differences understandable without colour alone. Use the approved brand colour #AD3651 and a typographic identity for the sample business Design the first screen around an object this business already works with and the decision someone makes from it. Name that object, its user, its fields, and the action that changes its state. Give it visual weight and use the owner's vocabulary. Use the approved brand colour and any supplied logo; otherwise create a typographic identity for the sample business. Pick typography, spacing, materials and imagery that suit the trade. Include a second working view when there is a genuine handoff or saved record to reopen. Keep engineering checks, the sales pitch and build instructions outside the operator interface. Recommended technology - Frontend: user interface to input and display data - Backend: calculations and data storage Acceptance checks - Enter the number of bouquets, stems per bouquet, usable stems on hand, and stems per market bunch → Calculate required stems, whole bunches to buy, and leftovers - Calculate the required stems, whole bunches to buy, and leftovers for 6 bouquets → 3 new bunches are needed - Calculate the required stems, whole bunches to buy, and leftovers for 8 bouquets → 4 new bunches are needed - Show the required stems, whole bunches to buy, and leftovers after making the bouquets → Required stems: 30, whole bunches to buy: 3, leftovers: 8 - For 6 bouquets, 3 new bunches are needed - For 8 bouquets, 4 new bunches are needed - Show required stems, whole bunches to buy, and leftovers after making the bouquets Preview and handoff Use fictional sample records and let me try the complete first task. Explain what you actually tested and what remains to verify. Give me the source files and show me how to reopen the app locally. Then offer the Cloudflare publishing steps below. From the demo to my application After I can try the demo, tell me which checks passed and what still needs testing. Ask me: “Would you like me to build this application from this demo?” Wait for my answer. If I reply “Yes, build this application”, or clearly agree, start implementing the first usable version in this coding workspace. Carry forward the approved design, workflow, source files and acceptance checks. Keep the demo available as a reference. If implementation reveals a gap, return to the interview and work through it with me. My yes authorizes building and testing. Get separate approval before publishing, enabling charges, connecting live accounts or customer data, or sending real messages. Put my finished app online with Cloudflare Once the first app passes its checks, offer to publish this exact version at a free workers.dev address I can open on my phone or share. Tell me the link will be public, show the proposed project name and sample records, and ask whether I want to publish now. A local build can stay local if I decline. Use my own Cloudflare account. If I am new, guide me through creating a free account at https://dash.cloudflare.com/, verifying my email, and choosing my account subdomain in Workers & Pages. If I already have an account, reuse it. Let me handle sign-in in my browser without pasting a password, token or one-time code into chat. If using the CLI, use npx wrangler login as needed and npx wrangler whoami to confirm the intended account. Package only the public app assets in a clean folder with index.html at its root. Use a new, available Worker name and a Wrangler configuration with today's compatibility date, workers_dev set to true, and assets.directory pointing to that folder. Keep the master prompt, report, private records and credentials outside the assets directory. Use Workers Free for this static app. If setup requests payment or would replace an existing app, pause and explain. A custom domain is optional. After I approve, run npx wrangler deploy in the configured project. If this environment cannot run it, guide me through the Workers dashboard static file upload one step at a time. Copy the actual workers.dev URL from Cloudflare's deployment output. Open the link in a fresh browser session, reload it, and try the main acceptance case. Give me the verified link and tell me how to publish updates to the same Worker. Use the official guide if the dashboard has changed: https://developers.cloudflare.com/workers/static-assets/get-started/. If you cannot access the link, say what remains for me to check. Keep live integrations and paid services separately opt-in.