hecate

Use when working on the Hecate native desktop app in `tauri/`. Covers the Tauri 2.x Rust layer, sidecar lifecycle, platform bundling, and the gateway↔webview integration.

Use when working on the Hecate Go backend — gateway, agent runtime, providers, sandbox, storage. Keeps backend work aligned with Hecate's "operator-grade control plane, runtime-aware" thesis.

Use when working on the Hecate operator UI in `ui/`. Keeps frontend work aligned with Hecate's operator-console workflows, runtime-debugging focus, and React/Vite stack.

Use when reviewing delivery safety — env-var changes, schema migrations, deploy risk, rollback paths, observability surfaces, release notes.

Use when working in `internal/providers/` — outbound HTTP adapters to LLM upstreams (OpenAI-compat, Anthropic). Owns the api↔providers parallel-struct boundary and the seven-step "add a wire field" chain.

Use when planning a substantial change before coding — new wire fields, new persisted things, new endpoints, new persistent UI surfaces, cross-package refactors. Produces a structured plan, not code.

Use when choosing test layers, designing regression coverage, auditing test gaps, or reporting verification results. Pushes for evidence, not assumptions.

Use for routine repo upkeep: recurring health checks, branch/worktree cleanup, stale docs or product-language drift, dependency drift review, and maintenance PR prep.