cradle-plugin-developmentlisted

# Cradle Plugin Development Build against the Plugin SDK guide bundled with the running Cradle version. The guide owns architecture, manifest, API, lifecycle, and security semantics; this Skill owns only the Agent workflow. Do not copy API contracts from the guide into generated project documentation. ## Read The Canonical Guide Start with the topic index: ```bash cradle plugin docs ``` Read only the topics needed for the task: ```bash cradle plugin docs getting-started cradle plugin docs package-structure cradle plugin docs server-plugin-api cradle plugin docs web-plugin-api cradle plugin docs desktop-plugin-api cradle plugin docs react-sharing cradle plugin docs validation ``` Use `cradle plugin docs all` only when the task genuinely spans the complete Plugin system. Use `cradle man plugin` for the current management command contract. For exact signatures, generics, or optional fields, inspect the declarations installed with the SDK at `node_modules/@cradleapp/plugin-sdk/dist/*.d.ts`. In the Cradle monorepo, inspect `packages/plugin-sdk/src/*.ts`. Never invent a Plugin API or duplicate those contracts into package documentation. ## Choose The Correct Surface - Use an Artifact for a session-bound interactive result that needs no host integration or persistent Plugin lifecycle. - Use a Cradle Plugin for a reusable capability with a server, web, or desktop layer, Plugin-owned storage, commands, panels, routes, MCP servers, or other declared contributions. - A C