ardanlabs

Prefer defaulting and naked switches over if/else chains for shallow branching logic in Go. Use when writing or refactoring conditional logic with 1-3 branches.

Use when adding a cross-cutting concern (OTEL tracing, logging, metrics, caching, auth) to a business domain, creating files under business/domain/*/extensions/*, or adding the extension seam (ExtBusiness/Extension) to a *bus package.

Enforce primitive-at-edges / strong-types-in-Business layering and the toBus/fromBusResponse/toDB converter pattern. Use when writing, editing, or auditing Go files under app/*, business/domain/*, or .../stores/*db.

Service Diffguard: read-only PR review lenses for correctness, error visibility, comment truthfulness, test coverage, type/contract boundaries, and simplification across every language in this repo (Go, Vue/JS/SCSS, Rego, protobuf, SQL, Helm/YAML, shell). Use for PR review, pre-commit review, unstaged-diff review, or a targeted review of one of those aspects.

Apply modern Go syntax guidelines based on the project's Go version. Use whenever writing, editing, or reviewing Go (.go) code — not only when explicitly asked for guidelines.

Enforce primitive-at-edges / strong-types-in-Business layering and the toBus/fromBusResponse/toDB converter pattern. Use when writing, editing, or auditing Go files under app/*, business/domain/*, or .../stores/*db.

Service DiffGuard: read-only PR review lenses for security (secrets/data-leak/vulnerability, mandatory), feature-completeness against acceptance criteria (unimplemented required behavior in unchanged files, mandatory when a ticket is supplied), correctness, error visibility, comment truthfulness, test coverage, type/contract boundaries, duplicate-code detection, and simplification across every language in the target service repo (Go, Vue/JS/SCSS, Rego, protobuf, SQL, Helm/YAML, shell). Drives a guided run: prompts for missing inputs (diff scope, issue-tracker URL, issue id), reviews the diff against the ticket's acceptance criteria, and writes auto-numbered findings and Mermaid diagram files under .reviews/<issue-id>/. USE whenever the user asks to review a PR or diff in any phrasing — "review this PR", "review my PR", "PR review", "can you review this pull request", "review the diff/changes", "review my code before I commit", "pre-commit review", "look over these changes", "review the branch", "unstaged-diff

Prefer defaulting and naked switches over if/else chains for shallow branching logic in Go. Use when writing or refactoring conditional logic with 1-3 branches.

Use when adding a cross-cutting concern (OTEL tracing, logging, metrics, caching, auth) to a business domain, creating files under business/domain/*/extensions/*, or adding the extension seam (ExtBusiness/Extension) to a *bus package.

Apply modern Go syntax guidelines based on the project's Go version. Use whenever writing, editing, or reviewing Go (.go) code — not only when explicitly asked for guidelines.

Apply modern Go syntax guidelines based on project's Go version. Use when user ask for modern Go code guidelines.

Post-edit toolchain to run after writing or modifying any `.go` file. Load whenever a task changes Go source.

Using the Kronk MCP service in the default agent configuration, where Kronk is wired directly into the host (OpenCode, Kilo, Pi) as an MCP server. Exposes `fuzzy_edit` (fallback for the host's exact-match edit when whitespace / line-endings cause it to miss) and `web_search` (Brave-powered). Load whenever you need web research, or when a host edit fails on exact matching.

The ONLY sanctioned path to the Kronk MCP service (`web_search`, `fuzzy_edit`) in the rote-routed config. Every command is a `rote ...` invocation in Bash. Load whenever you need web research, or when a host edit fails on exact-string matching and you need the rote-routed `fuzzy_edit` fallback.