# Build Enclosure for a circuit board You were asked to build the spec `onyx/project-enclosure`, version 0.1.1, from Spekkr. A two-part printable enclosure sized to your board, modelled as code, with dimensions and volumes a build must reproduce. 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/onyx/project-enclosure/start.md`, before you go on. Published by onyx, 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 `project-enclosure`, inside the project you are working in. ```sh mkdir -p project-enclosure && curl -fsSL https://spekkr.com/onyx/project-enclosure/bundle.tar.gz | tar -xz -C project-enclosure ``` 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/onyx/project-enclosure/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 `onyx/project-enclosure` and the person's choices. ## 2. Record the person's choices Write `project-enclosure/spekkr.inputs.json`. With every default it is: ```json { "spec": "onyx/project-enclosure", "version": "0.1.1", "inputs": { "cable_slot": true, "corner_radius": "4", "inner_height": "30", "inner_length": "100", "inner_width": "60", "standoffs": true, "tool": "cadquery", "wall": "2.4" } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `inner_length`, Inside length, mm: any text. - `inner_width`, Inside width, mm: any text. - `inner_height`, Inside height, mm: any text. - `wall`, Wall thickness, mm: any text. - `corner_radius`, Outside corner radius, mm: any text. - `standoffs`, Standoffs for the board: `on` or `off`, written `true` or `false`. - `cable_slot`, Cable slot: `on` or `off`, written `true` or `false`. - `tool`, Modelling tool: one of `cadquery`, `openscad`. 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 `project-enclosure`. 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`: Geometry, formulas and the numbers a build must match. - `tasks.md`: Build tasks in order, each with a check.