// 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.
Create the next desktop changelog entry when asked to add a changelog file or prepare the next release note under `packages/changelog/content`. Use this when the task is specifically about determining the next version and creating the markdown entry.
Migrate a TinyBase table to SQLite. Use when asked to move a data domain (e.g. templates, vocabs) from the TinyBase store to the app SQLite database.
Design or review schemas for `crates/cloudsync` using SQLite Sync constraints, not generic SQLite advice. Use when adding synced tables, changing synced columns, or planning CloudSync-safe migrations.
Build SQLite-backed reactive UI in `apps/desktop` using stable patterns for reads, selection, forms, writes, and loading states. Use when implementing or reviewing screens built on `useDrizzleLiveQuery` and SQLite mutations.
Choose between in-process `tower::ServiceExt::oneshot` tests and real `tokio::net::TcpListener` server tests for Axum services in this repository.
Live transcription, recording, and audio tools CLI. Use when the user needs to transcribe audio, record, play audio files, or manage speech-to-text models.
| name | add-plugin |
| description | 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. |
Create a new plugin with:
npx @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:
rollup.config.jsREADME.mdtsconfig.jsonpackage.jsonIf 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:
pnpm -F @hypr/plugin-<NAME> codegen
Finish by updating these integration points:
Cargo.tomlapps/desktop/src-tauri/Cargo.tomlapps/desktop/package.jsonapps/desktop/src-tauri/capabilities/default.jsonRun pnpm i after updating apps/desktop/package.json.