# Open Design

Generate design artifacts (landing pages, decks, prototypes, dashboards, components)...

- Repository: https://github.com/feimacode/open-design-agent-kit (756 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add feimacode/open-design-agent-kit --skill open-design -g -a claude-code -y`
Codex: `npx skills add feimacode/open-design-agent-kit --skill open-design -g -a codex -y`
Cursor: `npx skills add feimacode/open-design-agent-kit --skill open-design -g -a cursor -y`
Gemini CLI: `npx skills add feimacode/open-design-agent-kit --skill open-design -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add feimacode/open-design-agent-kit`

## Description

Generate design artifacts (landing pages, decks, prototypes, dashboards, components) using Open Design's bundled design skills and design systems. Use whenever the user asks to design, build, mock up, or generate something visual, a landing page, pitch deck, dashboard, prototype, or marketing page, even if they don't say "Open Design" explicitly.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<!-- generated:open-design-agent-kit -->

Open Design is a bundled catalog of design skills and design templates (reusable task recipes and rendering styles, both usable interchangeably as a `skillId`) plus design systems (brand-inspired visual token sets), exposed through the `open-design` MCP server's tools.

Every skill/template id is namespaced as `od:<mode>:<name>` (e.g. `od:deck:guizang-ppt`), where `mode` is one of: `prototype`, `deck`, `design-system`, `image`, `video`, `template`, `utility`, `audio`. Always pass the full namespaced id as `skillId`. Note: mode `design-system` means "a skill that helps author a design-system deliverable", it has nothing to do with `designSystemId`, which selects from the separate library of ~150 prebuilt brand design systems (see step 2).

A small, curated subset of skills/templates also has its own explicit `/open-design:<id>` skill, if the user's request closely matches one of those, prefer invoking it directly; it pins the exact skillId and often a ready-made example brief, removing any guesswork. Otherwise, follow the flow below yourself.

All Open Design content (skill/template text, design system tokens, example briefs) is delivered to you as plain text through the MCP tool calls below, never as a file path. You never need to, and should not, browse or search for Open Design's own files anywhere on disk; `list_open_design_skills` and `prepare_open_design_brief` already return everything you need as plain text.

The rest: https://github.com/feimacode/open-design-agent-kit/blob/HEAD/packages/cli/assets/codex-skills/open-design/SKILL.md