Claude Code is adding a /design skill that brings Claude Design’s artboard workflow into the command-line interface and desktop app. In a ClaudeDevs post, the feature is described as a research preview built on artifacts, allowing users to generate editable interface concepts, select one, make changes, and ask Claude to implement it.
The feature is available on Pro, Max, Team, and Enterprise plans, according to a follow-up post from ClaudeDevs. The announcement does not state how the new workflow differs from the existing Claude Design experience, a question raised by several commenters.
From artboards to implementation
The supplied desktop workflow shows /design being used to request a redesign of the composer based on reported usage patterns. Claude generates a “Composer redesign” artifact with options including “Adaptive row” and “Dense icon-only.”
One proposal keeps the existing layout largely intact while replacing MCP with the more frequently used “Switch Model” control. Another elevates frequent or recent actions into an adaptive row, with less-used commands placed under a “More” menu. The proposed controls include “Attach file,” “Switch model,” “Dictate,” “More,” and “Edit.”
The workflow also includes a five-step onboarding checklist that moves billing to the end, allowing users to reach the editor before being asked for payment details. A prompt reading “Ok, implement option B with my edits” illustrates the intended handoff from design selection to code changes.
Claude reports that the workflow ran the /design skill, executed four commands, created four files, ran two additional commands, and used a tool with a reported change count of “+212 -0.” The artifact includes save and export options and links through a claude.ai/code/artifact/ address.
A separate example uses the prompt, “/design for me what you imagine to be the ideal version of the bloom app.” The interface also lists /design consent and revoke commands.
Questions about overlap and access
The announcement prompted claims that similar functionality was already possible in the command line or within VS Code. One commenter mentioned using a /design command in another coding tool for months, while another described a workflow involving UI snippets pasted into an editor and paired with prompts.
Some users also reported difficulty accessing the research preview. One commenter with the latest macOS desktop app claimed that /design still opened the older version. The available material does not indicate whether the rollout is staged or how access is being granted beyond the listed subscription tiers.
Another open question concerns the relationship between /design in Claude Code and Claude Design as a separate experience. ClaudeDevs did not provide a comparison in the posts included with the announcement.
For now, /design appears to offer a direct path from editable interface concepts to implementation within Claude Code. Its practical value will depend on access, token consumption, the quality and variety of its generated designs, and how clearly it is separated from Claude Design.
Source: ClaudeDevs on X
