keynobi AGENTS.md

Agent Instructions

Tech Stack

• Framework: Tauri 2.0 (Rust backend + WKWebView frontend)
• Frontend: SolidJS + TypeScript + Vite
• Backend: Rust (tokio async runtime)
• Parsing: Tree-sitter (tree-sitter-kotlin-ng)
• Search: ripgrep library crates (grep-regex, grep-searcher, grep-matcher)
• Language Intelligence: JetBrains Kotlin/kotlin-lsp (download-on-demand)
• IPC Types: ts-rs (Rust → TypeScript auto-generation)
• State Management: SolidJS Stores (createStore, produce)
• Testing: Vitest (frontend), Rust #[test] / tokio::test (backend), Criterion (benchmarks)

Before You Write Code

1. Read docs/BEST_PRACTICES.md — architectural principles, security rules, performance targets, and the AI-first design philosophy.
2. Read docs/CODE_PATTERN.md and docs/DOMAIN_PATTERNS.md — concrete conventions: file naming, store patterns, IPC patterns, testing patterns.
3. Read docs/USER_MANUAL.md — understand what the user sees and does, so new features integrate naturally.

Key Rules

• Path security: Every command that accepts a path must validate it against the project root using canonicalization (see CODE_PATTERN.md §Path Security). Never use raw starts_with() without canonicalization.
• Keybindings = Actions: Use registerKeyAndAction() in App.tsx, never bare registerKeybinding(). Shortcuts that bypass the action registry are invisible in the command palette.
• Navigation: All jump-to-location actions must call openFileAtLocation() from project.service.ts, not setActiveFile() directly. This populates the navigation history stack.
• IPC types: Import from @/bindings, never redefine types that originate in Rust.
• Mutex discipline: Lock Rust state, clone what you need, drop the lock, then do I/O. Never hold a Mutex across an await.
• Bounded collections: Every in-memory collection that grows must have an explicit cap (see BEST_PRACTICES.md).
• No unwrap() in production Rust: Use ? or .map_err(...). expect() is allowed only for programmer-error invariants.
• Do not commit: The superpower spec and plan files.