What problem does it solve?
Rapidly creating and validating Paperclip plugin packages is error prone and involves boilerplate, runtime conventions, and verification steps that are easy to miss. This Skill provides a deterministic scaffold and a checklist of runtime assumptions and verification steps so engineers can produce compliant plugins consistently.
Core Features & Use Cases
- Scaffold Generation: Use the create-paperclip-plugin scaffold to generate package layout, manifest, worker, UI, tests, and package.json with recommended defaults.
- SDK Snapshotting: Support for snapshotting a local SDK into a .paperclip-sdk folder for plugins developed outside the monorepo.
- Conventions & Verification: Guidance on manifest fields, allowed capabilities, route and slot usage, prohibited runtime APIs (for example, no ctx.assets), and a verification flow requiring typecheck, test, and build.
- Use Cases: Adding an example plugin to packages/plugins/examples, onboarding a third-party plugin repository, or updating plugin authoring documentation and examples.
Quick Start
Scaffold a new Paperclip plugin named @acme/plugin-name into /absolute/path/to/plugin-repos using the create-paperclip-plugin scaffold and prepare manifest, worker, UI, and tests for verification.