Build Termy Plugins

Build small, native-feeling Termy extensions against the real v1 contract. Keep the plugin scoped, use the fewest capabilities, and verify behavior inside Termy when the user authorizes installation or development mode.

Start from evidence

1. Inspect repository instructions, the dirty state, and existing plugin files. Preserve unrelated work.
2. Read the plugin's managed termy.d.ts when available. Treat it and the current Termy checkout as authoritative when they differ from this skill.
3. Read references/api-reference.md before adding a new API surface or diagnosing a type/manifest error.
4. Read references/performance-security.md before handling user-controlled shell text, files, credentials, network, subprocesses, lifecycle events, storage, or native UI.
5. Read references/examples.md before scaffolding. Reuse assets/command-plugin/ or assets/native-ui-plugin/ when it fits.