thoba.it

The making of thoba.it

How this page was built.

Designed, written, reviewed and shipped by AI agents I direct, from a brand contract to a pull request. I set the bar and I merge. This is the record, since the repository is private.

In numbers

  • 1HTML file per page, zero build
  • 3Languages, one source of truth
  • 14Independent reviews
  • 0Lines of page code typed by hand

The loop

  1. Brief

    A few lines from me: fresh look, same CV purpose, the AI angle front and centre, references to space, technology and networks. The agent captured the live site, read the previous version's repository and studied design references before drawing anything.

  2. Brand as code

    DESIGN.md is the contract every agent reads before touching the page: a palette with roles, a type scale, motion rules, and the list of what never ships — glass, gradients, count-ups, cards. It is published with the site.

  3. Build

    One HTML file, no build step, real fonts, real copy. The night network is a real adjacency graph of my stack, drawn by the page itself. English is the document; French and Italian are dictionaries. The résumé PDFs are generated from those same dictionaries, so a sentence is edited once.

  4. Critique

    Render, look, fix: headless Chromium at three screen widths after every change. Then independent reviewers with no context critique the page against the contract — five design dimensions, accessibility and performance, and personas standing in for the people this page is for. Each answers one question: would I take the next step? Their notes become the next commit. That loop replaced an early green palette with this one (round five), set the page in motion as one continuous scroll film with a single morphing network and a hidden break-and-heal interaction (round six, V5), and tightened the mobile hero, the sweep timing, the label layout and the French typography against three fresh reviews (V5.1).

  5. Ship

    Pushed to my self-hosted Forgejo. The pull request is opened by a scoped job that can create, update and comment, never merge; its credential is injected at run time and never shown to the agent. I review and merge. A script syncs the files to S3 and invalidates CloudFront.

Read the design contract (DESIGN.md)

What stayed human

Direction and taste. Every fact, every number and both contacts. The six answers that shaped the last round: team scope, advisory, where I live. Every merge and every deploy. The agents do the work; I set the bar — which is exactly how I run teams.

The stack behind it

Kiro CLI on Anthropic's Claude, orchestrated by Kiro Crew — persistent memory, sub-agents for the independent reviews, scheduled jobs, vault-held credentials granted job by job. Playwright for the renders and the PDFs. Forgejo on a Proxmox container in my lab — the same lab the night network draws.