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) — the target decides the SOP: an existing rendered page is reproduced first (ground truth), while a brand-new page (in a real repo or from scratch) is designed directly with no reproduction step; see UI TARGET ROUTING in SUPERDESIGN.md
3. Set design system (optionally seed or refresh it from a live site via extract-website --design-md — you'll choose create-from / inspired-by / update-existing, asking first if a design-system.md already exists; see SUPERDESIGN.md SOP: BRAND NEW PROJECT Step 2)
4. Help me improve design of X
5. Make a poster / marketing asset (flyer, cover art, social feed post, story, channel cover, thumbnail, ad creative) — a static artwork, not a page. Skip repo init/analysis; read GRAPHIC.md and follow it (you generate the key visual with your own image tool, upload it, then compose the artwork on a fixed canvas; platform dimension table included).
6. Design from a live website / reference URL (borrow a style, restyle, recombine, or plan a rebuild) — extract a reference site's design DNA (style guide, design tokens, content structure, brand assets, a static reference clone) with extract-website, then design with it. Read WEBSITE.md and follow its recipes. Note: via the CLI a "recreate"/"clone" is a style-informed rebuild — faithful pixel-recreation and editable on-canvas clones are done in the Superdesign app (superdesign.dev), not the CLI.

Step 0 — Environment preflight (BEFORE any CLI step)

Superdesign runs entirely through its CLI, so you must be able to execute shell commands. Confirm that capability first, before any CLI verification.

If Superdesign is invoked in standard ChatGPT chat without Work Mode tools, do not start the workflow. Tell the user once:

Chat isn't supported by the Superdesign plugin. Please switch to the Work tab and paste this prompt in for the full experience.

If you have no way to run shell commands in this environment (no terminal/execution tool at all), OR your very first bare npx --yes @superdesign/cli@latest preflight attempt fails because command execution itself is unavailable (the harness reports it cannot run commands / there is no shell) then STOP. Do NOT keep retrying or improvise workarounds.

Step 1 — Is there a codebase to analyze?

Two entry paths. Choose one with this cheap, deterministic check BEFORE any init or design work.

No meaningful codebase (empty workspace, scratch/sandbox dir, no frontend code) — treat the workspace as "no codebase" when ALL of these hold:

• No .superdesign/init/ files already exist, AND
• No dependency manifest with frontend deps (no package.json, or a package.json whose deps include no frontend framework/UI library — react, vue, svelte, angular, next, nuxt, astro, etc.), AND
• No frontend source found (a quick scan for .tsx/.jsx/.vue/.svelte files, any .html/.css files such as a root index.html + style.css, or a src//app//components/ dir with UI files, turns up nothing).

→ SKIP repo init entirely. Do NOT "analyze" an empty sandbox, and do NOT ask the user to point you at a repo they don't have. Instead, gather design context conversationally FIRST: ask what they want to build, the target audience/platform, style/brand preferences, and any reference designs or inspirations. Then design from that conversation via the BRAND NEW PROJECT path in SUPERDESIGN.md.

Real codebase present (any frontend code, or an existing .superdesign/init/) — the repo-init path below is MANDATORY; run the full analysis before designing.

Exception — standalone extraction: if the task is ONLY to extract a site's design DNA or set/refresh design-system.md from a URL (extract-website → design-system.md, no design generation), run it WITHOUT repo init — extracting an external site's style doesn't require analyzing the user's codebase. Init is still required before generating designs FOR the existing codebase's UI (reproducing/redesigning an existing page).

Exception — graphics: posters/marketing assets (scenario 5) skip init even in a real codebase — the brief carries the style, and most of init's output (components, layouts, routes, pages) has no bearing on a fixed-canvas artwork. The graphic brief round asks whether the artwork should be on-brand with this repo's product (GRAPHIC.md Step 1); only an on-brand "yes" pulls in the design-system/brand context — running init first only if that context doesn't already exist.

Init: Repo Analysis (real-codebase path)

When a real codebase is present (per Step 1, and neither Step 1 exception — standalone extraction, graphics — applies) and init is NOT complete, you MUST automatically:

1. Create the .superdesign/init/ directory
2. Read INIT.md
3. Follow its instructions to analyze the repo and write context files

Init-complete test (one decidable rule, used everywhere): init is complete only if all six named files below exist AND are non-empty. A directory that is missing any of them, or holds an empty one (e.g. an interrupted init), is NOT complete — rerun the full init, which regenerates all six; overwriting existing files is expected and fine.

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

Mandatory Init Files

If init is complete (all six files present and non-empty), you MUST read ALL of them 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 dependency tree — the candidate set of --context-file files. Pass them under the PAYLOAD BUDGET rules in SUPERDESIGN.md (line-range ~900+ line files to their render/token sections; drop files with no visual bearing) so the payload does not 400. Then also add the globals.css tokens, tailwind.config, and design-system.md.

Superdesign CLI (MUST use before any command)

IMPORTANT: Run the CLI on demand with npx --yes @superdesign/cli@latest. Start every session with the bare command — it IS the preflight.

1. Preflight once:

   npx --yes @superdesign/cli@latest
   

   The bare command verifies everything in one shot: that the CLI runs at all, an auth: status line (authenticated as team "…" vs not authenticated — run superdesign login), and a list of recent projects — read that list when deciding whether to reuse an existing project or create-project.

2. If the auth: line says not authenticated, run login NOW, before any real command:

   npx --yes @superdesign/cli@latest login
   

   Wait for login to complete successfully before proceeding.

3. Run the intended commands with the same npx --yes @superdesign/cli@latest prefix. A session can still expire mid-flow — handle a later auth/login error per the failure block below.

Never assume the user is already logged in — read the preflight's auth: line instead of guessing or probing with real commands.

When a command fails

• Auth/login error (the CLI ran but rejected the session): run login (above), then retry the intended command ONCE. If login itself fails (headless/no-browser auth, expired flow, user declines), tell the user plainly and STOP — do not keep retrying or improvise.
• extract-website fails or times out (it can take ~60–120s): retry ONCE. If it still fails, offer to continue WITHOUT the extraction (design from the conversation / existing design system) rather than blocking.
• General rule: retry a failed command at most once, then report the failure to the user and stop — never silently loop or fall back to inventing output.

Command examples

Always use the full on-demand runner prefix:

npx --yes @superdesign/cli@latest create-project --title "X"
npx --yes @superdesign/cli@latest extract-website --url https://example.com --design-md
npx --yes @superdesign/cli@latest create-design-draft --project-id <id> --title "Current UI" -p "Faithfully reproduce..." --context-file src/Component.tsx
npx --yes @superdesign/cli@latest iterate-design-draft --draft-id <id> -p "dark theme" -p "minimal" --mode branch --context-file src/Component.tsx
npx --yes @superdesign/cli@latest execute-flow-pages --draft-id <id> --pages '[{"title":"Product Details","prompt":"Product detail page with image gallery, specs and add-to-cart"},{"title":"Checkout","prompt":"Checkout page with cart summary and payment form"}]' --context-file src/Component.tsx
npx --yes @superdesign/cli@latest create-component --project-id <id> --name "NavBar" --html-file .superdesign/tmp/navbar.html --props '[{"name":"activeItem","type":"string","defaultValue":"home"}]'
npx --yes @superdesign/cli@latest update-component --component-id <id> --html-file .superdesign/tmp/navbar.html
npx --yes @superdesign/cli@latest list-components --project-id <id>
npx --yes @superdesign/cli@latest upload-asset ./key-visual.png --project-id <id>
npx --yes @superdesign/cli@latest create-design-draft --project-id <id> --title "Launch Poster" --kind graphic --width 900 --height 1200 -p "Design a static poster..."

Each item in the execute-flow-pages --pages array generates one new page styled after the source draft (1-10 pages per call).

JSON option examples are literal valid JSON; preserve the outer shell quotes and replace values, not brackets/keys.

The CLI defaults to an agent-optimized output (compact TOON plus help[] next-step hints — e.g. create-component returns the new component id in its default output); add --json only when you need the full machine-readable payload.

Create the workspace-local .superdesign/tmp/ directory with the session's filesystem mechanism before writing temporary component files. Ensure .superdesign/tmp/ is ignored by the project's .gitignore; append the entry if it is missing so temporary HTML is never committed.

--context-file supports path:startLine:endLine; see SUPERDESIGN.md for the complete workflow and current command contract.

Surface the canvas URL

Every project/draft command's default output includes a canvas: link (the project canvas, https://superdesign.dev/teams/<teamId>/projects/<projectId>) and, for drafts, a preview: link (https://superdesign.dev/preview/draft/<draftId>). Read these from the command output — do NOT hand-construct them (the ids are server-generated).

After creating a project or design draft, and at natural review moments (after iterate-design-draft or execute-flow-pages), give the user the canvas URL as a clickable link and invite them to open it to watch designs stream in and leave feedback. Adding ?live=1 to the canvas URL opens the live view where drafts appear as they generate.

Browser Choice

create-project auto-opens the canvas in user's browser by default. Leave it on, and tell the user the canvas was opened (with the canvas URL as a clickable link). Only pass --no-open when there's no user-facing browser (CI, headless).

After generating: offer to go further

Always close with a short, warm follow-up that offers to go further (on every surface). Ask one question with 2 to 3 concrete options tailored to what you just made, not a generic list. For example: try a different hero image or key visual direction, try an alternate layout or composition, or generate a few more variations or asset ideas as surprises. Only generate after the user picks, since every generation spends credits.

(Graphics get a dedicated one-round visual self-review before this close — GRAPHIC.md Step 5. UI drafts are reviewed by the user on the canvas.)

How it works

Read SUPERDESIGN.md, then follow its instructions.