mirror of
https://github.com/nexu-io/open-design.git
synced 2026-10-27 09:51:12 +01:00
lefarcenandGitHub
f6cceb303d
Picking a Home example-prompt card (or "Replicate this content" in the plugin detail modal) seeds the composer with the plugin manifest's `description`. Many descriptions were authored with cosmetic hard wraps (a single newline mid-paragraph, ~75 cols, as if formatted for a terminal/markdown source). The composer renders the seed with `white-space: pre-wrap`, so those newlines survived as short ragged lines that never filled the editor width — leaving a large blank gutter on the right of the input box (e.g. the Trading Analysis Dashboard template: 4 hard breaks, ~200px / 29% of the editor blank). Reflow the offending `description` / `description_i18n` strings in the 56 affected bundled manifests into flowing text (wrapped lines joined, real blank-line paragraph breaks preserved; CJK joins carry no space). Surgical string edits only — manifest formatting/key order untouched (146 lines changed across 56 files). The full build spec still reaches the agent as plugin context (SKILL.md + example.html); only the human-facing seed copy changed. Add an e2e guard (plugin-description-hardwrap.test.ts) that fails if any bundled manifest description carries an intra-paragraph hard wrap, so the cleanup can't silently regress when new examples are added.
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