Route design-generation work into the right Open Design workflow mode โ prototype, deck, document, or media artifact. Use when the user needs local-first UI prototype generation, presentation deck creation, or design-system-aware HTML/PDF/PPTX artifacts via locally-installed coding agents. Supports 72 built-in design systems, 5 visual directions, 93 media prompt templates, and multi-format export. Triggers on: open-design, local design tool, prototype generation, design deck, design artifact, design agent workflow, open design prototype, design system artifact, UI prototype generation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Route design-generation work into the right Open Design workflow mode โ prototype, deck, document, or media artifact. Use when the user needs local-first UI prototype generation, presentation deck creation, or design-system-aware HTML/PDF/PPTX artifacts via locally-installed coding agents. Supports 72 built-in design systems, 5 visual directions, 93 media prompt templates, and multi-format export. Triggers on: open-design, local design tool, prototype generation, design deck, design artifact, design agent workflow, open design prototype, design system artifact, UI prototype generation.
allowed-tools
Bash Read Write Edit Glob Grep WebFetch
compatibility
Requires Node.js ~24 and pnpm 10.33.x. Run `pnpm tools-dev run web` to launch the local UI. Auto-detects 13+ coding agent CLIs (Claude Code, Cursor, Gemini CLI, GitHub Copilot, etc.). Extend with file-based skills in the `skills/` directory. Plugin install via `claude plugin marketplace add nexu-io/open-design`.
Open-source alternative to Anthropic's Claude Design โ generates web, mobile, and desktop prototypes, decks, and media artifacts using coding agents already installed on your machine.
Open Design is most useful when you choose the smallest generation mode that fits the job:
start with a prototype before reaching for a full deck
pick one design system before layering custom styles
choose one output format (HTML review before PDF/PPTX export)
use the Turn 1 discovery form to reduce redirect cycles before generation begins
When to use this skill
The user needs a local-first UI prototype, presentation deck, or document artifact from a single prompt
The user wants to generate design artifacts using coding agents they already have installed (Claude Code, Cursor, Gemini CLI, etc.)
The user wants to apply one of 72 built-in design systems (Linear, Stripe, Vercel, Notion, Apple, etc.) to their output
The user needs multi-format export: HTML review โ PDF, PPTX, ZIP, or Markdown
The user wants AI-generated images, video, or audio media embedded in design artifacts
The user wants to extend Open Design with custom file-based skills or install it as a Claude Code plugin
Do not use this skill when
The task is live UI component authoring in a real codebase โ route to stitch-skills or design-system
The task is video production or Remotion animation โ route to video-production
The task is a data-driven presentation deck without design-system application โ route to presentation-builder
The task is compressing or optimizing existing media files โ route to compresso
The task is a broad web UI critique or audit โ route to web-accessibility
Instructions
Step 1: Capture the generation mode
Collect the minimum packet before choosing a workflow:
Output type: UI prototype, presentation deck, landing page, document, or media artifact
Design system: one of the 72 built-ins (Linear, Stripe, Vercel, Notion, Tesla, Appleโฆ) or custom
Visual direction: one of 5 directions (minimal, bold, playful, enterprise, dark)
Export format: HTML review, PDF, PPTX, ZIP, or Markdown
Agent: which installed CLI to delegate to (auto-detected or explicit)
Use this rule set:
If output is a UI prototype or landing page โ choose prototype mode
If output is a presentation or investor deck โ choose deck mode
If output is a long-form document or spec โ choose document mode
If media (image/video/audio) generation is the primary output โ choose media mode
If the user has not chosen a design system โ use the Turn 1 discovery form to reduce drift before generating
Step 2: Install Open Design
# Clone and install
git clone https://github.com/nexu-io/open-design.git
cd open-design
corepack enable
pnpm install
# Start the local web UI
pnpm tools-dev run web
pnpm tools-dev start # start daemon
pnpm tools-dev stop # stop daemon
pnpm tools-dev run web # open local web UI
pnpm tools-dev status # check status
pnpm tools-dev logs # tail logs
pnpm tools-dev inspect # inspect agent connections
pnpm tools-dev check # preflight check
Step 3: Choose the right generation mode
A. Prototype mode
Use when the user needs a web, mobile, or desktop UI mockup.
Mode: Prototype
Design system: Linear (or any of 72 built-ins)
Visual direction: minimal / bold / playful / enterprise / dark
Output: HTML review โ PPTX / PDF / ZIP
Best for:
SPA dashboards, landing pages, mobile screens
Multi-page prototype flows
Design-system-aligned mockups before actual implementation
B. Deck mode
Use when the user needs an investor pitch, roadmap, or architecture deck.
Mode: Media | Backend: gpt-image-2 | Template: Product hero
Prompt: "Clean product hero image for a developer CLI tool, dark background, code aesthetic"
Example 4: Plugin install
# Claude Code plugin
claude plugin marketplace add nexu-io/open-design
Best practices
Use the Turn 1 discovery form to freeze design system, visual direction, and output format before generation โ do not skip it for ambiguous requests.
Choose one design system per artifact to keep cross-format output coherent.
Prefer HTML review before committing to PDF/PPTX to save iteration cost.
Use media mode only when generated images/video are the primary deliverable, not a side effect.
For real codebase UI components, route to stitch-skills or design-system instead.
When adding file-based skills to Open Design, follow the same SKILL.md format used in this repo.
Prefer pnpm tools-dev check before first use to verify Node.js and pnpm version requirements.