Drop the folder into Claude and it walks you through all seven moves, from your brand files to a live URL on your own domain. Day one, design and audit. Day two, ship and hand over. No developer. No drift.
There are a thousand videos of AI design output. Almost none of it ever reaches a real domain, and almost none of what does survives a year of price changes and menu updates. This is the part nobody shows you: the export, the launch, and the Tuesday afternoon a year from now when you need to change one line.
Voice note on Monday. Live URL by Wednesday.
Six files plus the Kit, and a Start Here that lets Claude drive. Prefer to drive yourself? The Run Sheet on page one is the same journey in seven moves.
One page you paste into Claude Design along with your design system. Back comes a full homepage built on your own components, not a template.
The four files to upload, in order, and the exact opening prompt that built The Iru, word for word. This is what stops the model from inventing its own colors and spacing.
Every fix I made on The Iru, all twenty, in order. Half were taste, half became permanent rules. Plus the habits that save passes: describe the target, not the direction. Reference images beat adjectives.
Two paste blocks. The first makes Claude confess every decision nobody asked for. The second checks every claim, color and price against its source. This is how I caught "award-winning" on a restaurant that doesn't exist.
One prompt to freeze and export, then four for Claude Code: repo, Vercel, domain with SSL, verification. About fifteen minutes of real work, including the launch pass and the registrar snags nobody warns you about.
How every future edit works. Text changes go live in minutes with zero design risk. Visual changes get a private preview link first. Any change, one email.
The AI Brand Kit, all eight files. The pipeline builds on the design system the Kit produces, so it comes in the box.
Drop the folder into a Claude chat. It asks one question first, do you have a design system yet, routes you into the Kit if not, and if yes, runs the build one move at a time: which tool to open, what to upload, the exact text to paste, what you should see. You report back, it moves on.
Day one is moves one through four. Day two is five through seven.
Open Claude Design. Upload four things in order: design system, brand guidelines, brand brief, photos. The model builds from what's attached because it has nowhere else to look.
Paste the opening prompt, word for word. A full homepage comes back, built from your own components. Correct and a little generic, which is exactly the starting point you want.
Shape it with plain-English corrections from the Correction Sequence. If Claude is driving, it serves the proven correction language at the right moments.
Two paste blocks make Claude Design confess every decision nobody asked for, then trace every claim, color and price to its source. You rule keep, fix or decide. Nothing ships before this.
Declare the design frozen. One prompt restructures it into a deployable site with every editable word, menu, prices, hours, meta, moved into one content file.
Open Claude Code in the exported folder. Four prompts in order: repo, Vercel, domain with SSL, verification. Then a launch pass: WebP, favicon, social cards, 404, sitemap.
Every future edit takes one of two lanes. Content goes straight to live in minutes. Visual changes get a private preview link you approve first. A price change on The Iru took eleven seconds.
You'll need an account with each. The Launch Pack walks you through setup in the order you'll hit it.
The Iru's website is live right now on its own domain. Built from the Kit's design system, corrected with the sequence above, launched with the four prompts. Changing Friday hours took forty-two seconds. A new 404 page took fifty-one.
Homepage, story, menu, gallery and footer, exactly as they ship. Every color, type size and spacing rule traces back to a file in the Kit.
No. Claude Code does the work between the design export and the live site. You answer a few questions and paste four prompts. If you can copy and paste, you can launch.
No. Drop the whole folder into Claude and it guides you move by move: which tool to open, what to upload, what to paste, what you should see. Prefer to drive? The Run Sheet on page one is the same journey in seven steps.
Claude asks that first. If the answer is no, it routes you into the included AI Brand Kit and brings you back when your design system is ready. Nothing to figure out.
Two days end to end. Day one is design, direction and the audit, moves one through four. Day two is freeze, ship and hand over. The launch itself is about fifteen minutes of real work.
It's included, and Claude checks for it on the first question. If you already own the Kit, the pipeline picks up exactly where your Design System Setup left off.
The brand and design phases work for anything. The Launch Pack is built for a one-page site with no CMS. Multi-page and headless CMS is a separate series.
No. The concept is fictional. The brand, the guidelines, the site and the process are all real and all shown on camera.
Claude, GitHub and Vercel. All three are free at this scale. Claude Code runs locally on your machine.
Yes. If it isn't useful, email me within 14 days and I'll refund it. No questions asked.