Anthropic product designer Nate Parrott announced on August 18 that the company is releasing an early preview of a /design command inside Claude Code, letting developers generate interactive UI mockups directly in the terminal or desktop app before writing implementation code. The command accepts prompts such as "/design a few options for {feature}" and returns multiple editable artboards rendered through the same Artifacts runtime that powers Claude Code's live previews.

Claude reads the existing codebase to match the project's current UI style and design tokens, then produces shareable prototypes as Artifacts that carry into the build step. The workflow — generate artboards, pick one, edit inline, then have Claude implement it — brings the artboard canvas from the standalone Claude Design web app (launched in April 2026) into the coding session itself, eliminating the context switch of exporting from claude.ai/design and pasting back into the IDE.

What's new

  • Command: /design a few options for {feature} runs in Claude Code CLI and Desktop.
  • Output: Multiple editable UI artboards as Artifacts, selectable and refinable in place.
  • Integration: Reads the repository to match existing design system (colors, typography, components) — though automatic design-system import is not yet confirmed for this preview.
  • Availability: Research preview for Claude Pro, Max, Team, and Enterprise subscribers; requires Claude Code version 2.1.234 or newer (claude update).
  • Known limitation: Token-hungry — generating multiple artboards on top of an active coding session can press context and usage limits.

Why it matters

The /design command collapses the design-to-code handoff into a single session. For individual developers and small teams without a dedicated designer, it lowers the barrier to exploring multiple layout directions before committing to one. For larger organizations already using Claude Design's design-system import and export pipeline (Canva, PDF, PPTX, HTML), the CLI version offers a faster path from idea to shipped code when the implementer is already in the repo — though it does not yet replace the full web app's stakeholder-facing export formats or guaranteed design-system fidelity.

Our take

The real shift is not the mockup generation itself — developers could already chain Claude Design output into Claude Code manually — but the packaging of that workflow into a single, discoverable command that respects the repo's existing style. The token cost remains the practical gate: treat /design as a deliberate tool for kicking off new screens, not a default for every UI tweak.

Sources