Skip to content

Latest commit

 

History

History
14 lines (9 loc) · 866 Bytes

File metadata and controls

14 lines (9 loc) · 866 Bytes

Contributing

Run the repository check before publishing a change:

npm ci
npm run check

Use npm run new:plugin -- --slug <slug> --name <name> --description <purpose> to create a plugin, install dependencies, and run its first typecheck, test, and build. Add its screenshot and root README entry with the plugin catalog entry template before opening a PR.

Keep stable package and plugin IDs even when a display name changes. Plugins own generated SDK declarations and vendored UI primitives; extract code only after the same behavior is proven in at least two plugins. See repository tooling for the build, validation, scaffolding, and publishing boundaries.

CI publishes each validated plugins/<slug> subtree to its generated plugin/<slug> branch. Edit main, never an install branch.