pftom
9e196d34af
- Updated the plugin sharing prompts to utilize local daemon endpoints for publishing to GitHub and contributing to Open Design, streamlining the user experience. - Refactored the `PluginsView` and `PluginShareMenu` components to support new sharing functionalities, including confirmation modals and improved link handling. - Enhanced the CSS styles for the plugin share confirmation modal and related UI elements for better visual consistency. - Added tests to verify the functionality of the new sharing workflows and ensure proper integration within the existing plugin management system. This update significantly improves the plugin sharing experience, making it easier for users to publish and contribute their plugins effectively.
Open Design Community Plugin Kit
This folder is the shareable developer kit for Open Design plugin authors. It is meant to work for a human reading the repo and for an external coding agent such as Claude Code, Codex, Cursor, OpenClaw, Hermes Agent, or another Agent Skills compatible tool.
Open Design plugins follow the same portable shape as Agent Skills: a folder with SKILL.md plus optional assets, references, scripts, and examples. Open Design adds open-design.json as a sidecar so the same folder can appear in the OD plugin gallery, hydrate the home composer, declare inputs and GenUI surfaces, run an OD atom pipeline, and participate in publish or PR flows.
Folder Map
SPEC.md- the community-facing spec and taxonomy.AGENT-DEVELOPMENT.md- copy this into an external agent session to build and validate a plugin.CONTRIBUTING.md- PR standards for community plugins.templates/- blank starter files.examples/- complete example plugin folders and a sample marketplace index.
What To Build
Workflow lanes:
- Import - Figma, GitHub, code folders, URLs, screenshots, PDFs, PPTX, Framer, Webflow.
- Create - prototypes, slide decks, live artifacts, image assets, video prompts, HyperFrames compositions, audio assets.
- Export - PPTX, PDF, HTML, ZIP, Markdown, Figma handoff, Next.js, React, Vue, Svelte, Astro, Angular, Tailwind.
- Share - public links, GitHub PRs, Gists, Slack, Discord, Notion, Linear, Jira.
- Deploy - Vercel, Cloudflare Pages, Netlify, GitHub Pages, Fly.io, Render.
- Refine - critique, patch, tune, brand swap, A/B variants, stakeholder review.
- Extend - plugin authoring, marketplace publishing, internal catalog automation.
Five Minute Start
- Copy
templates/to a new plugin folder. - Rename the folder and frontmatter
nameto a lowercase id such aslaunch-deck. - Write a pushy
descriptioninSKILL.md: "Use this plugin when..." - Fill
open-design.json: title, version, tags,od.taskKind,od.mode,od.useCase.query,od.pipeline, inputs, and capabilities. - Add a small
examples/orpreview/artifact if the plugin is visual. - Validate locally:
pnpm guard
pnpm --filter @open-design/plugin-runtime typecheck
When the daemon CLI is built:
od plugin validate ./path/to/plugin
od plugin install ./path/to/plugin
od plugin apply <plugin-id> --input key=value
Compatibility Promise
A folder with SKILL.md can be used as a plain skill in Agent Skills compatible clients. Adding open-design.json should never make the skill less portable; it only adds Open Design product behavior.
References:
- Agent Skills overview: https://agentskills.io/home
- Agent Skills specification: https://agentskills.io/specification
- Open Design plugin spec: ../../docs/plugins-spec.md