Cline rules for Tauri

# Cline and Roo rules

Project rules for Cline and Roo Code in this Tauri repository.
Use the project's commands. Do not invent a package manager, and do not run destructive shell commands.

## Tool use

- Read the files you will change before editing them.
- Prefer a focused patch over rewriting a whole file.
- Run the test command from this file after a behavior change, or say why you could not.
- Do not delete generated folders, lockfiles, or migrations unless the task says so.

## Stack

This repository is a Tauri app. Privileged work is a Rust command. The webview calls `invoke`. Capabilities grant only the permissions the window needs.

## Layout

- Rust commands live in `src-tauri/src`.
- Capabilities and permissions live in `src-tauri/capabilities` or the project's gen folder.
- The frontend stays a normal web app and reaches Rust only through `invoke`.

## Commands

- Dev: `npm run tauri dev`
- Rust tests: `cargo test`
- Frontend tests: `npm test`

Use the script the repo already defines when it differs from the command above.

## Conventions

- Add a `#[tauri::command]` only for work the webview cannot do safely.
- Return `Result`. Do not unwrap on arguments the UI sent.
- Update the capability allow-list when you add a command or a plugin.
- Keep the allowlist narrow. Do not grant fs or shell glob permissions to get unstuck.
- Share types deliberately. Do not serialize the whole app state to the webview.
- Run `cargo fmt` on Rust changes.

## Testing

Add or update tests when behavior changes.

Unit-test the command's pure logic in Rust. Do not need the webview for a validation rule.

## Style

- Optimize for the next reader over the shortest diff.
- Comment only when the why is non-obvious.
- Name things the way neighboring files already do.
- Do not reformat code you did not change.

## Errors

- Fail at the boundary. Do not swallow errors.
- Return a structured error string or the project's error enum from the command. The UI should be able to show it.

## Scope

- Do the requested task. Do not refactor unrelated code.
- Match the rigor already in the repo. Fix what you touch.
- Ask one clarifying question only when the task cannot be finished without it. Otherwise state the assumption and continue.

## Avoid

- Do not call Rust by shelling out from the frontend.
- Do not disable the capability system.
- Do not hold a webview handle and block the UI thread.
- Do not clone secrets into a command's debug log.

## Done when

- The requested behavior works.
- `cargo test` passes and `tauri dev` still opens the window.
- The diff stays inside the task.
- You list anything you could not run.