A skill for Claude · part of ados-addons
Idea to a live, indexed, tracked URL in one pass
Seven gates that each refuse to move on without evidence, and a variant engine that mathematically forbids a new site from resembling any site already shipped.
This page was built by the skill it describes · deploy in ~25s · zero dependencies
The fourth landing page this quarter
- The fourth landing this quarter, and the third one that looks like the last three.
- Two hours of the day 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
Seven gates that each halt on missing evidence, and a variant engine that mathematically forbids a new site from resembling any site already shipped. The generator cannot quietly produce a plausible-looking failure, because every gate is an executed command with an exit code.
Idea to live URL in one pass
Brief, variant, scaffold, deploy, custom domain, SEO, analytics and registry entry — one sequence, run end to end.
Two sites never look alike
Seven visual axes, 158,760 combinations, and a hard rule: a new site differs from every shipped site on at least four of them.
No silent success
Every gate is an executed command with an exit code. A plan is not evidence, and a green page is not a passing gate.
The seven gates
G0 · repo gate — halts before generating anything
G1 · uniqueness brief — approved by a human first
G2 · variant — deterministic, distance ≥ 4 enforced
G3 · content — ten sections, one CTA, no invented facts
G4 · local checks — exit 1 on any failure
G5–G7 · deploy, register, verify
Evidence, not adjectives
Break the page four ways and the checker catches all four: an inline <style>, a mismatched CTA, an
Negative controls, all four raised FAILunsafe-inlinesmuggled into the CSP, a missing social image.
Sixty sites placed in a row. Minimum pairwise distance across all 1,770 pairs: 4. The rule is not advisory.
Anti-sameness, stress-tested
This page was built by the skill it describes, and building it exposed five defects in that skill — including a CTA that pointed at a URL which did not exist yet.
Dogfooded
Get it
Free, private
Read this repository, fork it, run it.
What you supply
A repository named <slug>.alxevt.com and answers to nine questions.
Nothing is generated until the repository exists under the exact required name. A failed run leaves no half-built site behind.
Objections, answered
Do generated sites look the same?
No, and that is enforced rather than hoped for. Seven axes — layout, type, palette, shape, motion, texture and section rhythm — give 158,760 combinations, and a new site must differ from every shipped site on at least four of seven. Sixty consecutive placements held that minimum.
What happens if the repository is missing?
The run halts at G0 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. The local gate fails the build if unsafe-inline appears in the CSP at all.
How long does a deploy take?
The Cloudflare build for a one-page static site finishes in roughly twenty-five seconds. Every later push to main rebuilds automatically.
What is not automated?
Four things, and they are 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, 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