This is the Hecate repo — an open-source AI gateway and agent-task runtime (Go gateway with embedded React UI plus companion integration entrypoints). Shared agent guidance lives in docs-ai/. This file is a thin Claude-specific adapter; the substance lives there.
docs-ai/README.md is the entry point and map.
Pick the right skill for the change:
- Backend (anything outside
ui/andtauri/) —hecate-backend. - UI (
ui/) —hecate-ui. - Native desktop app (
tauri/) —hecate-tauri. Tauri 2.x Rust layer, sidecar lifecycle, platform bundling, gateway↔webview integration. - Provider adapters (
internal/providers/, anything that crosses the api↔providers boundary) —hecate-providers. Owns the canonical seven-step "add a wire field" chain. - Planning a substantial change —
hecate-architect. Produces a plan, not code. - Test strategy / coverage audit / verification report —
hecate-tester. - Delivery review (env vars, schema migrations, CI/CD, observability surfaces) —
hecate-devops.
| Command | What it does |
|---|---|
/race |
Full Go race suite — the canonical "ready to commit" check for runtime/backend changes |
/test-affected |
Tests only for packages touched in the working tree |
Shared agent guidance is repository-owned and committed. There is no .local override layer and no personal customization tier. If a rule belongs in agent context, it lives in docs-ai/, in the open, under version control.
AGENTS.md at the repo root, ui/AGENTS.md, and internal/providers/AGENTS.md are the codebase map and the Codex-discoverable entry points. They stay scoped to map-and-recipes; conventions and longer guidance live in docs-ai/.