🎨 What /design Is
Anthropic just launched an official /design skill for Claude Code — it brings Claude Design's popular artboard workflow directly into Claude Code. "You can use it wherever you use Claude Code — terminal or the VS Code extension." Update, type /design, and it's built in. 0:00
🖼️ The Canvas Editor
The artifact opens in a canvas with Figma-style editing: change accent colors, adjust spacing and font scale, tweak fonts and weights via the right-hand sidebar, and edit text in place. "A much better experience when you're polishing a website for production." 0:47
| Feature | What it does |
|---|---|
| Live editing | Accent colors, spacing, font scale, font weights — from the canvas |
| Sharing | Toggle to share with peers/clients (like a Google Doc link) |
| Comments | Leave comments on the canvas |
| Chat edits | Apply bigger changes by chatting from the same Claude Code session |
"One clear benefit: this whole artifact is connected to your Claude Code. Leave comments, or chat with it to apply bigger changes." 1:26
⚔️ /design vs Claude Design
The obvious question — how is this different from Claude Design? The answer is context. With /design in Claude Code, one prompt captured "all our designs, all the details, and all the numbers were correct." With Claude Design, the same prompt produces default fonts, a generic black-and-blue palette, and incorrect details. 2:00
🧠 The Context Advantage (ARMS)
"Claude Code actually doesn't work from just one prompt — it also works on your workspace context." Jay teaches context engineering through the ARMS framework: connect Claude Code to your Applications, set up Routines, and connect Memory (design systems, brand books, business details) + Skills. 2:20
🔌 Using Your Own Skills
A second advantage: you can combine /design with your own skills. Jay invokes his /generate skill (which connects to AI video/image models on a pay-as-you-go basis) to generate a dot-matrix robot video and place it as the landing page's background. 4:22
/design in Claude Code wins. 5:35
🚀 Deploy Straight to Vercel
The final difference: deployment. Ask Claude Design to "push this to Vercel" and "it tells me to do it myself." Ask Claude Code the same thing and "it did just that — it's now live at this URL." 5:58
✅ Key Takeaways
- /design brings Claude Design's artboard workflow into Claude Code — one prompt produces an editable, shareable artifact.
- The canvas is Figma-like: live color/spacing/font editing, comments, sharing links, and chat-driven edits.
- Context is the whole difference. Claude Design has no memory; Claude Code has your workspace context — so the same prompt yields correct details vs generic defaults.
- ARMS framework: Applications + Routines + Memory + Skills are what make one prompt produce a non-vibe-coded design.
- Your own skills work with /design (e.g. /generate for AI media) — Claude Design locks you to default skills.
- Deploy seamlessly: Claude Code pushes to Vercel; Claude Design tells you to do it yourself.
🔗 Resources & Links
- 📺 Original video — RoboNuggets