npx claudepluginhub manalkaff/opendesign --plugin opendesignThis skill uses the workspace's default tool permissions.
Loaded when the user asks you to produce a reusable design system or UI kit from an existing brand, codebase, or product.
Guides building design systems with tokens (typography, colors, spacing, shadows), components, documentation, governance, and best practices. Use for UI consistency across teams.
Creates structured DESIGN.md files for visual design systems (colors, typography, spacing, components) that AI agents read to generate consistent UI. Handles from-scratch visions, website extractions, or codebase analysis.
Provides 68 pre-built DESIGN.md files to scaffold full UI design systems in Claude Design, generating CSS tokens, type scales, component previews, HTML kits, and SKILL.md files.
Share bugs, ideas, or general feedback.
Loaded when the user asks you to produce a reusable design system or UI kit from an existing brand, codebase, or product.
All design systems for a project live under ./opendesign/design-systems/<name>/. Multiple systems can coexist — for example, ./opendesign/design-systems/marketing/, ./opendesign/design-systems/product/, ./opendesign/design-systems/deck-template/. The name is required and descriptive of what the system is for (brand surface, product surface, deck template, co-brand partner). Never use design-system/ singular or generic names like main.
A folder is recognized as a design system if it contains either a SKILL.md or a tokens file (colors_and_type.css at the root, or tokens/colors_and_type.css nested). opendesign accepts either marker when detecting systems. Always write both: the SKILL.md makes the folder portable as a standalone agent skill, and the tokens file is the canonical output of this skill.
Every generated system MUST write to these exact paths, relative to project root. opendesign auto-discovery depends on them — deviating breaks detection.
./opendesign/design-systems/<name>/SKILL.md — portable skill marker../opendesign/design-systems/<name>/tokens/colors_and_type.css — canonical tokens file. Nested under tokens/, not at the folder root. This is the discovery marker../opendesign/design-systems/<name>/README.md — human-facing index.Do not write the tokens file to any other path (no colors.css, no styles/tokens.css, no flat colors_and_type.css at the root of the system folder). Do not omit SKILL.md. Do not rename the design-systems/ parent inside opendesign/.
opendesign/design-systems/<name>/
README.md
tokens/
colors_and_type.css
fonts/
[font files the brand actually ships]
assets/
logos/
icons/
imagery/
brand/
voice-and-tone.md
style-notes.md
ui-kit-<product>/
components/ # JSX components, one per file
index.html # interactive showcase of core screens
sample-slides/ # only if a deck template was provided
./opendesign/design-systems/<name>/tokens/colors_and_type.css — not the folder root, not a renamed file. Also write ./opendesign/design-systems/<name>/SKILL.md so the folder is recognized and portable. Define raw variables (--fg-1, --fg-2, --bg-1, --accent-1, font families, weights, size steps) and semantic variables (--h1, --h2, --body, --caption, --surface-primary, --border-subtle, etc.). Semantic vars reference raw vars.assets/. Never hand-draw.index.html that assembles the core screens so the kit can be reviewed interactively.assets/ and reference it by filename.Close with a clear ask to iterate: list the parts you were confident about, the parts you were unsure about, and the decisions you want the user to confirm before the system is considered canonical.