Real session, real command. I typed /design a few options for my SEO agency homepage — and Claude opened a design wizard.
What you're watching: the real /design wizard inside Claude Code — it asks which brand to match, offers my live goldie.agency colours and fonts as the base, asks static mockups or clickable prototype, then reads my actual site files and generates three artboards — you'll see the published link land at the end.
And here is what it made.
Three homepage directions for my real agency, on my real brand — inside the actual Claude Design canvas.
What you're watching: the real canvas /design published — Option A "Editorial Split", Option B "Dashboard Proof", Option C "Founder-Led Narrative". Same coral brand system, same real copy, three different structures. I just point at one.
First run: type /design consent once. That connects Claude Design and the command lights up.
What you're watching: the activation flow, live — /design revoke turns it off, /design consent turns it back on ("Design agent access granted for your Claude Design projects"). If /design only prints a usage line for you, run the consent step and update Claude Code — it's a research preview rolling out account by account.
And it answers inside my Agent OS too.
Same command, typed into the Claude chat on my dashboard.
What you're watching: the Agent OS Claude tab. I type /design consent into the chat, Claude thinks, and the real answer streams back — "Design agent access granted for your Claude Design projects."
One command. Five completely different things. Watch.
§0 · build 1 a booking page for a consulting business
"/design a few options for a booking page…"
The canvas /design published for "a booking page for a consulting business". Four directions — a gentle tonal one, a dark high-end one, a warm approachable one, and a data-driven authority one — each annotated with sticky-note reasoning.
The full run, time-lapsed — the command typed, the wizard answered, the artboards generated. Real session.
"/design a few options for a simple task tracker…"
The canvas /design published for "a simple task tracker for a team". The wizard even asked which shape the tracker should be — kanban, list or grid — before drawing.
The full run, time-lapsed — the command typed, the wizard answered, the artboards generated. Real session.
You do not install anything new. You update Claude Code, type /design, and it is there.
What you're watching: a real terminal on my Mac. Claude Code 2.1.229, the /design command answering, the three artboard files sitting in the folder, and the feature's own description read straight out of the installed program.
§2 the whole workflow
Describe it. See options. Pick one. Then it builds.
Four steps, and the code only shows up at the end.
§3 who has it today
It is on your plan already.
Two places to use it, four plans that have it. Update Claude Code and it appears.
Stick with me — the part that fixes everything is level two.
§4 the problem
The One Guess Problem.
Up until now you described a page in words, and Claude went away and wrote all the code.
One version. One guess. And if you did not like how it looked, you described the changes in words and it rebuilt the whole thing again.
Every lap of that circle costs you real time and a real rebuild. This is the part /design deletes.
§5 what every lap costs
Every "make it more modern" is a full rebuild.
The words are cheap. What follows them is not — a whole page of working code gets written again.
§6 the fix
The design now happens before the build.
That is the whole change. Same tool, different order.
§7 three levels
There are three parts to this.
Once you see all three, you will understand why this is bigger than it looks.
§8 level one · the artboards
You type it. You get artboards.
An artboard is just a picture of what the thing could look like — like a designer showing you three sketches before building anything.
What you're watching: three real artboards for the same booking page, on one canvas. Clean, busy, corporate. Click one and it gets picked, the others fade. No code has been written yet.
Each artboard is one file. Claude lays them out side by side so you can compare them like sketches on a table.
§10 where it came from
The design brain moved in with the building brain.
Anthropic took the artboard workflow from Claude Design and pulled it straight into Claude Code.
§11 the magic word
Ask for "a few options".
That one word turns a single guess into several visual directions at once.
§12 like clothes on a bed
Three outfits, laid out. You just point.
Same booking page, three directions. You do not need design words — you need a finger.
This next part is the one that fixes everything.
§13 level two · the editing
It is 80% right? Tweak it. Don't start over.
The artboards are editable. You change the picture directly instead of writing a paragraph asking for changes.
What you're watching: the picked artboard being edited live — headline size dragged up, accent colour swapped, button text rewritten. Still zero code. Nothing has been built yet.
Same page. Same person. The only change is when you decide how it looks.
OLD WAY
~ days
Describe the page in a paragraph
Wait while all the code gets written
Get one version you didn't choose
Write another paragraph: "more modern"
Watch it rewrite working code
Repeat five or six times
Or hire a designer and wait days for mockups
NEW WAY
~ minutes
Type /design a few options
Look at several finished-looking layouts
Point at the one you like
Drag the headline, swap the colour
Say "implement this"
Get the working page, built once
Total: one build instead of six
§15 why that matters
Changing a picture is cheap. Changing finished code is expensive.
Same fix, two very different prices.
THINKING IT?"This sounds like a tool for designers."
It is the opposite. Designers already have their tools.
This is for people who were never going to open a design app. If you can describe what you want and point at a picture you like, that is the whole skill.
The picture you approved becomes the working thing — buttons that click, a form that checks itself, a real confirmation.
What you're watching: the finished booking page from the artboard we just tweaked — same big headline, same gold accent, same button words. A slot gets picked, the form gets filled, and the booking confirms.
The design and the code live in the same tool, so Claude builds from the exact artboard you approved.
§18 my own setup
My whole dashboard was built with Claude Code.
Mission Control, every agent panel, every page my sites publish — and the design step was always the slow part.
What you're watching: my live Agent OS on this Mac — Mission Control, the agent kanban, the Claude panel, goal mode. Every screen you see here was built by describing it to Claude Code.
And here are the /design artboards INSIDE the Agent OS — the Claude Workspace lists the design-artboards project, and the preview pane renders the REAL generated canvas (the three goldie.agency options), the artboards and the finished booking page without leaving the dashboard.
§19 what it used to cost me
Six builds for one layout. Now: one.
"Make the cards tighter." "Different colour scheme." Every round meant Claude rewriting real code.
§20 and the same for pages
Every new page needs a layout. Now that is a two-minute decision.
Before: accept whatever came back, or go rounds. Now: look, point, build.
§21 you have this problem too
It is whatever you keep putting off.
Same bottleneck, different name, in every business.
most people
Your website
You know it looks dated. You have not touched it because the redesign feels like a project.
service businesses
A booking page
You want people to book calls, so it has to look worth booking.
teams
A simple internal tool
A tracker your team actually uses, instead of another spreadsheet nobody opens.
§22 who this is really for
Describe. Point. That is the whole skill.
Not designers — they already have their tools. This is for people who were never going to open a design app in their life.
THINKING IT?"I'm not technical. Claude Code sounds like a developer tool."
The name does not help, but Claude Code is a chat box in a window. You type what you want in plain English.
This command makes it less technical, because the hardest part — the visual part — is now point and click. Some of the people getting the most out of it are agency owners and ecommerce sellers who had never written a line of code before this year.
§23 the honest picture
Two real limits. No hype.
This is a research preview, which means early. Anthropic is asking for feedback on it, so expect some rough edges.
i.
It uses more of your plan
Generating several visual artboards costs more of your capacity than plain text. Do not design ten things for fun — design the thing you actually need.
ii.
Matching an existing brand isn't perfect yet
If your site already has a very specific look, the artboards will not always nail it on the first pass. It is better at fresh designs than at copying your existing ones.
§24 what is actually new
The workaround became a feature.
People have been asking Claude to mock things up in HTML before building for a while. That was a workaround. This is built in.
THE MANUAL VERSION
a hack
Ask for a mockup in words
Get one page at a time
Compare them by opening files yourself
No way to edit — describe changes again
Then explain it all again to build it
THE BUILT-IN WORKFLOW
a feature
One command: /design
Several artboards at once
Laid out side by side on one canvas
Editable — tweak the picture directly
Connected straight to the build step
§25 the bigger pattern
Everything keeps moving into Claude Code.
It started as a coding tool. Watch what has been added since.
§26 learn the harness
The harness is the thing to learn — not the model.
A harness is the tool that wraps around the AI and lets it actually do work. Claude Code is mine. The skills carry over to any of them.
§27 three beliefs to drop
The tools change. The workflow does not.
These are the three things I hear that keep people standing still.
Wrong: "I'll wait until these tools settle down, then learn the winner."
Right: The people who waited last year are still waiting, and they're a full year behind the ones who started. Everything you learn now transfers.
Wrong: "Designing things is a talent. I don't have it."
Right: You don't need to make the design. You need to recognise the one you like. Everyone can do that.
Wrong: "AI can build things, but it can't make them look good without a fight."
Right: That was true until today. Now you see the options first and the fight never starts.
Don't take my word for it
Members post their wins every day — agency owners, ecom founders, course creators, solo operators across 38 countries. Real businesses, real numbers, in their own words.
You made decisions. Claude did work. Pointing at pictures is far faster than writing paragraphs about them.
§30 one more layer
The approved design goes into the shared memory.
Inside my Agent OS every agent reads the same vault, so the design decision happens once and everything downstream builds from it.
THINKING IT?"Doesn't running an Agent OS burn a fortune in tokens?"
No — that is the biggest myth about it. It runs the everyday work on a free local model on your own machine, free APIs slot in for more, and for the heavy work it drives the tools you already pay for — your Claude subscription already includes the Claude Code CLI, and the Agent OS plugs straight into it.
It is a layer on top of what you already own, not a new meter. Inside the Boardroom there are full token-efficiency tutorials so you learn to cut usage to the bone.
§31 the real lesson
Features come and go. Systems compound.
A single new command is nice. A system where every new command makes everything else stronger is where the advantage lives.
§32 where things stand
Live today. Rough in places. Worth it the first time you use it.
status
Live
Research preview, in Claude Code right now.
plans
4
Pro, Max, Team and Enterprise.
to start
1
Update Claude Code, then type /design and what you want.
/design a few options for a booking page for my consulting business
The AI Profit Boardroom is where the actual Agent OS lives — the templates, the prompts, the daily rooms, the weekly walkthroughs. Same skills you read about here, taught hands-on inside.
