open-design/plugins
pftom 9ea33e076b feat(context-plugins): add support for context plugins in project metadata and UI
- Introduced a new `contextPlugins` field in the `ProjectMetadata` type to accommodate plugins selected via `@` mentions, allowing for additive context in project creation.
- Updated the `HomeHero` and `EntryShell` components to handle and display context plugins, enhancing user interaction with selected plugins.
- Implemented rendering logic for context plugins in the metadata block, providing clear visibility of selected plugins and their descriptions.
- Enhanced the UI to support the removal of context plugins and display additional details on hover, improving the overall user experience.

This update significantly enriches the project creation process by allowing users to incorporate multiple context plugins seamlessly.
2026-05-14 15:29:49 +08:00
..
_official feat(context-plugins): add support for context plugins in project metadata and UI 2026-05-14 15:29:49 +08:00
community feat(context-plugins): add support for context plugins in project metadata and UI 2026-05-14 15:29:49 +08:00
registry feat(context-plugins): add support for context plugins in project metadata and UI 2026-05-14 15:29:49 +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

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: