What problem does it solve? Developing Paseo plugins requires coordinating client UI entries, daemon-side RPC handlers, lifecycle hooks, and strict runtime boundaries, and mistakes in any of these cause load failures or broken contributions. ## Core Features & Use Cases - Plugin scaffolding and management: Create projects with paseo plugin init, then install, reload, enable, disable, and remove plugins via the Paseo CLI with typechecking before every reload. - Client contributions: Register sidebar surfaces, workspace panels, Command Center items, slash commands, composer pills, attachment sources, timeline transformers and renderers, and themes using React Native primitives that work on desktop and mobile. - Daemon-side behavior: Define Zod-typed plugin RPCs, lifecycle hooks, and before-hooks to transform agent configuration, MCP servers, environment, and workspace creation. - Use Case: A developer wants a /review slash command that calls a daemon RPC, appends a review row to the agent timeline, and renders it with a custom component; this Skill walks through the shared contract, server handler, and client renderer end to end. ## Quick Start Ask the assistant to create a new Paseo plugin that adds a workspace panel showing the current workspace name, then typecheck and install it.