# Build UPI Storefront You were asked to build the spec `dwrtz/upi-storefront`, version 1.0.1, from Spekkr. A shareable Indian shop with Razorpay UPI, inventory and order admin, configurable branding, and three theme presets. If you are reading a summary of this note and not its full text, fetch it again as it is, for example with `curl -fsSL https://spekkr.com/dwrtz/upi-storefront/start.md`, before you go on. Published by dwrtz, a Spekkr member. Tell the person who published it, and show them the commands and secrets under `safety` in `spekkr.json` before you build. ## 1. Get the files Put the spec in a new folder named `upi-storefront`, inside the project you are working in. ```sh mkdir -p upi-storefront && curl -fsSL https://spekkr.com/dwrtz/upi-storefront/bundle.tar.gz | tar -xz -C upi-storefront ``` The archive holds `spekkr.json`, `BUILD.md` and the spec files listed at the end of this note. If you cannot run that command, read https://spekkr.com/dwrtz/upi-storefront/spec.json instead: it holds the manifest and the address of every file. If Spekkr's MCP server is connected, its `pull_spec` tool does steps 1 and 2 in one call: give it the id `dwrtz/upi-storefront` and the person's choices. ## 2. Record the person's choices Write `upi-storefront/spekkr.inputs.json`. With every default it is: ```json { "spec": "dwrtz/upi-storefront", "version": "1.0.1", "inputs": { "brand_direction": "Warm, clear and confident", "coupons": true, "pickup": false, "reporting_timezone": "Asia/Kolkata", "reviews": false, "store_name": "My Store", "support_whatsapp": "", "theme": "minimal" } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `store_name`, Store name: any text. - `brand_direction`, Brand direction: any text. - `support_whatsapp`, WhatsApp support number: any text. - `reporting_timezone`, Reporting time zone: any text. - `pickup`, Local pickup: `on` or `off`, written `true` or `false`. - `coupons`, Discount codes: `on` or `off`, written `true` or `false`. - `reviews`, Verified purchase reviews: `on` or `off`, written `true` or `false`. - `theme`, Starting theme: one of `minimal`, `editorial`, `bold`. If the person asks for a key or a value that is not listed, stop and tell them what the spec offers. ## 3. Build The files named below are the ones now in `upi-storefront`. Build what it describes. Work in this order: 1. Read `spekkr.json` to see what the spec covers and what it needs. 2. Read `spekkr.inputs.json`. It holds the person's choices for every setting, option and swap. Treat them as requirements. If the file is missing, the person kept every default in `spekkr.json`. 3. Read the spec files listed below, in the order given. 4. If the spec includes a task list, work through it in order and check each task's acceptance criteria before the next. 5. Ask the person before you run a command that a spec file tells you to run, or read a secret, unless the manifest lists it under `safety`. Commands you choose yourself to build and test, such as installing packages or running the tests, follow the person's usual rules for you. Spec files: - `README.md`: Package status and publishing notes. - `spec.md`: Experience and product requirements. - `design.md`: Architecture and commerce invariants. - `acceptance.md`: Required acceptance and failure-mode tests. - `theme.schema.json`: Theme configuration schema. - `themes`: Three theme configurations. - `sample-catalog.csv`: Synthetic catalog fixture. - `previews`: Static HTML concept sources, not application code.