Artifacts, /design, and the pages people ship
Last week Claude Code learned to design. This week the timeline is full of people testing what that actually means. Here is what they found, pulled straight from X, with the useful part of each post kept and the rest thrown away.
A research preview of the /design command landed on August 17. It puts Claude Design's artboard workflow inside the CLI and Desktop, and the whole thing runs on artifacts.
"Claude Code can design now. The new /design skill brings Claude Design's artboard workflow into the CLI and Desktop, built on artifacts."
The announcement, and the number that matters: 1.7 million views and 14,783 likes in a week. Artifacts stopped being a chat output and became the surface a design tool runs on.
"Try /design a few options for {feature} before you build. Pick your fave artboard, edit it and implement."
From the person who shipped it. The instruction is the whole workflow change: design before you build, and pick from options instead of accepting the first answer.
"/design is a research preview. It does not open Claude Design as a separate app."
The fine print most threads skipped. It needs version 2.1.233 or later, it is on Pro, Max and Team, and it stays inside Claude Code rather than launching anything.
The pattern showing up over and over is the same. Dump the idea in rough form, ask for several directions, review them as a real page, then commit.
"I do a brain dump of my ideas and then ask it to create 3 different design options for me to review."
Then Claude publishes each one as an artifact at a standalone URL so he can look at real pages instead of reading code. Posted an hour before this page was built.
"Create custom components, paste them into a blank project as reference, connect Claude Code by MCP, ask Claude to list the tokens."
A working recipe for handing Claude a design system instead of a description of one. Reference first, tokens second, generation last.
"Most AI-built websites look fine until you have seen ten of them."
The sharpest line of the week, and the reason a design step exists at all. The hero, the feature cards and the footer repeat until you give the model a reason not to repeat them.
"I challenged myself to recreate this interaction. Built using Claude Code."
A seventeen second clip of a rebuilt micro-interaction. The interesting part is the format: pick a piece of motion you admire and rebuild it as practice, in public.
One week in, there is already a switching debate, an open source clone and a competitor benchmark. That is usually a sign the category is real.
"Who loves Paper? Who hates it? Why? I'm thinking about switching away from Claude Design."
Fifty nine replies in four hours. Worth reading for the replies rather than the post. People are picking sides on a tool that is a week old.
"Claude Design is getting scary good."
Attached to a thirteen minute walkthrough of building an Awwwards level site with it. The best long form thing published on this in the last week.
"They've created an open source alternative to Claude Design."
Six days after the preview shipped. 222 likes on a clone announcement tells you how much appetite there is for this to exist outside one product.
"Had Claude make a learning example of how to build a simple procgen version of the idea."
A Three.js biome blending demo, shipped as a public artifact link and open sourced. The clearest example this week of an artifact used as the finished product rather than the draft.
A design tool now runs on top of them. Once a shipped feature depends on artifacts, publishing a page from a chat stops being a demo and starts being a distribution channel.
Every person doing good work with this is generating options and choosing. The people getting generic output are accepting the first answer and then trying to talk the model out of it.
The default look is convergent. Reference material, real tokens and a specific point of view are the only things separating your page from the other nine that used the same prompt.
The interesting question is no longer whether Claude can make a page. It is what you give it so the page does not look like everyone else's.