Skip to content
Back to search

design-studio

MarketplaceWorks with Claude CodeGitHub

AI design studio for Claude Code: describe an app, answer a few questions, get a designed, responsive, clickable screen set on localhost.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/jxngrx--design-studio/badge.svg)](/listings/jxngrx--design-studio)

HTML

<a href="/listings/jxngrx--design-studio"><img src="/api/listings/jxngrx--design-studio/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

You need **Node.js 16.7+** (18+ recommended), **git**, and the **[Claude Code](https://docs.claude.com/en/docs/claude-code) CLI** (`claude` on your `PATH`, signed in). The studio uses it to do the designing; there are no API keys to configure.

npx skills add jxngrx/design-studio

That installs the `/design-studio` skill. Restart Claude Code, run `/design-studio`, and say yes when it offers to set up the local app in `~/.design-studio` (a one-time download).

<details> <summary>Other ways to install</summary>

**Shell installer** (skill and app in one step)

curl -fsSL https://raw.githubusercontent.com/jxngrx/design-studio/main/install.sh | bash

**Claude Code plugin marketplace**

/plugin marketplace add jxngrx/design-studio
/plugin install design-studio@design-studio

**Manual**

git clone https://github.com/jxngrx/design-studio.git ~/.design-studio
mkdir -p ~/.claude/skills/design-studio
cp ~/.design-studio/skills/design-studio/SKILL.md ~/.claude/skills/design-studio/

**Update:** run the install command again (it pulls the latest). **Uninstall:** delete `~/.design-studio` and `~/.claude/skills/design-studio`.

</details>

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 11 lines
  1. {
  2. "name": "design-studio",
  3. "owner": { "name": "jxngrx" },
  4. "plugins": [
  5. {
  6. "name": "design-studio",
  7. "source": "./",
  8. "description": "AI design studio skill. On first use it offers to install the local app to ~/.design-studio."
  9. }
  10. ]
  11. }
README.md · README · 269 lines · 1 finding marked
  1. <div align="center">
  2. <img src="docs/logo.svg" width="84" alt="Design Studio logo">
  3. # Design Studio
  4. **Describe an app. Answer a few questions. Get a designed, responsive, clickable screen set.**<br>
  5. A local AI design studio that lives inside Claude Code.
  6. [![License: MIT](https://img.shields.io/badge/license-MIT-e8743b.svg)](LICENSE)
  7. ![Node](https://img.shields.io/badge/node-%E2%89%A516.7-3c873a.svg)
  8. ![Zero dependencies](https://img.shields.io/badge/dependencies-0-lightgrey.svg)
  9. ![Runs locally](https://img.shields.io/badge/runs-100%25%20local-14120f.svg)
  10. ![Claude Code skill](https://img.shields.io/badge/Claude%20Code-skill-8d8778.svg)
  11. <br>
  12. <img src="docs/screenshots/01-new.png" alt="Design Studio, the New screen" width="880">
  13. </div>
  14. <br>
  15. | **~90x** | **$0.002** | **0** | **100%** |
  16. |:---:|:---:|:---:|:---:|
  17. | cheaper per screen than a default Claude Code call | to draw one screen in economy mode | dependencies, no build step | local: your files, your machine |
  18. <br>
  19. Design Studio is a Figma-style canvas that runs on `localhost`. You write the idea in plain language; Claude asks the few questions that actually change the design, proposes the screens, and only then draws them. Everything is plain HTML and CSS you can open, edit, or hand to a developer. No account, no cloud, no build step.
  20. ## Watch it
  21. [![Design Studio in 23 seconds](docs/demo.jpg)](docs/demo.mp4)
  22. ## Highlights
  23. | | |
  24. |---|---|
  25. | **Idea in, project out** | Submit an idea and a project appears at once, named by Claude. Its questions and progress live on the server, so switching tabs or reloading never loses them. |
  26. | **Questions that matter** | 3 to 4 idea-specific, multi-select questions plus platform. Pick Mobile and it asks which phone (iPhone, Pixel, Samsung) and designs in iOS or Material conventions accordingly. |
  27. | **You approve the screens** | Rename, remove, or add screens before anything is drawn. It designs exactly that list. |
  28. | **Responsive web** | Web projects are built fluid. Preview Mobile 390, Tablet 820, Laptop 1280 and Desktop 1440 with one click. |
  29. | **Clickable prototype** | Play the flow like the real thing. Buttons, tabs and cards navigate by built-in links, hotspots you draw, or by matching their label to a screen name. |
  30. | **Variants** | Ask for three alternative takes on any screen, compare them next to the original, keep one. The original is saved to `history/`. |
  31. | **Design system, editable live** | Every project gets a CSS design system. Change a token and every screen updates. |
  32. | **Cheap by design** | Economy mode (default) draws on a small model with lean calls and three screens per call: about **$0.002 per screen** in my measurements, roughly 90x less than a default Claude Code call per screen. Every project shows its measured cost. |
  33. | **Design sources (MCP)** | Connect Mobbin, Figma, Canva, Subframe, Playwright (screenshots of Dribbble, Awwwards, Behance...) or your own MCP server, and choose which ones a project uses. Research mode also searches the galleries directly. |
  34. | **Bring your skills** | Plug in installed Claude skills (impeccable, frontend-design, ui-ux-pro-max, taste-skill and more). Recommended UI skills are added automatically when installed. |
  35. ## Screenshots
  36. <table>
  37. <tr>
  38. <td width="50%"><img src="docs/screenshots/02-questions.png" alt="Questions and screen list"><br><sub><b>Questions and an editable screen list.</b> Multi-select, platform and phone, then you decide what gets drawn.</sub></td>
  39. <td width="50%"><img src="docs/screenshots/03-generating.png" alt="Screens drawing themselves"><br><sub><b>Screens sketch themselves,</b> then become live thumbnails. Leave the page any time, it keeps going.</sub></td>
  40. </tr>
  41. <tr>
  42. <td><img src="docs/screenshots/04-canvas.png" alt="Canvas with an explorer sidebar"><br><sub><b>An explorer-style sidebar.</b> Projects are folders; sections and screens expand like a file tree.</sub></td>
  43. <td><img src="docs/screenshots/05-responsive.png" alt="Responsive preview at mobile width"><br><sub><b>Responsive by default.</b> The same site at Mobile 390, with a working menu.</sub></td>
  44. </tr>
  45. <tr>
  46. <td><img src="docs/screenshots/06-design-system.png" alt="Design system panel"><br><sub><b>Design system panel.</b> Edit colors, fonts and sizes; every screen updates live.</sub></td>
  47. <td><img src="docs/screenshots/10-variants.png" alt="Variants panel"><br><sub><b>Variants.</b> Bolder, Calmer, New layout, or a direction you type.</sub></td>
  48. </tr>
  49. <tr>
  50. <td><img src="docs/screenshots/07-prototype-player.png" alt="Prototype player"><br><sub><b>Prototype player.</b> Click real buttons and tabs to move through the flow.</sub></td>
  51. <td><img src="docs/screenshots/08-prototype-edit.png" alt="Prototype hotspot editing"><br><sub><b>Prototype mode.</b> Links found in the design show as dashed boxes; draw your own hotspots.</sub></td>
  52. </tr>
  53. <tr>
  54. <td colspan="2"><img src="docs/screenshots/09-settings-skills.png" alt="Settings, skills tab"><br><sub><b>Settings.</b> Model, mode, parallelism, web access, and auto-added UI skills.</sub></td>
  55. </tr>
  56. </table>
  57. ## Install
  58. You need **Node.js 16.7+** (18+ recommended), **git**, and the **[Claude Code](https://docs.claude.com/en/docs/claude-code) CLI** (`claude` on your `PATH`, signed in). The studio uses it to do the designing; there are no API keys to configure.
  59. ```bash
  60. npx skills add jxngrx/design-studio
  61. ```
  62. That installs the `/design-studio` skill. Restart Claude Code, run `/design-studio`, and say yes when it offers to set up the local app in `~/.design-studio` (a one-time download).
  63. <details>
  64. <summary>Other ways to install</summary>
  65. **Shell installer** (skill and app in one step)
  66. ```bash
  67. curl -fsSL https://raw.githubusercontent.com/jxngrx/design-studio/main/install.sh | bash
    • Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
    • Line 91 on GitHub
  68. ```
  69. **Claude Code plugin marketplace**
  70. ```text
  71. /plugin marketplace add jxngrx/design-studio
  72. /plugin install design-studio@design-studio
  73. ```
  74. **Manual**
  75. ```bash
  76. git clone https://github.com/jxngrx/design-studio.git ~/.design-studio
  77. mkdir -p ~/.claude/skills/design-studio
  78. cp ~/.design-studio/skills/design-studio/SKILL.md ~/.claude/skills/design-studio/
  79. ```
  80. **Update:** run the install command again (it pulls the latest). **Uninstall:** delete `~/.design-studio` and `~/.claude/skills/design-studio`.
  81. </details>
  82. ## Use it
  83. **From Claude Code.** Type `/design-studio`, or just say what you want:
  84. > Design a meal-planning app for busy families.
  85. Claude starts the studio, opens `http://localhost:4400`, and your idea lands on the analysis screen. If you already described the project in chat, it opens with the idea filled in.
  86. **On its own.**
  87. ```bash
  88. cd ~/.design-studio && node server.mjs # then open http://localhost:4400
  89. ```
  90. ### The flow
  91. 1. **Describe** the idea on the New screen. Pick a model, a mode (*Claude design* or *Research and design*), and optional skills.
  92. 2. **Answer** the questions. Choose a platform; for mobile, choose the phone.
  93. 3. **Edit the screen list.** Rename, remove, add.
  94. 4. **Watch** the screens draw. Open the canvas any time.
  95. 5. **Refine.** Click a screen and tell Claude what to change, generate variants, edit the design system, or play the prototype.
  96. ### Deep links
  97. Handy for bookmarks and scripts.
  98. ```text
  99. #new the New screen
  100. #settings?tab=skills a settings tab
  101. #p/<Project>?vp=mobile a project at a viewport (mobile, tablet, laptop, desktop)
  102. &panel=ds|insp|var open a side panel
  103. &mode=proto prototype mode
  104. &play=<screen id> open the player on a screen
  105. &select=<id>&zoom=0.4 select a screen, set the zoom
  106. ```
  107. ## Recommended skills
  108. Design Studio works on its own and gets better with UI skills installed. Turn on **Settings, Skills, Auto-add UI skills** and any of these that are installed are used on every project (4 skills maximum per run).
  109. | Skill | Repository | Good at |
  110. |---|---|---|
  111. | impeccable | [pbakaus/impeccable](https://github.com/pbakaus/impeccable) | Avoiding generic "AI slop": type, color, spacing, motion |
  112. | frontend-design | [anthropics/claude-code](https://github.com/anthropics/claude-code/tree/main/plugins/frontend-design) | Anthropic's official distinctive-UI guidance |
  113. | ui-ux-pro-max | [nextlevelbuilder/ui-ux-pro-max-skill](https://github.com/nextlevelbuilder/ui-ux-pro-max-skill) | Styles, palettes, font pairings, UX rules |
  114. | taste-skill | [Leonxlnx/taste-skill](https://github.com/Leonxlnx/taste-skill) | Polished marketing and landing pages |
  115. Read a skill before installing it; skills are instructions your agent will follow.
  116. ## Design sources and references
  117. Each project has an **Inspiration** panel for links and images that Claude uses whenever it designs or edits that project, plus a **Design sources (MCP)** section.
  118. - **Connect sources** in Settings, Connections (or from the Inspiration panel): Mobbin, Figma, Canva, Subframe, Playwright, Context7, shadcn, or a **custom MCP server** (HTTP, SSE, or a local command). Servers are added through the `claude` CLI, so they are the same ones Claude Code uses. Servers that need a sign-in are authorized once with `/mcp` in Claude Code.
  119. - **Choose per project** with **+ MCP** in the first chat box. Selecting any makes the project research first: Claude pulls real screens and flows from those sources and writes style notes the screens follow.
  120. - **Cost note:** user-added MCP servers are loaded alone, so calls stay lean. Claude.ai connectors cannot be isolated, so a research step that uses one carries all of that connector's tools and costs more.
  121. - **No MCP?** Research mode still searches Mobbin, Dribbble, Behance, Awwwards and Land-book through web search, and you can paste pages under *Pages to read first*. The studio reads page text, not images, so MCP sources or screenshots give richer inspiration.
  122. ## What it costs
  123. > **Short version:** a default Claude Code call spends about **$0.19** on one screen, mostly on ~140K tokens of overhead. Design Studio's economy mode spends about **$0.002**.
  124. Design Studio runs on your own Claude Code login, so usage counts against your plan (or API billing). A normal `claude` call carries about 140K tokens of overhead (system prompt, hooks, skills, connector tools), which is most of the price of a screen. **Economy mode** removes it: a short system prompt, only the tools needed, no hooks or connectors, a small model on low effort for drawing, three screens per call, and terse markup that reuses the design system.
  125. ### Measured
  126. Real numbers from Claude's own usage reports, one screen of the same size, one machine (yours will differ):
  127. | One screen | Cost | vs default call |
  128. |---|---:|---|
  129. | Default Claude Code call (Sonnet 5.5) | **$0.186** | `██████████████████████████████` |
  130. | Lean call, same model | $0.096 | `███████████████` |
  131. | Lean call, Haiku 5.5 | $0.005 | `▏` 35x cheaper |
  132. | Lean, Haiku, 3 screens per call | **$0.002** | `▏` **~90x cheaper** |
  133. | Whole 3-screen project, plan + design system + screens, all Haiku | **$0.018** | |
  134. ### Estimated against Claude.ai artifacts
  135. I did **not** measure artifacts. This estimate prices a Sonnet-drawn artifact page like the "lean call, same model" row above ($0.096 per screen), because a chat turn also has little overhead. On a Claude.ai plan, artifacts use your plan limits rather than dollars, so treat this as a token-cost comparison, not a bill.
  136. | Job | Design Studio (economy) | Same screens as Sonnet artifacts | Roughly |
  137. |---|---:|---:|---|
  138. | 1 screen | $0.002 | $0.096 | **~45x cheaper** |
  139. | 3-screen project (measured) | $0.018 | ~$0.29 | **~16x cheaper** |
  140. | 9-screen project (calculated) | ~$0.03 | ~$0.86 | **~29x cheaper** |
  141. Whole projects save less than single screens because planning and the design system are paid once on top. The model does most of the work here: Haiku is much cheaper than Sonnet, and plain Haiku in a chat would be cheap too. What Design Studio adds is the multi-screen flow, consistency, variants and prototype in one pass. A single artifact on a stronger model can look richer than Haiku; raise **Planning model** in Settings, Generation if you want better plans, or turn Economy mode off for the full-power flow.
  142. ### Design Studio or an artifact?
  143. | | Claude artifact | Design Studio |
  144. |---|---|---|
  145. | One page, quick | Best choice | Overkill |
  146. | A whole app or site flow | Many manual turns | One pass, consistent |
  147. | Shared design system and header | You re-prompt for it | Built in |
  148. | Variants, prototype, responsive preview | No | Yes |
  149. | Your files | Hosted by Claude | Local HTML you own |
  150. | Shareable link | Yes | Not yet |
  151. | Cost visible per project | No | Yes |
  152. | Setup | None | One command |
  153. Every project shows its measured cost on its page, and Settings shows the total spent.
  154. ## How it works
  155. ```text
  156. browser (index.html + ui/*.js) <-> server.mjs (127.0.0.1:4400) -> claude -p (your Claude Code login)
  157. |
  158. screens.json projects.json settings.json proto.json screens/*.html refs/ history/
  159. ```
  160. - **No build step, no dependencies.** A single Node file serves static files and a small JSON API; the UI is plain JavaScript.
  161. - **Each screen is one HTML file** in `screens/`, linked to its project's design system stylesheet. Open them in any browser or editor.
  162. - **Projects are state machines** on the server: `analyzing`, `brief`, `generating`, `ready`, `partial`, `error`. Questions, edits and logs survive reloads.
  163. - **Failures are visible.** Every step is logged, each screen retries once automatically, and failed screens show the reason with a one-click retry.
  164. <details>
  165. <summary>Repository layout</summary>
  166. ```text
  167. server.mjs server + AI pipeline (analysis, planning, drawing, variants, tokens, prototype)
  168. index.html canvas and frame rendering
  169. ui/ sidebar, New screen, project page, panels, prototype, settings, viewports
  170. skills/design-studio/ the Claude skill (SKILL.md)
  171. scripts/ export.sh builds a clean shareable copy
  172. examples/seed/ the example project created on first run (release builds)
  173. install.sh one-command installer
  174. docs/ logo and screenshots
  175. ```
  176. </details>
  177. ## Privacy and safety
  178. - Everything runs on your machine. The server listens on `127.0.0.1` only and rejects requests from other hosts and other sites.
  179. - Your designs, references and settings stay in the install folder. Nothing is uploaded by Design Studio itself.
  180. - It calls the `claude` CLI, so prompts (your idea, answers, reference content) go to Anthropic under your own Claude account, like any Claude Code session.
  181. - Web research is optional and can be turned off in Settings. Fetched page text is treated as data, never as instructions.
  182. - Claude runs with the studio folder as its working directory and is allowed to read, edit and write files there (plus fetch web pages when web access is on). Review a skill before you enable it.
  183. ## Troubleshooting
  184. | Problem | Fix |
  185. |---|---|
  186. | "Could not reach the studio server" | Start it: `cd ~/.design-studio && node server.mjs` |
  187. | Nothing is generated or every step fails | Check `claude --version` and that you are signed in. Failed screens list their reason; use **Retry failed screens**. |
  188. | Port 4400 is busy | `PORT=4500 node server.mjs` |
  189. | Generation is slow or expensive | Keep Economy mode on, lower **Parallel screens**, and avoid claude.ai connectors in research. |
  190. | A skill is missing from the list | Install it, then press **Refresh** in the skills picker. |
  191. ## Roadmap
  192. Versions with undo, export to code (HTML bundle, React with Tailwind), share links, and a one-click critique pass are next. Ideas and pull requests are welcome.
  193. ## License
  194. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.