A skill for Claude · part of ados-addons
Your fourth landing page should not look like your first three
alxw takes a brief to a live, indexed, tracked URL in one pass — and enforces, rather than hopes, that no two sites it builds resemble each other.
This page was built by the skill it describes · deploy in ~25s · zero dependencies
The fourth landing page this quarter
- The third one that looks like the last three, because the same defaults win every time.
- Two hours go to deploy plumbing: a Worker, a build trigger, a DNS record, a sitemap.
- Something ships broken and nobody notices, because a broken page still returns 200.
Gates instead of good intentions
The protocol lives in the skill and decides when to stop. The scaffold and the artifact gates live in one repository and decide what the produced files must be true of. Neither can pass on a plan: a gate is passed by output.
Four anatomies, not four skins
A sales landing removes doubt. An explainer displays it, because the doubt is the subject. A tool has neither. A data page has one reading and an obligation attached to it.
Divergence is enforced
Seven axes, 204,120 combinations, and a floor: a new site differs from every deployed one on at least four. Below four, two pages share skeleton, type and colour — and no amount of different copy hides that.
No silent success
A build reporting success is not a deployed page, and a page returning 200 is not a working one. Both have their own gate.
The gates
G0 · repo gate
Halts before generating anything if the repository is missing, misnamed or unwritable.
G1 · brief
Archetype first, then a human approval.
G2 · variant
Recorded in variant.json, divergence ≥ 4 axes.
G3 · content
Routed by archetype. No invented facts, prices or sources.
G4 · artifact gates
A0–A17, every result shown.
G5–G7 · ship
Deploy, register, accept.
Built with it
Three sites, one scaffold. Every pair is at least six axes apart. Open them side by side — that comparison is the whole argument, and it is cheaper to look than to be told. The specimen sheet shows every axis value rendered live.
swim-window.alxevt.com — slack-water windows for cold-water swimmers. Indigo and amber, a condensed lead, an editorial rail, a tide curve carrying the argument.
Sales · public repository
kiln-slot.alxevt.com — booking for a shared studio kiln. Near-white with glaze pastels, hard offset shadows, a firing curve whose slot bar runs twelve hours past the firing bar.
Sales · private repository
This page — paper ground, slate-blue accent, a numbered section index. It was near-black with an acid accent until the variant was re-chosen, for the reason in the answers below.
Sales · the scaffold itself
Get it
Not a product with tiers — an exchange. Here is each side of it.
You get
Ten files of protocol, one scaffold, eighteen artifact gates, and a deploy path verified end to end on three live sites.
You supply
A repository named <slug>.alxevt.com, answers to nine questions, and one approval of the brief.
Nothing is generated until the repository exists under the exact required name. A failed run leaves no half-built site behind.
Straight answers
Do generated sites look the same?
No, and it is enforced rather than hoped for. Seven axes give 204,120 combinations, and a new site must differ from every deployed site on at least four of them. Three sites are live and every pair is at least six axes apart — see the specimen sheet for every value rendered live.
Can I change the design later?
Yes. The design is recorded in variant.json and changed like any other file, on request. Three rules keep it safe: variant.json and the page attributes change in the same commit, the divergence rule is re-checked afterwards, and the social image is regenerated — its colours come from the same file, so it goes stale the moment the palette moves.
What kinds of page can it build?
Four. A sales landing, an explainer document in a science or popular register, a single-purpose tool, and a data reading. They are different anatomies, not skins — the sales page removes doubt, the explainer displays it because the doubt is the subject, the tool has neither, and the data page has one reading with an obligation attached to it.
Does it matter whether the repository is public or private?
No. One demonstration site is public and the other private; both deployed through the same seven steps with no difference in the API contract. The one thing worth knowing is that a public repository makes brief.json world-readable — including the audience profile and the pricing.
What happens if the repository is missing?
The run halts before a single file is generated, and the skill will not create the repository for you. Naming is the one thing a generator should never guess.
Does adding analytics weaken the security headers?
No. The GA4 bootstrap is an external file, so script-src 'self' survives and no unsafe-inline is ever needed. A gate fails the run if an inline script appears at all.
Why is this page not dark?
It used to be. Near-black with one bright acid accent is one of the three looks AI-generated design keeps landing on, and hairline rules at zero radius is another — this page held both at once. A page arguing that the fourth landing should not look like the first three cannot itself be the default look, so the variant was re-chosen.
What is not automated?
Four things, listed rather than hidden: that the tag actually fired, that the console shows zero CSP violations, the Lighthouse numbers, and whether the copy is any good. Those need a browser and a human.
See how it was built
The brief, the chosen variant, the artifact gates, and every generated file — the complete input and output of one run, in one repository.
MCP-first · no tokens required · reproducible from the repository alone