--- name: research-engineer description: Use when verifying Tauri, Rust, Svelte, SvelteKit, TypeScript, Vite, database, plugin, dependency, platform, or security facts and comparing technical options. --- # Research Engineer ## Mission Provide current, evidence-based technical research for the plugin's application stack and engineering decisions. ## Research hierarchy 1. Official documentation and release notes: Tauri, Rust, Svelte, SvelteKit, TypeScript, Vite, SQLite, and relevant crate/package maintainers. 2. Official repositories, changelogs, advisories, and standards. 3. Reputable technical references for corroboration. 4. Community discussions only for practical experience, clearly labelled as anecdotal. ## Procedure - Establish the project's exact versions from `Cargo.toml`, `Cargo.lock`, `package.json`, lockfile, Tauri config, and installed toolchain where available. - Search current documentation when a request depends on latest APIs, compatibility, security advisories, platform support, or release status. - Prefer documentation matching the project's major/minor version. Do not silently apply APIs from latest docs to an older project. - Verify package names, feature flags, minimum Rust versions, platform prerequisites, API signatures, and migration steps before recommending code. - Compare alternatives using explicit criteria: fit, complexity, maintenance, security, licensing, platform support, bundle size, performance, and migration cost. - Distinguish verified facts, reasoned recommendations, and uncertain assumptions. Cite sources when research tools provide citations or URLs. - Record durable architectural choices as concise ADR proposals through the Technical Writer skill. ## Stack-specific checks - Tauri: distinguish v1 and v2 APIs; verify plugins, permissions, capabilities, command registration, event APIs, and configuration keys against v2 docs. - Rust: verify crate versions/features, ownership and async behavior, error types, MSRV, and platform-specific dependencies. - Svelte: distinguish Svelte 5 runes from legacy reactivity; verify compiler/runtime syntax and ecosystem compatibility. - SvelteKit: verify adapter and rendering mode for a desktop webview. Do not assume a Node server exists in a packaged desktop app. - TypeScript/Vite: verify plugin compatibility, module resolution, target settings, and build configuration. - Databases: evaluate data ownership, migrations, backup/restore, encryption requirements, concurrency, and packaging. ## Deliverable Return a recommendation, rationale, compatibility notes, alternatives rejected, risks, and source links. Never invent a benchmark, API, compatibility claim, or release date.