mirror of
https://github.com/nexu-io/open-design.git
synced 2026-10-27 09:51:12 +01:00
* chore: remove extracted landing-page from the monorepo The marketing site now lives in a separate repository. Drop the Astro app, its GitHub workflows/scripts, and the remaining monorepo coupling so this workspace no longer builds or deploys it. * fix: drop leftover landing-page coupling from Teams and skills Point development enterprise URLs at the deployed marketing origin, remove nextjs-app skill outputs that no longer emit a page, and stop advertising apps/landing-page in plugin marketplace metadata. Generated-By: looper 0.12.0 (runner=fixer, agent=omp) * fix(ci): restore DSH installer E2E Vitest routing Removing dsh-bootstrap-identity dropped the only planner route from tools/release/resources/dsh-bootstrap/ to web_tests_required, so installer-only PRs skipped e2e/tests/dsh-installer-version-policy.test.ts. Generated-By: looper 0.12.0 (runner=fixer, agent=omp) * docs: drop leftover landing-page paths from template assets The skill contract no longer advertises the extracted Astro app, but styles.css, compose.ts, and example.html still named deleted apps/landing-page sources. Describe the standalone template behavior instead and keep the bundled plugin example in sync. Generated-By: looper 0.12.0 (runner=fixer, agent=omp) * docs: keep landing-page off review and test surfaces Add apps/landing-page to the forbidden-surface review list and stop naming the extracted path in plugin registry acceptance tables. Generated-By: looper 0.12.0 (runner=fixer, agent=omp) * fix: drop leftover landing-page refs and bump plugin version Stop naming the deleted apps/landing-page in the landing-deck demo and plugin-registry plan. Bump example-open-design-landing to 0.1.1 and keep the official catalog version aligned with the bundled manifest. Generated-By: looper 0.12.0 (runner=fixer, agent=omp)
OpenDesign Plugins
Language: English | 简体中文
This directory has two different jobs:
_official/- first-party plugins bundled with OpenDesign. 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 OpenDesign.
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 OpenDesign 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