add-plugin

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗

Scaffold a new Tauri plugin in this repository when asked to add or create a plugin under `plugins/`. Use this for plugin generation and repository integration work, not for editing an existing plugin unless the request is specifically about bringing a freshly generated plugin in line with project conventions.

.agents/skills/add-plugin/SKILL.md

Download bundle ↓
main · 143e3d81 bundle fileScanned 2026-09-15

SKILL.md

286 tokens · o200k_base · 1,214 bytes

Source excerpt starting at line 1.
---name: add-plugindescription: Scaffold a new Tauri plugin in this repository when asked to add or create a plugin under `plugins/`. Use this for plugin generation and repository integration work, not for editing an existing plugin unless the request is specifically about bringing a freshly generated plugin in line with project conventions.metadata:  internal: true--- Create a new plugin with: ```bashnpx @tauri-apps/cli plugin new NAME \--no-example \--directory ./plugins/NAME``` Decide `NAME` from the user request, then run the generator. Follow the style and conventions used in `plugins/analytics`: - remove generated `rollup.config.js`- remove generated `README.md`- update `tsconfig.json`- update `package.json` If the user does not ask for different command behavior, keep the single `ping` function in both `ext.rs` and `commands.rs`. After the code changes are in place, generate bindings: ```bashpnpm -F @anlg/plugin-<NAME> codegen``` Finish by updating these integration points: - `Cargo.toml`- `apps/desktop/src-tauri/Cargo.toml`- `apps/desktop/package.json`- `apps/desktop/src-tauri/capabilities/default.json` Run `pnpm i` after updating `apps/desktop/package.json`. 
Discovery context

Discovered by repository scan. No exact path reference found in the snapshot’s root AGENTS.md.