🎯 What the /design Skill Is
Anthropic launched the /design skill — accessible by default in Claude Code and Cowork. It gives you a live canvas to visualize any design you're creating: presentations, websites, social media images, infographics, email newsletters — and you can edit text, size, colors, and layouts directly on the canvas. 0:00
The canvas is a live artifact: anyone on your team can open it, make edits, and download assets directly from it. It's the Claude Design tool's features, now usable from inside Claude Code/Cowork — alongside skills and connectors, so you stop tool-hopping between apps.
🧠 Vibe Designing vs. Real Designing
The core insight: the canvas is nice, but a canvas alone doesn't produce good designs. 2:11
| Vibe designing | Real designing |
|---|---|
| Throw in a quick prompt, generate the design | Pre-establish as much of the design as possible before prompting |
| Endless iteration loop, burns tokens | One-shot prompt brings you 80–90% of the way there |
| Frustrating, doesn't reach a great design | Final 10% adjusted quickly on the canvas |
"Pre-establish the brand guides, colors, fonts, styles, format, layout, structure — ideally even the copy. If that's defined well, a one-shot prompt gets you 80–90% there."
🛠️ The 4-Step Process
Ben's system for consistent, fast, brand-aligned designs. 3:20
- Design system — a folder with colors, fonts, styles, logos, images
- Templates — one example per repetitive use case, so Claude doesn't guess layouts
- Skills — package the system + template into a skill that automates the use case
- Human in the loop — the skill outputs into the /design canvas for final edits
🎨 1. Create a Design System
The foundation: a folder Claude can always reference. 6:26
What's in it: color guides, fonts, shadows, logos, image assets, voice profiles. Ben gives Claude access to this folder every time, so any design is instantly brand-aligned. For clients, build one design system per client — "worth doing once, because all your designs are brand-aligned forever."
How to build one (easy): his free "design system creator" skill + the free Firecrawl connector (scrapes websites more comprehensively than Claude natively can) → throw in your existing website, example brand assets, or reference sites you like → it extracts everything and returns a zip with your design system.
📐 2. Creating Templates
The step most people skip — and one of the most important. 8:03
Why it matters: templates remove the guesswork from layouts and structures — where most of the iteration happens. If you have past examples, give Claude the design system + one example and it builds a template. If not, find examples online (styles/layouts for your use case) and ask: "build me templates around these in my brand style using /design."
📦 3. Creating Design Skills
Package the system + template into a reusable skill — automation without prompting. 9:30
The skill contains: the templates/examples embedded, the instruction to always use the brand system, copywriting rules, and an input definition (LinkedIn post, X post, etc.). Ben's examples: presentation builder, carousel builder, infographic/social image builder.
The self-improvement tip: add a rule — "whenever a user approves a final design, save it as a good example in the skill automatically." The skill accumulates examples and gets better over time.
🧭 4. Human in the Loop
The most important rule when building the skill — and the part that ties it all together. 11:18
The rule: "before giving the output, the skill runs
/design as part of the workflow." You build the human-in-the-loop into the skill itself, so the final design lands on the canvas where you make the last adjustments, then export and use it.💡 Key Takeaways
- /design is the canvas, not the answer — it's where you make the final 10% of edits, not where you generate from scratch.
- Pre-establish the design before prompting — brand guides, colors, fonts, format, layout, copy → one-shot prompt gets 80–90%.
- A design system is a folder — colors, fonts, logos, images, voice profiles; give Claude access every time.
- Templates kill the iteration loop — one example per use case means Claude doesn't guess layouts.
- Package into skills — embed the template + brand system + copy rules, and automate the whole use case.
- Make skills self-improving — auto-save approved designs as new examples.
- Human in the loop is a rule, not a hope — force the skill to output into /design for final edits.