For sites you build with an AI agent
Where the words live decides what a change costs.
The free setup audit checks where yours live, with a read-only script you run on your repository.
That did not send. Check the address and try again.
Built twice. Measured both times.
A worked example / 001
Ask for a change. See which files it touches.
Choose a lit file to read why.
A fictional pottery studio
Ask for a change
No change yet5 files touched3 files touched
No change yet1 file touched
You ask Pick a change above.“Put the prices above the classes.”“Make the prices section dark.”“Change the headline to ‘Clay, fired on Thursdays’.”
The reason for each lit file shows here.
2. Classes3. Prices2. Prices3. ClassesThe copy doc lists the sections by number, kept by hand, because the headlines are typed into the components.
Field mark Where the headlines are typed. Audit check 1 of 8.
<Classes /><Prices /><Prices /><Classes />The page runs in the order of these tags.
Field mark None. This is the edit you asked for.
padding-top: 96px;padding-top: 32px;This padding caught the Classes cards, which hang 64px into the band below them. Under the hero it would leave a gap.
Field mark Negative margins holding neighbours. Audit check 5 of 8.
padding-top: 32px;padding-top: 96px;Reviews now sits under Classes, so it has to catch the hanging cards instead.
Field mark Negative margins holding neighbours. Audit check 5 of 8.
const stages = ["Hero", "Classes", "Prices", "Reviews", "Visit"];const stages = ["Hero", "Prices", "Classes", "Reviews", "Visit"];The progress rail names the sections by position, so it shows the old order until someone edits it.
Field mark Scripts that count sections. Audit check 6 of 8.
{ "id": "classes" },{ "id": "prices" },{ "id": "prices" },{ "id": "classes" },The page runs in this record’s order, and every band has the same spacing, so nothing hangs between them.
Limit Docs that restate the order go stale. After this site’s rebuild three still did, and no check noticed.
background: #e2e8f1;color: #0e1726;background: #0a1730;color: #eaf4ff;Its colours are typed into its own style, each one chosen for a light ground.
Field mark Raw colours in component styles. Audit check 4 of 8.
.card { background: #ffffff; }.card { background: #ffffff; }.card--dark { background: #05070d; }Classes uses the same card and stays light, so the card needs a second version and a prop to choose it.
Field mark Components with their own styles. Audit check 2 of 8.
const lightBands = [1, 2, 4];const lightBands = [1, 4];The rail changes colour over the bands it knows are light, and it knows them by number.
Field mark Scripts that count sections. Audit check 6 of 8.
"tone": "surface""tone": "dark"One word. The tone re-points every colour inside the band, the cards included.
Limit No check compares neighbours. Prices and Reviews are now both dark, and only a screenshot shows the join.
Hero: Make something you’ll use.Hero: Clay, fired on Thursdays.The copy doc repeats the headline by hand, so it can drift from the page.
Field mark Where the headlines are typed. Audit check 1 of 8.
<Base title="Make something you’ll use"><Base title="Clay, fired on Thursdays">The page title repeats the headline in a second file.
Field mark Where the headlines are typed. Audit check 1 of 8.
<h1>Make something you’ll use.</h1><h1>Clay, fired on Thursdays.</h1>The headline is typed into the component, inside markup that also holds its layout and styles.
Field mark Where the headlines are typed. Audit check 1 of 8.
"title": "Make something you’ll use.""title": "Clay, fired on Thursdays."The headline and the page title sit in the same record, a line apart.
Limit A share image with the old headline drawn into it still has to be made again. This site’s has the same limit.
This is an interactive illustration using a fictional website. Counts describe this example. This site’s own figures come next.
This site’s own receipt
The copy sat inside the components, so a new layout meant a rebuild.
407agent-minutes
The first build: live the day it started, with its gate passing.
1,412agent-minutes
The rebuild. It also added a schema and QA tools, so it overstates the layout alone.
2.1agent-minutes at most
Each of three layout changes after the rebuild: one content file, plus the docs by hand. Nobody timed one on the first build.
The setup audit, free for an email
Every field mark in the example above is one of the audit’s eight checks.
Each says how to run it, and what failing it cost this site.
It counts six of the checks in your repository, beside this site’s before and after. It reads Astro projects.
AGENTS.md, with a CLAUDE.md copy, so every change starts from the same rules.
The kit, not on sale yet
The kit is that structure, with this site’s gate, form endpoint, deploy and live check, and a build guide from clone to live. Pre-orders open to the list first, refunded if the ship date slips.
$199 once
One person, any number of sites, client work included.
$599 once
A studio of up to five, with a client handover pack.
Fair warning
If your agent makes it well for free, keep your money. The setup audit tells you whether it did.
For you if
Not for you if
The setup audit
The eight checks, the script and the rules file, in one email. After that, one more when pre-orders open.
That did not send. Check the address and try again.