Files
open-design/plugins
qiongyu1999 ac2301894d feat(plugins): unify all 30 community deck seeds with the Open Design product narrative
Replace per-deck placeholder content with one canonical 10-section story
sourced from the homepage structure doc and README: cover, why (Claude
Design proved it, OD opens it), three claims, numbers board (60K+ stars /
300+ contributors / 217+ plugins / 129 design systems / 21 agents), 5-step
workflow, multimodal outputs, capabilities, agent ecosystem, testimonial,
and CTA with GitHub/Discord/X links for organic resharing.

Content-only edits: CSS tokens, layouts, decorations, animations, keyboard
nav and hash routing untouched in every deck. huashu-* decks carry the zh
copy; fs-/hps-/ve- decks carry the en copy (latin display faces). All 29
rewrites + 1 pilot verified: script syntax, cover screenshot, no fictional
brand residue.
2026-06-11 12:49:29 +08:00
..

Open Design Plugins

Language: English | 简体中文

This directory has two different jobs:

  • _official/ - first-party plugins bundled with Open Design. The daemon scans this tree at startup and registers these plugins as official.
  • community/ - community plugin source folders. These are installable plugins, but they are not preinstalled unless a registry entry points at them and the user installs one.
  • registry/ - default registry source manifests (open-design-marketplace.json) for official and community catalogs. These feed the Plugins Available/Sources UI.
  • spec/ - the portable plugin specification, templates, examples, and agent handoff kit for building, testing, publishing, or opening a PR back to Open Design.

The common contract is the same everywhere: a plugin is a portable agent skill folder with a SKILL.md, plus an optional versioned open-design.json sidecar that gives Open Design marketplace metadata, inputs, previews, pipelines, and trust/capability hints.

Start here: