mirror of
https://github.com/nexu-io/open-design.git
synced 2026-10-27 09:51:12 +01:00
2569f4eba9
* feat(scenarios): add od-share-to-community plugin + Share to Open Design button After the user finishes a generation, they currently have to re-prompt the agent to package what they just made. This adds a quiet "Share to Open Design" pill in the assistant-completion-row — same area as the post-feedback Discord prompt — that injects a single trigger prompt into the chat and lets the bundled `od-share-to-community` scenario auto-derive the manifest from `*.artifact.json`, `brand-spec.md`, and the workspace files instead of asking the user fields the project files already answer. The skill mirrors `home-hero/plugin-authoring.ts`'s constraint surface verbatim: no chained CLI suggestions, no `jq` dependency (not in the agent runtime baseline), and after `od plugin install --source`, point the user at the existing 3-button plugin-folder card (Add to My plugins / Publish repo / Open Design PR) instead of recreating those flows freeform — the source of bug #2332. Verified end-to-end via headless browser: - daemon registers the bundled scenario at /api/plugins - button renders in the live DOM, gated on (isLast && showFeedback) - click fires POST /api/runs with the trigger prompt as a user message - Claude Opus picks up the prompt and starts the share flow * fix(web): debounce share to open design action * fix(plugins): register share community scenario pipeline --------- Co-authored-by: kokisanai <kokisanai@users.noreply.github.com> Co-authored-by: Siri-Ray <2667192167@qq.com>
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:
- Plugin spec kit:
spec/README.md - Plugin authoring spec:
spec/SPEC.md - Agent handoff guide:
spec/AGENT-DEVELOPMENT.md - Registry publishing strategy:
spec/PUBLISHING-REGISTRIES.md - Full product spec:
../docs/plugins-spec.md - Manifest schema:
../docs/schemas/open-design.plugin.v1.json - Marketplace schema:
../docs/schemas/open-design.marketplace.v1.json