open-design / plugins

# Plugin Directory Guide

This directory owns OpenDesign plugin content and plugin authoring material.

## Boundaries

- `plugins/_official/` contains bundled first-party plugins. The daemon boot walker scans only this subtree and registers it as `source_kind='bundled'`.
- `plugins/spec/` is the portable plugin specification and authoring kit. It is documentation, starter material, and example source for contributors and external agents; it must not be treated as an installed first-party catalog.
- Keep runnable plugin examples portable: every example should have a `SKILL.md`; add `open-design.json` only as the OD sidecar.
- Keep `SKILL.md` bodies free of OD-only marketplace metadata. Put OD display, inputs, preview, pipeline, capabilities, and source information in `open-design.json`.
- Do not import app-private code from plugin content. A plugin may reference OD atoms, design systems, craft docs, assets, scripts, MCP servers, or connectors through the manifest.

## Authoring Rules

- New spec examples belong under `plugins/spec/examples/<plugin-id>/`.
- New first-party bundled plugins belong under `plugins/_official/<tier>/<plugin-id>/` only when the product should auto-register them on daemon startup.
- Use the v1 JSON schema at `docs/schemas/open-design.plugin.v1.json`.
- Contribution-facing spec docs are bilingual. When editing `README.md`, `SPEC.md`, `CONTRIBUTING.md`, `AGENT-DEVELOPMENT.md`, or example README files under `plugins/spec/`, update the matching `*.zh-CN.md` mirror in the same change.
- Prefer TypeScript for project-owned scripts. Avoid adding new `.js`, `.mjs`, or `.cjs` files unless they are generated, vendored, or explicitly allowlisted by `scripts/guard.ts`.
- Keep example plugins concise and agent-readable. Move long reference material to `references/` and tell the agent when to load it.

### HTML-backed preview contract

- When a bundled example's `template.json` declares `format: "html"` or carries
  `referenceHtml`, commit the real rendered sample as `example.html`. Do not use
  a screenshot or placeholder image as the canonical preview for an HTML
  artifact.
- Point `od.preview` at that source with `type: "html"` and
  `entry: "./example.html"`. Use `motion: "scroll"` for documents,
  `motion: "deck"` for slide navigation, and `motion: "static"` only for a
  fixed, non-scrolling surface.
- Keep `od.useCase.exampleOutputs` and `od.context.assets` aligned with
  `./example.html`. A poster such as `example.webp` may remain as a secondary or
  derived asset, but it must not replace the HTML preview source.
- When `referenceHtml` is present, materialize `example.html` from it (or from
  the same deterministic generator) and keep their rendered source in sync.
- Before submitting, verify `/api/plugins/<id>/preview` returns `200` with an
  HTML content type. In preview-baker output, the plugin must render as
  `+ <id>`, not `skip (status 404)`.

## Validation

For plugin content changes, run:

```bash
pnpm guard
pnpm --filter @open-design/plugin-runtime typecheck
```

When the daemon CLI is built and available, also validate runnable plugin folders with:

```bash
od plugin validate ./plugins/spec/examples/<plugin-id>
```