Build my first project: Remnant Inventory Manager What: I run Offcut Works, a little bag studio. We make zip pouches out of rectangular canvas remnants. I decide which remnant can yield enough matching panels for each batch. When: A usable piece of fabric got passed over because we laid the pattern in one direction. Later we discovered that turning every panel would have fitted the whole order. Where: The choice happens at the cutting table. The maker sees the pattern, the direction of a woven stripe and our chalk measurements, but our notebook only records the area. Why: I want to cut a matching batch from a single offcut. If the print is directional we must respect its grain; on plain canvas we can turn the whole pattern layout. How: The maker should see the actual pattern pieces fitted to the remnant. Switching between directional and plain fabric should show the orientation, the quantity and whether the batch fits. The project I chose: Remnant Inventory Manager What I want to prove: Use a 40 × 24 cm offcut and 12 × 20 cm panels, with four panels requested and no cut allowance. A directional fabric fits three upright panels. Plain canvas may turn the uniform grid 90 degrees, so four fit. Draw the actual grid, and update it when dimensions change. 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 Remnant Inventory Manager project, start by designing the first screen around the object that Offcut Works already works with, which is the remnant. The user of this object is the maker, and the fields include the remnant dimensions, pouch dimensions, and fabric directionality. The action that changes the state of this object is the calculation of the number of pouches that can be made from the remnant. Give this object visual weight and use the owner's vocabulary. Use the approved brand colour #C45B31 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 remnant dimensions, pouch dimensions, and fabric directionality, and allow the user to enter these values. The system should then calculate the number of pouches that can be made from the remnant based on these inputs. For example, if the user enters a remnant dimension of 40cm x 24cm, a pouch dimension of 12cm x 20cm, and selects directional fabric, the system should display that three pouches can be made from the remnant. If the user selects plain fabric, the system should display that four pouches can be made from the remnant. The system should also update the calculated number of pouches when the user changes the remnant dimensions. The technology used for this project will be JavaScript, HTML, and CSS. The checks for this project include user enters remnant dimensions and pouch dimensions, user selects directional fabric, user selects plain fabric, user changes remnant dimensions, check if the remnant is large enough to make the requested number of pouches, and check if the fabric's directionality affects the number of pouches that can be made. The limits for this project include remnant dimensions, pouch dimensions, and fabric directionality. The design for this project should create a simple and intuitive interface that allows the user to enter the remnant and pouch dimensions, and select the fabric's directionality. Display the calculated number of pouches that can be made from the remnant. The cases for this project include user enters remnant dimensions and pouch dimensions, user selects directional fabric, user selects plain fabric, and user changes remnant dimensions. The task outcome for this project is to calculate the number of pouches that can be made from the remnant based on the user's inputs. The missing information for this project is the remnant dimensions, pouch dimensions, and fabric directionality. The boundary condition for this project is the minimum and maximum remnant dimensions and pouch dimensions. The conflicting conditions for this project are the fabric directionality and the remnant dimensions. The repeatability for this project is to repeat the calculation with the same inputs and verify that the result is the same. Workflow examples that must pass User enters remnant dimensions (40cm x 24cm) and pouch dimensions (12cm x 20cm) → Calculate the number of pouches that can be made from the remnant (stage = Before calculation, remnant_length = 40, remnant_width = 24, pouch_length = 12, pouch_width = 20) User selects directional fabric → Display the calculated number of pouches that can be made from the remnant (3) (stage = After calculation, fabric_directionality = directional) User selects plain fabric → Display the calculated number of pouches that can be made from the remnant (4) (stage = After calculation, fabric_directionality = plain) User changes remnant dimensions → Update the calculated number of pouches that can be made from the remnant (stage = After calculation, remnant_length = 50, remnant_width = 30) Design My chosen brand colour is #C45B31. Use it consistently as an accent, provide a readable foreground on every surface, and keep important status differences understandable without colour alone. Create a simple and intuitive interface that allows the user to enter the remnant and pouch dimensions, and select the fabric's directionality. Display the calculated number of pouches that can be made from the remnant. 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 - JavaScript - HTML - CSS Acceptance checks - User enters remnant dimensions (40cm x 24cm) and pouch dimensions (12cm x 20cm) → Calculate the number of pouches that can be made from the remnant - User selects directional fabric → Display the calculated number of pouches that can be made from the remnant (3) - User selects plain fabric → Display the calculated number of pouches that can be made from the remnant (4) - User changes remnant dimensions → Update the calculated number of pouches that can be made from the remnant - Check if the remnant is large enough to make the requested number of pouches - Check if the fabric's directionality affects the number of pouches that can be made 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.