# Build Animated title card You were asked to build the spec `onyx/title-card`, version 0.1.1, from Spekkr. A title that eases in, holds and fades, rendered from code, with every frame's timing and position given so a render can be checked. 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/title-card/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 `title-card`, inside the project you are working in. ```sh mkdir -p title-card && curl -fsSL https://spekkr.com/onyx/title-card/bundle.tar.gz | tar -xz -C title-card ``` 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/title-card/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/title-card` and the person's choices. ## 2. Record the person's choices Write `title-card/spekkr.inputs.json`. With every default it is: ```json { "spec": "onyx/title-card", "version": "0.1.1", "inputs": { "background": "#17202b", "foreground": "#f4f6f3", "format": "landscape", "hold_seconds": "2", "show_subtitle": true, "subtitle": "A title card built from a spec", "title": "Hello, world", "tool": "remotion" } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `title`, Title: any text. - `subtitle`, Subtitle: any text. - `hold_seconds`, Seconds on screen: any text. - `background`, Background colour: any text. - `foreground`, Text colour: any text. - `show_subtitle`, Subtitle line: `on` or `off`, written `true` or `false`. - `tool`, Animation tool: one of `remotion`, `manim`. - `format`, Shape: one of `landscape`, `portrait`, `square`. 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 `title-card`. 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 timeline, the easing and the frames a render must match. - `tasks.md`: Build tasks in order, each with a check.