/design
Research preview, 2026-08-17: pick an artboard, then implement
On 2026-08-17 Nate Parrott (design at Anthropic) posted an early preview of /design in Claude Code: from Desktop or CLI, run /design a few options for {feature}, pick an artboard, edit, implement. ClaudeDevs the same day: research preview, built on artifacts, Pro / Max / Team / Enterprise. Run claude update first.
Four facts you can quote
A slash command, not a separate site
Runs inside Claude Code Desktop or CLI. The posted example is /design a few options for {feature}: editable artboards first, implementation second.
Early-preview announce
Primary sources are Nate Parrott’s post and the ClaudeDevs thread that day. The June 2026 round-trip was Design ↔ Code sync; 08-17 puts the artboard workflow inside Code.
The board lives in the same session
ClaudeDevs: the /design skill brings Claude Design’s artboard workflow into CLI and Desktop, built on artifacts. It reads the repo, matches UI style, and makes shareable mocks.
Pro / Max / Team / Enterprise
ClaudeDevs: Available on Pro, Max, Team, and Enterprise. Update Claude Code to try it. Not GA. QCode does not host Claude Design.
What /design is for: stop collapsing design into the first code step
Ask Claude Code to “build the home page” and requirements, visuals, and implementation often collapse into one move. /design splits it: requirements → visual exploration on a canvas/artboard → pick and tweak → then implement. That is Claude Design’s board inside Code, not a Figma-replacement slogan. Preview behavior follows whatever your updated binary actually exposes.
Not the same ship as the June /design sync
Around 2026-06 Claude Design could already read a design system from the repo and hand a finished board to Claude Code. The 08-17 news is the editor and prompting living inside Code, without opening claude.ai/design and pasting screenshots back. Week 34 (2026-08-17–21) logged it in whats-new. It is still a research preview.
Timeline
Claude Design showed up from Anthropic Labs as canvas + chat (later recaps). A separate design assistant, not yet a Code slash command.
Two-way Design ↔ Code: codebase-aware imports, design-system ingest, /design already typed in the terminal. That round was the round-trip, not the 08-17 artboard preview packaging.
Nate Parrott: early preview. ClaudeDevs: skill, artifacts, plan gate. claude update. As of 2026-08-30 this page still calls it a research preview.
Confirmed vs rumor
Confirmed
Primaries are the 2026-08-17 Nate Parrott post and ClaudeDevs thread: Desktop + CLI, artboards, artifacts, research preview, Pro/Max/Team/Enterprise. Repo-aware UI matching is in the follow-up posts.
Rumor / misread
“/design means Claude Design is GA” — they still say research preview. “QCode hosts Claude Design” — QCode is a model API. “Any API key unlocks the official /design skill” — ClaudeDevs named plan tiers; trust the client.
Design-first vs just implement
When /design is the right first move
Several visual directions, must match existing components, need a mock before code. The official example is a few options for {feature}. Pick an artboard, then implement in the same session.
When you can skip the board
No UI, or the system is already locked and you are filling logic. Preview usage still spends the shared Claude Code / chat pool.
Official path (no platform switch required)
Update Claude Code, type /design … in Desktop or CLI, pick a direction on the artboard, then ask for implementation. This page does not describe QCode as the host of Claude Design. Model routing is separate: if your agent uses an API, pick models that are actually sold. No bypass of plan gates or client spoofing.
QCode does not run Claude Design
/design is a skill / slash command in the Claude Code client. Artboards and artifacts are Anthropic product surface. QCode bills API usage at official price × service fee. Bring your own key for models that are sold; do not expect QCode to render Claude Design artboards.
FAQ
Does /design work in both CLI and Desktop?
Nate Parrott and ClaudeDevs both said Desktop or CLI. Update past the announce build. If the command is missing, trust claude --version and /help on your machine.
GA or preview?
ClaudeDevs: research preview. Capabilities, quota, and UI will move. Do not freeze it as GA in a production spec.
Which Anthropic plan?
ClaudeDevs: Pro, Max, Team, and Enterprise. Whatever the signed-in client actually enables — this page does not invent extra tiers.
How is this different from the June /design?
June reporting was Design ↔ Code round-trip and design-system import. 08-17 puts Design’s editor and prompting inside Code and emits editable artboards via artifacts.
Will QCode render those artboards?
No. Artboards live in Claude Code / Claude Design. QCode is a model API. Not the same product.
Where is usage billed?
June reporting said Design shares the Code / chat pool. The 08-17 preview did not publish a second ledger. Trust /usage and the plan page.
Sources
Nate Parrott https://x.com/nateparrott/status/2089470636796059754 (2026-08-17). ClaudeDevs same-day thread: research preview, artifacts, Pro/Max/Team/Enterprise. code.claude.com/docs/en/whats-new Week 34 (2026-08-17–21). June round-trip is background, not the 08-17 note. Rechecked 2026-08-30.
You can bring your own model; the board still lives in Claude Code
QCode does not host Claude Design. For API access, official price × service fee on models that are actually sold.
Related
Claude Code guide
The client that hosts slash commands — not the Design product.
Claude Code slash commands
The rest of the command list; keep /design distinct from /effort and /model.
Claude Code Ultrathink / Ultracode
The high-effort implement path that often follows a chosen artboard.
Public posts from Anthropic staff and ClaudeDevs plus Claude Code whats-new — not a guarantee about preview behavior. Whether the command exists depends on your client version. QCode does not bypass plan gates.