Skip to content
Back to search

superdesign

MarketplaceWorks with Claude CodeGitHub

The Superdesign UI, presentation, and graphics skill for Claude Code, published by Superdesign dev, Inc.

Safety scan

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

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/superdesigndev-superdesign-skill/badge.svg)](/listings/superdesigndev-superdesign-skill)

HTML

<a href="/listings/superdesigndev-superdesign-skill"><img src="/api/listings/superdesigndev-superdesign-skill/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.

**Any coding agent** — installs the skill for any of the [70+ supported coding agents](https://github.com/vercel-labs/skills#supported-agents):

npx skills add superdesigndev/superdesign-skill

**Claude Code** — install it as a plugin instead, so it stays namespaced and updates with `/plugin update`:

/plugin marketplace add superdesigndev/superdesign-skill
/plugin install superdesign@superdesign

The skill is then invoked as `/superdesign:superdesign`. (Do not also run `npx skills add` in Claude Code — that installs a second, unnamespaced copy of the same skill.)

Either way, install the CLI it drives:

npm install -g @superdesign/cli@latest
superdesign login

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 · 24 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "$schema": "https://json.schemastore.org/claude-code-marketplace.json",
  3. "name": "superdesign",
  4. "description": "The Superdesign UI, presentation, and graphics skill for Claude Code, published by Superdesign dev, Inc.",
  5. "owner": {
  6. "name": "Superdesign dev, Inc.",
  7. "email": "support@superdesign.dev",
  8. "url": "https://superdesign.dev"
  9. },
  10. "plugins": [
  11. {
  12. "name": "superdesign",
  13. "source": "./",
  14. "category": "design",
  15. "tags": [
  16. "design",
  17. "ui",
  18. "design-systems",
  19. "graphics",
  20. "presentations"
  21. ]
  22. }
  23. ]
  24. }
