vndangkhoa/open-design
1
0
Fork 0
mirror of https://github.com/nexu-io/open-design.git synced 2026-06-01 03:14:35 +07:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
open-design/plugins
History
chaoxiaoche 912c7e380a
fix(plugin): infer semantic roles for token maps (#3231) 
Co-authored-by: chaoxiaoche <chaoxiaoche@chaoxiaochedeMacBook-Pro.local>
2026-05-29 03:50:56 +00:00
..
_official fix(plugin): infer semantic roles for token maps (#3231) 2026-05-29 03:50:56 +00:00
community Garnet hemisphere (#1702) 2026-05-14 21:12:50 +08:00
registry Merge origin/main into release/v0.8.0 2026-05-23 12:17:18 +08:00
spec feat(plugins): add specVersion and version fields to plugin and marketplace schemas 2026-05-13 22:24:50 +08:00
AGENTS.md feat(plugins): introduce portable plugin specification and authoring kit 2026-05-13 21:24:36 +08:00
README.md feat(plugins): add registry protocol and enhance plugin management features 2026-05-14 08:55:36 +08:00
README.zh-CN.md feat(plugins): add registry protocol and enhance plugin management features 2026-05-14 08:55:36 +08:00

README.md

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: