PluginBench
Skill
Fail
Audit score 45

superdesign

superdesigndev/superdesign-skill

Design agent for frontend UI/UX—create and iterate design drafts before implementation.

What is superdesign?

Superdesign is a design-focused agent that helps you explore design inspirations, generate design drafts, and iterate on UI/UX before coding. Use it at the start of any frontend feature or page design workflow to establish design direction and component patterns.

  • Analyze repository structure and extract design context (components, layouts, routes, themes)
  • Generate faithful design reproductions and variations (dark theme, minimal, etc.) on an infinite canvas
  • Create and iterate design drafts with branching support for multiple design directions
  • Extract reusable components from design drafts with configurable props
  • Manage design projects and component libraries with full version history
  • Support line-range context for precise file references in design analysis

How to install superdesign

npx skills add https://github.com/superdesigndev/superdesign-skill --skill superdesign
Prerequisites
  • Node.js and npm installed
  • Superdesign CLI installed globally: npm install -g @superdesign/cli@latest
  • Active Superdesign account (login via superdesign login)
  • Repository with existing UI components or design context
Claude Code
Cursor
Windsurf
Cline

How to use superdesign

  1. 1.Run superdesign --version to verify CLI is installed; if not, install with npm install -g @superdesign/cli@latest
  2. 2.Run superdesign login if not already authenticated
  3. 3.Run superdesign init to analyze your repo and generate context files in .superdesign/init/
  4. 4.Create a project: superdesign create-project --title "Your Project Name"
  5. 5.Create a design draft: superdesign create-design-draft --project-id <id> --title "Design Name" --context-file <path> with relevant component/page files
  6. 6.Iterate on the draft: superdesign iterate-design-draft --draft-id <id> -p "style option" --context-file <path>
  7. 7.Extract components: superdesign create-component --project-id <id> --name "ComponentName" --html-file <path> --props '[...]'

Use cases

Good for
  • Design a new feature page before implementation—create a draft, iterate with variations, then extract components
  • Improve an existing page's UI—reproduce current design, iterate with new styles, execute flow across multiple pages
  • Establish a design system—analyze repo components and layouts, set design tokens and CSS variables
  • Create component library—extract reusable UI components from design drafts with documented props
Who it's for
  • Frontend developers building new features or pages
  • UI/UX designers collaborating with engineering teams
  • Teams establishing or refining design systems
  • Developers needing design direction before implementation

superdesign FAQ

What files do I need to provide as context?

Check .superdesign/init/pages.md for the complete dependency tree of your page. Pass all files in that tree plus globals.css, tailwind.config, and theme.md as --context-file arguments.

Can I design multiple variations of the same page?

Yes. Use superdesign iterate-design-draft with --mode branch to create design variations without overwriting the original draft.

How do I extract a component from a design draft?

Use superdesign create-component with the --html-file pointing to the component HTML and --props as a JSON array of prop definitions.

Do I need to manually set up the .superdesign/init/ directory?

No. The skill automatically creates and populates .superdesign/init/ when you run superdesign init. You must read all files in this directory before starting design tasks.

What if I'm not logged in?

Run superdesign login and complete authentication before running any design commands. The skill will verify login status automatically.

Full instructions (SKILL.md)

Source of truth, from superdesigndev/superdesign-skill.


name: superdesign description: > Superdesign is a design agent specialized in frontend UI/UX design. Use this skill before implementing any UI that requires design thinking. Common commands: superdesign create-project --title "X" (setup project), superdesign create-design-draft --project-id <id> --title "Current UI" -p "Faithfully reproduce..." --context-file src/Component.tsx (faithful reproduction), superdesign iterate-design-draft --draft-id <id> -p "dark theme" -p "minimal" --mode branch --context-file src/Component.tsx (design variations), superdesign execute-flow-pages --draft-id <id> --pages '[...]' --context-file src/Component.tsx (extend to more pages), superdesign create-component --project-id <id> --name "NavBar" --html-file /tmp/navbar.html --props '[...]' (extract reusable component), superdesign update-component --component-id <id> --html-file /tmp/navbar.html (update existing component), superdesign list-components --project-id <id> (list existing components). Supports line ranges: --context-file path:startLine:endLine metadata: author: superdesign version: "0.0.2"

SuperDesign helps you (1) find design inspirations/styles and (2) generate/iterate design drafts on an infinite canvas.


Core scenarios (what this skill handles)

  1. superdesign init — Analyze the repo and build UI context to .superdesign/init/
  2. Help me design X (feature/page/flow)
  3. Set design system
  4. Help me improve design of X

Init: Repo Analysis

When .superdesign/init/ directory doesn't exist or is empty, you MUST automatically:

  1. Create the .superdesign/init/ directory
  2. Fetch the init prompt from the URL below
  3. Follow the prompt instructions to analyze the repo and write context files
https://raw.githubusercontent.com/superdesigndev/superdesign-skill/main/skills/superdesign/INIT.md

Do NOT ask the user to do this manually — just do it.

Mandatory Init Files

If .superdesign/init/ exists, you MUST read ALL files in this directory FIRST before any design task:

  • components.md — shared UI primitives with full source code
  • layouts.md — shared layout components (nav, sidebar, header, footer)
  • routes.md — page/route mapping
  • theme.md — design tokens, CSS variables, Tailwind config
  • pages.md — page component dependency trees (which files each page needs)
  • extractable-components.md — components that can be extracted as reusable DraftComponents

When designing for an existing page: First check pages.md for the page's complete dependency tree. Every file in that tree MUST be passed as --context-file. Then also add globals.css, tailwind.config, and design-system.md.

Superdesign CLI (MUST run before any command)

IMPORTANT: Before running ANY superdesign command, you MUST ensure the CLI is installed and logged in.

Follow these steps in order — do NOT skip any step:

  1. Check if CLI is already installed:

    superdesign --version
    
    • If the command succeeds (prints a version), skip installation and go to step 2.
    • If the command fails (not found), install the CLI:
      npm install -g @superdesign/cli@latest
      
  2. Check login status by running any command (e.g. superdesign --help). If you see an auth/login error, run:

    superdesign login
    

    Wait for login to complete successfully before proceeding.

  3. Only after login succeeds, run your intended superdesign commands.

Never assume the user is already logged in. Always verify login first.

How it works

MUST MANDATORY Fetch fresh guidelines below:

https://raw.githubusercontent.com/superdesigndev/superdesign-skill/main/skills/superdesign/SUPERDESIGN.md

Action accordingly based on instruction in the SUPERDESIGN.md