paperclip-create-plugin

Topics in the source

• Create and develop a Paperclip plugin
• 1. Default: build the plugin OUTSIDE Paperclip core
• 2. Ground rules
• 3. CLI-first scaffold workflow
• 4. Local install + rebuild loop
• 5. After scaffolding, sanity-check the package
• 6. Verification (run before declaring success)
• 7. Success checklist (report this back)

Use this skill when the task is to create, scaffold, or iterate on a Paperclip plugin against a local Paperclip instance. Plugins are their own packages. Unless the task explicitly asks for a bundled in-repo example, do not add plugin source under packages/plugins/ in this repo. Scaffold the plugin into a directory outside the Paperclip checkout (e.g. /dev/paperclip-plugins/ ). Install it into the running Paperclip instance by local absolute path. Edit code in the external package; let Paperclip pick up rebuilt output. Only edit Paperclip core itself when the user asks to surface a plugin as a bundled example (server/src/routes/plugins.ts, in-repo example lists, docs). Reference docs when you need detail: 1. doc/plugins/PLUGINAUTHORINGGUIDE.md 2. packages/plugins/sdk/README.md 3. doc/plugins/PLUGINSPEC.md — future-looking context only Current runtime assumptions: plugin workers are trusted code plugin UI is trusted same-origin host code worker APIs are capability-gated plugin UI is not sandboxed by manifest capabilities no host-provided shared plugin UI component kit yet ctx.assets is not supported in the current runtime Use paperclipai plugin init. Do not invoke the scaffold packa

This is an excerpt. Refer to the complete source and its current requirements.