# Build Spot Santa You were asked to build the spec `dwrtz/spot-santa`, version 0.1.0, from Spekkr. A 3D find-the-person game in the browser: a seaside festival town of 10,000+ animated people, all made from code. Spot Santa fast. 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/spot-santa/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 `spot-santa`, inside the project you are working in. ```sh mkdir -p spot-santa && curl -fsSL https://spekkr.com/dwrtz/spot-santa/bundle.tar.gz | tar -xz -C spot-santa ``` 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/spot-santa/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/spot-santa` and the person's choices. ## 2. Record the person's choices Write `spot-santa/spekkr.inputs.json`. With every default it is: ```json { "spec": "dwrtz/spot-santa", "version": "0.1.0", "inputs": { "crowd_size": "10000", "miss_penalty": "3", "shadows": true, "target_coat": "#c62828", "target_name": "Santa", "target_trim": "#ffffff" } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `target_name`, Name of the person to find: any text. - `target_coat`, Santa's coat and hat colour: any text. - `target_trim`, Santa's beard and trim colour: any text. - `crowd_size`, People in the town: any text. - `miss_penalty`, Seconds added for a wrong pick: any text. - `shadows`, Sun shadows: `on` or `off`, written `true` or `false`. 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 `spot-santa`. 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: - `spec.md`: Requirements and acceptance checks. - `design.md`: The town, the people, the motion, the camera and the picking maths. - `tasks.md`: Build tasks in order, each with a check.