§0pipeline

How this site was built

I built this site with an agentAn AI program that writes and changes code, for example Claude Code or Cursor. On this site, "agent" means a coding agent., under its own rules. This is the record. One prompt file, eleven steps (0 to 10, plus 7b for the slides), run with Claude. Every number on this page was recorded during the build. None is estimated. The full record is filled in after step 10; this is the short form for the talk.

Step What it produced
0 Start Settings, the claims registryA number on this site, kept with its base, its source and its date in one registry., a private naming blocklist
1 Analysis 13 comparable sites reviewed; every industry figure opened again; 2 figures dropped, 3 corrected
2 Visual direction Two brands from Open Color, six open-licence fonts with Czech coverage, the contrast proof
3 Design system The design system in Claude Design, two home directions, the choice, four permutationsOne combination of the modifier options. This site has four.
4 Voice and tone The voice rules, built with the voice-and-tone plugin
5 Content Every page, the register, the ladder questions, the slide texts in two languages
6 Page designs Every page type on desktop and phone
7 Code DTCGThe Design Tokens Community Group and its file format for design tokens, version 2025.10. A Final Community Group Report, not a W3C standard. tokensA named design value, for example a color or a spacing step, kept as data. DTCG 2025.10 gives the file format., Terrazzo, shadcn/uiA set of open-source components that you copy into your code. Agents know it well., the checks in CIContinuous integration: the checks that run on each change of the code.
7b Slides One HTML and CSS file, two brands, two modes, two languages
8 Launch Rock8Cloud, the EmDash CMS
9 Quality control An independent pass over the live site
10 Handover The editor guide and the talk kit
§1numbers

Recorded numbers

StepRecordedValue
Step 1Comparable sites reviewed13
Step 1Industry figures dropped / corrected after opening the source again2 / 3
Step 2Text contrast pairs checked across 4 permutations, minimum ratio48, 4.75:1
Step 3Tokens written by the design tool76 (20 colours × 4 themes, 18 type styles, 18 sizes, 9 spacing, 5 radius, 1 shadow, 3 borders, 2 measures)
Step 3Components written20, then 22 after the direction choice
Step 3Time13 minutes
Step 4Voice rules: confirmed / derived / assumed / disputed51 / 2 / 6 / 0
Step 5Pages written; decisionsA written choice of the team, with an id, a reason and the check that enforces it. On this site, a row of the register.; claims36; 16; 39
Step 6Artboards designed51
Step 7DTCG token definitions after conversion; tokens built by Terrazzosee the footer line and the CI log
§2gaps

What could not be built honestly

  • No logo exists. The wordmark is set in type.
  • The design tool stores tokens as a list, not DTCG. They were converted once to DTCG 2025.10; the repository leads from there.
  • The design tool's type families are global, not per theme; the brand switch of fonts, sizes and radius runs through role tokens.
  • Feature 12 (installable parts as a shadcn registryA list of the components of a system that a tool or an agent can read.) is built last and may be dropped for the talk.
  • Feature 9 (the checklist result) follows after the talk.
§3prompt

The prompt file

The prompt file, as run