Build my first project: Shot Schedule Builder

What: I coordinate a two-camera wedding film crew at Afterglow Films. I build the shot schedule and both camera operators use it to see where they need to be next.

When: At our last wedding one shooter was listed for the couple's first look and a simultaneous family toast. Nobody saw the clash until they were in different rooms.

Where: It happens between our paper run sheet and each camera operator's phone. A location and a time can look perfectly fine until you check which shooter has that slot.

Why: A missed first look cannot be reshot. I need to spot double bookings while there is still time to hand a shot to the other operator and update the call sheet.

How: I'd like to see two time lanes and move a shot from one shooter to the other. I should see exactly which shots overlap, then see a clear schedule once the handoff is made.
The project I chose: Shot Schedule Builder
What I want to prove: On the shot schedule Mia has first look 14:00–14:20 and family toast 14:10–14:30. Show an overlap for Mia. Move the toast to Jules and clear the conflict. A new Mia shot starting exactly at 14:20 is back to back and must be allowed.

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 implement the Shot Schedule Builder, start by designing the first screen around the shot schedule object. The shot schedule object has fields for the camera operator, shot start time, and shot end time. The action that changes its state is assigning a shot to a camera operator. Use the approved brand colour #6F54A6 and typography that suits the trade. Include a second working view for handoff or saved record. The interface should have visual weight and use the owner's vocabulary. The first screen should display two time lanes for the two camera operators and allow the user to move a shot from one operator to the other. The system should alert the user to potential conflicts or gaps in coverage. For example, if Mia has a first look shot from 14:00-14:20 and a family toast shot from 14:10-14:30, the system should show an overlap for Mia. The user should be able to move the toast shot to Jules and clear the conflict. A new Mia shot starting exactly at 14:20 should be allowed as it is back to back. The system should be tested with a sample schedule and overlapping shots to verify that it alerts the user to potential conflicts or gaps in coverage. The user should be able to easily add, remove, and rearrange shots in the schedule.

Workflow examples that must pass
Mia has first look 14:00–14:20 and family toast 14:10–14:30 → Overlap detected (stage = Before scheduling, camera_operator = Mia, shot1_start = 14:00, shot1_end = 14:20, shot2_start = 14:10, shot2_end = 14:30)
Show an overlap for Mia → Overlap shown (stage = Before scheduling, camera_operator = Mia, shot1_start = 14:00, shot1_end = 14:20, shot2_start = 14:10, shot2_end = 14:30)
Move the toast to Jules and clear the conflict → Conflict cleared (stage = After scheduling, camera_operator = Jules, shot2_start = 14:10, shot2_end = 14:30)
A new Mia shot starting exactly at 14:20 is back to back and must be allowed → Shot allowed (stage = After scheduling, camera_operator = Mia, shot3_start = 14:20)

Design
My chosen brand colour is #6F54A6. 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 #6F54A6 and typography that suits the trade
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
- Front-end framework for building the user interface
- Back-end framework for storing and managing the shot schedule data

Acceptance checks
- Mia has first look 14:00–14:20 and family toast 14:10–14:30 → Overlap detected
- Show an overlap for Mia → Overlap shown
- Move the toast to Jules and clear the conflict → Conflict cleared
- A new Mia shot starting exactly at 14:20 is back to back and must be allowed → Shot allowed
- Test the shot schedule builder with a sample schedule and overlapping shots
- Verify that the tool alerts the user to potential conflicts or gaps in coverage
- Check that the user can easily add, remove, and rearrange shots in the schedule

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.