README.md · README · 329 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Superdesign: UI, presentations, and graphics for coding agents
  2. **Stop shipping AI-slop UI.** Coding agents write great code and mediocre interfaces: generic layouts, default shadcn everything, no taste. Superdesign is the skill that gives your agent design judgment, so the UI it ships actually looks considered.
  3. Install it once and your agent (Claude Code, Cursor, Codex, and 70+ others) can find real design direction and generate + iterate high-quality UI, presentations, and graphics on an infinite canvas, all without leaving your terminal.
  4. > Powered by [superdesign.dev](https://superdesign.dev), the AI product design agent.
  5. [![Superdesign skill demo](https://i.ytimg.com/vi/AZYJWyWZ6pQ/maxresdefault.jpg)](https://youtu.be/AZYJWyWZ6pQ)
  6. *▶ Watch the skill in action.*
  7. ---
  8. ## What is Superdesign?
  9. **Superdesign is an AI product design agent.** It gives coding agents (Claude Code, Cursor, Codex, and 70+ others) real design judgment, so the UI they ship looks considered instead of generic.
  10. - **What it does** — finds design direction, sets up design systems, approves presentation outlines, and generates + iterates high-quality UI, slide decks, and graphics on an infinite canvas.
  11. - **Who it's for** — developers, indie hackers, and product/UI designers who want to go from idea to shippable UI fast without leaving their coding agent.
  12. - **How it's different** — style-preset skills just swap in a theme or a component library. Superdesign designs *into* your existing design system: it reads your code for context, gathers real style references, and produces branchable drafts you refine.
  13. - **Cross-session continuity** — after the first real-codebase design, the skill remembers the project, draft, extracted components, and budgeted source-context bundle so later unchanged iterations resume without repeating codebase discovery.
  14. - **Two ways in** — this skill from any coding agent, or the web app at [superdesign.dev](https://superdesign.dev).
  15. > **Not the legacy IDE extension.** The archived open-source `superdesigndev/superdesign` VS Code extension is an older, separate project. This skill and [superdesign.dev](https://superdesign.dev) are the current, maintained product.
  16. ---
  17. ## Install
  18. **Any coding agent** — installs the skill for any of the [70+ supported coding agents](https://github.com/vercel-labs/skills#supported-agents):
  19. ```
  20. npx skills add superdesigndev/superdesign-skill
  21. ```
  22. **Claude Code** — install it as a plugin instead, so it stays namespaced and updates with `/plugin update`:
  23. ```
  24. /plugin marketplace add superdesigndev/superdesign-skill
  25. /plugin install superdesign@superdesign
  26. ```
  27. The skill is then invoked as `/superdesign:superdesign`. (Do not also run `npx skills add` in Claude Code — that installs a second, unnamespaced copy of the same skill.)
  28. Either way, install the CLI it drives:
  29. ```
  30. npm install -g @superdesign/cli@latest
  31. superdesign login
  32. ```
  33. ## Use it
  34. Just talk to your agent:
  35. ```
  36. /superdesign help me redesign this settings page so it doesn't look like default AI slop
  37. ```
  38. ```
  39. /superdesign set up a design system from my current codebase
  40. ```
  41. ```
  42. /superdesign improve the design of my dashboard
  43. ```
  44. ```
  45. /superdesign create an 8-slide presentation about our product launch
  46. ```
  47. The skill handles the rest: it reads your code for context, gathers real style references, and produces design drafts you can branch and refine.
  48. ---
  49. # Core scenarios (what this skill handles)
  50. 1. **Design or improve UI** (feature/page/flow)
  51. 2. **Create a presentation** with an editable approved outline
  52. 3. **Create graphics** (posters, covers, social posts, and ads)
  53. 4. **Set or extract a design system**
  54. 5. **Generate supporting images or video**
  55. ## Tooling overview
  56. ### A) Inspiration & Style Tools (generic, always available)
  57. Use these to discover style direction, references, and brand context. Browse the full [prompt library](https://superdesign.dev/library) in the web app, or query it from the CLI:
  58. - **Search prompt library** (style/components/pages)
  59. ```bash
  60. superdesign search-prompts --query "<keyword>"
  61. superdesign search-prompts --tags "style"
  62. superdesign search-prompts --tags "style" --query "<style keyword>"
  63. ```
  64. - **Get prompt details** — read the compact index first, then fetch the full body only for the slug(s) you pick
  65. ```bash
  66. superdesign get-prompts --slugs "<slug1,slug2,...>" # index
  67. superdesign get-prompts --slugs "<slug>" --full # full body of the chosen slug(s)
  68. ```
  69. - **Extract a site's design DNA from a URL** (style guide, tokens, content, brand, clone)
  70. ```bash
  71. superdesign extract-website --url https://example.com --design-md
  72. ```
  73. ### B) Canvas Design Tools
  74. Use design agent to generate high quality design drafts:
  75. - Create project (optionally seed a baseline draft from an HTML template via `--template`)
  76. - Create design draft
  77. - Iterate design draft (replace / branch)
  78. - Plan flow pages → execute flow pages
  79. - Fetch specific design draft
  80. - Create a presentation from an approved ordered slide outline
  81. - Read stored presentation outline and preferences for safe iteration
  82. - List reusable Project Brand Assets
  83. ---
  84. ## Overall SOP for designing features on top of existing app:
  85. 1. Investigate existing UI, workflow
  86. 2. Setup design system file if not exist yet
  87. 3. Requirements gathering: ask the user using the session's available user-input mechanism; if none is available, ask in chat (optionally use Inspiration tools when needed)
  88. 4. Ask user whether ready to design in superdesign OR implement UI directly
  89. 5. If yes to superdesign
  90. 5.1 Create/update a pixel perfect html replica of current UI of page that we will design on top of in `.superdesign/replica_html_template/<name>.html` (html should only contain & reflect how UI look now, the actual design should be handled by superdesign agent)
  91. 5.2 Create project with this replica html + design system guide
  92. 5.3 Start desigining by iterating & branching design draft based on designDraft ID returned from project
  93. ## Always-on rules
  94. - Design system should live at: `.superdesign/design-system.md`
  95. - If `.superdesign/design-system.md` is missing, run **Design System Setup** first.
  96. - Ask high-signal questions about constraints, taste, and tradeoffs using the session's available user-input mechanism; if none is available, ask in chat.
  97. - Read each command's default output directly — it is agent-optimized (compact TOON plus `help[]` next-step hints). Add `--json` only when you genuinely need the full machine-readable payload, and `--full` only to expand truncated fields.
  98. ---
  99. ## replica_html_template rules (Canvas only)
  100. The purpose of replica html template is creating a lightweight version of existing UI so design agent can iterate on top of it (Since superdesign doesn't have access to your codebase directly, this is important context)
  101. Overall process for designing features on top of existing app:
  102. 1. Identify & understand existing UI of page related
  103. 2. Create/update a pixel perfect replica html in `.superdesign/replica_html_template/<name>.html` (Only replicate how UI look now, do NOT design)
  104. - If design task is redesign profile page, then replicate current profile page UI pixel perfectly
  105. - If design task is add new button to side panel, identify which page side panel is using, then replicate that page UI pixel perfectly
  106. **replica_html_template = BEFORE state (what exists now).** It provides context for Superdesign agent.
  107. Actual design will be done via superdesign agent, by passing the prompt
  108. The replica_html_template must contain **ONLY UI that currently exists in the codebase**.
  109. - **DO NOT** design or improve anything in the replica_html_template
  110. - **DO NOT** add placeholder sections like `<!-- NEW FEATURE - DESIGN THIS -->`
  111. - **DO** create pixel-perfect replica of current UI state
  112. - Save to: `.superdesign/replica_html_template/<name>.html`
  113. ### Naming & Reuse
  114. **Naming convention**
  115. Name replica_html_template for reusability: Use the page route (e.g., `home.html`, `settings-profile.html`, `dashboard.html`)
  116. This makes it easy to identify if a page_template already exists.
  117. **Before creating a replica_html_template:**
  118. 1. Check if `.superdesign/replica_html_template/` already contains a matching file
  119. 2. If exists: reuse it or update to reflect the latest existing UI
  120. 3. If not exists: create the neww file
  121. ### Example: Adding a "Book Demo" section to home page
  122. **BAD approach:**
  123. ```html
  124. <!-- replica_html_template includes a sketched Book Demo section -->
  125. <section class="book-demo">
  126. <!-- DESIGN THIS - Add CTA here -->
  127. <h3>Book a Demo</h3>
  128. <button>Schedule</button>
  129. </section>
  130. ```
  131. **GOOD approach:**
  132. ```html
  133. <!-- replica_html_template is pure replica of existing home page (hero + projects) -->
  134. ```
  135. Then in the iterate command:
  136. 1/ create project passing this replica html
  137. 2/ create design draft based on design draft id
  138. ---
  139. # 1) Design System Setup
  140. ### Step 0 — Ask user (one question)
  141. "Do you want to **create a new design system** or **extract from the current codebase**?"
  142. ### A) Extract from codebase
  143. 1. Investigate codebase:
  144. - Product context: what is being built, target users, core value proposition, key user journeys and page structure
  145. - design tokens, typography, colors, spacing, radius, shadows
  146. - motion/animation patterns
  147. - example components usage + implementation patterns
  148. 2. Write standalone design system to:
  149. - `.superdesign/design-system.md`
  150. - Must be implementable without the codebase
  151. ### B) Create a new design system (to improve current UI)
  152. 1. Investigate codebase to understand:
  153. - Product context: what is being built, target users, core value proposition, key user journeys and page structure
  154. - needed pages/components
  155. 2. Gather inspirations (generic tools):
  156. - `superdesign search-prompts --tags "style"`
  157. - `superdesign get-prompts --slugs ...` (index first; add `--full` for the chosen slug's full body)
  158. - optional: `superdesign extract-website --url ... --design-md` (style guide → design.md; add `--brand` for assets)
  159. 3. Ask the user to choose a direction using the session's available user-input mechanism; if none is available, ask in chat
  160. 4. Write:
  161. - `.superdesign/design-system.md` (product context + UX flows + visual design, adapted to references)
  162. ---
  163. # 2) Designing X (feature/page/flow)
  164. ### Example workflow - Add feature to existing page
  165. 1. Investigate the existing design and ask targeted questions about requirements and taste using the session's available user-input mechanism; if none is available, ask in chat
  166. 2. After clarifying, Ask user whether ready to design in superdesign OR implement UI directly
  167. 3. If design in superdesign
  168. 3.1 Ensure `.superdesign/design-system.md` exists (setup if missing)
  169. 3.2 Identify page most relevant, and build a pixel-perfect replica in replica_html_template:
  170. - `.superdesign/replica_html_template/<page>-<feature>.html`
  171. 3.3 Create project, seeding the baseline draft from the replica HTML template (returns `draftId`):
  172. ```bash
  173. superdesign create-project \
  174. --title "<feature>" \
  175. --template .superdesign/replica_html_template/<file>.html
  176. ```
  177. → Note: `draftId` in the response is the baseline draft. The design system is passed as a `--context-file` on the iterate step below, not on `create-project`.
  178. 3.4 Branch designs from baseline (use `draftId` from step 3.3)
  179. ```bash
  180. superdesign iterate-design-draft \
  181. --draft-id <draftId> \
  182. -p "Dark theme with neon accents" \
  183. -p "Minimal with more whitespace" \
  184. -p "Bold gradients and shadows" \
  185. --mode branch \
  186. --context-file .superdesign/design-system.md
  187. ```
  188. 3.5 Share design title & preview URL → collect feedback → iterate
  189. ### Advanced usage
  190. #### Design multiple page OR a full user journey
  191. Execute:
  192. ```bash
  193. superdesign execute-flow-pages \
  194. --draft-id <draftId> \
  195. --pages '[{"title":"Signup","prompt":"..."},{"title":"Payment","prompt":"..."}]'
  196. ```
  197. #### Get HTML reference from a draft
  198. ```bash
  199. superdesign get-design --draft-id <draftId> --output ./design.html
  200. ```
  201. ---
  202. ## Quick reference (key commands)
  203. ```bash
  204. # Inspirations
  205. superdesign search-prompts --query "<keyword>"
  206. superdesign search-prompts --tags "style"
  207. superdesign get-prompts --slugs "<slug1,slug2>" # index; add --full for full bodies
  208. superdesign extract-website --url https://example.com --design-md # style guide; add --brand/--tokens/--content-structure/--clone for more
  209. # Canvas - Create project
  210. # Optional --template <path> seeds the first (baseline) draft from an HTML file.
  211. # The design system is passed as --context-file on the draft/iterate commands, not here.
  212. superdesign create-project --title "X"
  213. superdesign create-project --title "X" --template ./index.html
  214. # Presentation - approve the outline in chat before this call
  215. superdesign create-presentation --project-id <id> --title "X" \
  216. --outline-file ./slides.json --visual-direction "..." \
  217. --navigation-controls show --transition auto --brand-assets use
  218. # Iterate: replace mode (single variation, updates in place)
  219. superdesign iterate-design-draft --draft-id <id> -p "..." --mode replace
  220. # Iterate: Explore multiple versions & variations (each prompt = one variation, prompt should be just directional, do not specify color, style, let superdesign design expert fill in details, you just give direction)
  221. superdesign iterate-design-draft --draft-id <id> -p "dark theme" -p "minimal" -p "bold" --mode branch
  222. # Iterate: Auto explore (only give exploration direction, and let Superdesign fill in details, e.g. explore different styles; Default do not use this)
  223. superdesign iterate-design-draft --draft-id <id> -p "..." --mode branch --count 3
  224. # Fetch & get designs
  225. superdesign fetch-design-nodes --project-id <id>
  226. superdesign get-design --draft-id <id> --json # full HTML payload; or --output <path> to write to a file
  227. # Create new design from scratch without any reference - ONLY use this for creating brand new design, default NEVER use this
  228. superdesign create-design-draft --project-id <id> --title "X" -p "..."
  229. ```
  230. ---
  231. ## Links
  232. - Web app: [superdesign.dev](https://superdesign.dev)
  233. - Prompt library: [superdesign.dev/library](https://superdesign.dev/library)
  234. - Design system convention: [DESIGN.md](./DESIGN.md)
  235. - Skill install for 70+ agents: [vercel-labs/skills](https://github.com/vercel-labs/skills)
  236. ## License
  237. MIT. See [LICENSE](./LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

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