rust

Rust Implementation Patterns

Use this skill for idiomatic Rust with a practical bias toward Tauri-backed desktop application logic. Assume the Rust side often owns heavy operations such as filesystem work, process orchestration, indexing, background tasks, editor services, and stable IPC with the frontend.

Delivery Workflow

Use the checklist below and track progress:

Rust progress:
- [ ] Step 1: Discover crate boundaries, module layout, and Tauri integration points
- [ ] Step 2: Model ownership, data flow, and error shapes explicitly
- [ ] Step 3: Implement logic with small focused types and functions
- [ ] Step 4: Handle async work, IO, and concurrency without blocking UI flows
- [ ] Step 5: Verify tests, formatting, linting, and boundary behavior

Core Rust Rules

• Model ownership intentionally before writing broad mutable flows.
• Prefer simple types and explicit lifetimes over clever abstractions.
• Use the type system to make invalid states difficult to represent.
• Keep functions small, intention-revealing, and focused on one capability.
• Avoid writing TypeScript, C++, or Java in Rust syntax.

Data Modeling and Errors

• Prefer structs and enums that encode real domain meaning.
• Use Result and Option intentionally; do not erase failure modes behind generic strings.
• Model recoverable application errors explicitly and keep infrastructure errors distinguishable.
• Use thiserror or the project-standard error pattern when structured errors improve clarity.
• Keep serialization DTOs separate from internal domain types when the boundary is non-trivial.

Async, IO, and Concurrency

• Keep blocking filesystem, process, or indexing work off the main async path when it can stall responsiveness.
• Use the project's async runtime conventions consistently.
• Preserve cancellation and shutdown behavior where long-running tasks exist.
• Prefer message passing, task isolation, or scoped ownership over broad shared mutable state.
• Make background work observable and controllable when it affects the UI experience.