이미지: X — 테스팅카탈로그 영상 갈무리
Summary
- The /design command has been added to Claude Code CLI and desktop as a research preview
- It brings the artboard workflow from Claude Design into the artifacts framework, generating multiple editable UI drafts
- Reactions were mixed, with some users voicing concerns over the trust level required so early after launch
- 기능명
- /design (연구 프리뷰)
- 지원 환경
- 클로드 코드 CLI, 데스크톱
- 기반 기술
- Claude Design 아트보드 워크플로우, artifacts 기반
- 사용 흐름
- 아트보드 생성 → 선택 → 수정 → Claude가 구현
- 발표 시점
- 2026년 8월 17일(UTC 23:49)
A tool that once only wrote code now draws screens too
Until now, Claude Code was a tool for writing and fixing code inside the terminal. If a screen design was needed, a person had to sketch the layout first and describe it in words to turn it into code. The newly added /design command reverses this order. Running the command has Claude generate several editable screen drafts — so-called "artboards" — first, and once the user picks and refines one, Claude implements it as actual code.
The news was shared by the ClaudeDevs account and picked up by TestingCatalog. According to the announcement, /design is still in research preview and layers the artboard workflow on top of artifacts, Claude Code's existing output format that lets code or documents Claude produces be displayed in a separate window for immediate review and editing. The artboard concept itself comes from Claude Design, referring to a workflow of comparing and refining multiple UI drafts side by side.
How to try it
The feature has been confirmed available through both the Claude Code CLI and the desktop app. It starts simply by typing /design into the command prompt, with no additional setup required.
- Open Claude Code CLI or the desktop app and type /design.
- Claude generates and displays several editable artboards for the requested screen.
- Pick the draft you like.
- Adjust colors, layout, and copy directly, or request changes in words.
- Hand off the finalized artboard to Claude, which implements it as working code.
Beyond being a research preview, the announcement did not specify any plan tier or regional restrictions. For example, it could be used to generate several landing page drafts for a web service and turn one into deployment-ready code, or to iteratively refine an internal dashboard layout.
Reactions: anticipation mixed with caution
Reactions were mixed right after the announcement. One user noted on their account that it was "asking for a lot of trust for launch week." Since a single command can touch multiple files at once, there is concern about how much code-editing authority should be granted to an unproven early version. On the other hand, some responses focused on the shift from artboards as fixed deliverables handed off by a person to something an agent regenerates on the fly.
| Category | Before | After /design |
|---|---|---|
| Draft creation | Person manually writes drafts | Claude auto-generates multiple artboards |
| Editing method | Request via text, then check code | Adjust directly within the artboard |
| Output location | Separate documents/images | Edited directly within artifacts |
Editor's take
This /design feature is best read as a signal that competition among coding agents is moving past "who codes well" toward "who can be trusted with the whole screen." Rival tools like Cursor are also testing closed betas of tabs that survey an entire codebase, pointing in a similar direction. Across the board, agents are being pushed to operate not on single lines of code but on the full context of a project — now including design.
The generational shift is noticeable. With older coding agents, asking to "make the login screen look nicer" would simply drop a chunk of code. If it wasn't to your liking, you had to rewrite the prompt from scratch. What's different here is the addition of a "choose and refine" step in between. The very process of comparing multiple drafts side by side resembles what people used to do in design tools.
In practical terms, the "research preview" label shouldn't be taken lightly yet. Rather than attaching it to a production codebase, it makes more sense to try it first on side projects or prototypes and check for yourself how many files get touched at once. As one user pointed out, a feature that changes multiple files with a single command isn't something to merge without review just yet.
Over the coming weeks, feedback from developers who actually use the feature will likely pour in, and how well the artboards translate into production-quality code will be the key question. It's also worth watching when the research preview label comes off.
