Use this agent for Metabase Clojure backend work on enterprise platform features — serialization (export/import), audit logging, SCIM provisioning, multi-tenancy, database routing, dependency tracking, remote sync, premium features infrastructure, content translation, stale content detection, or support access grants.…
Use this agent for Metabase Clojure backend work on query processor (QP), MBQL query language, SQL compilation, driver system, middleware pipeline, Lib, metadata providers, or streaming execution. This includes debugging query compilation issues, adding new MBQL clauses, fixing database-specific SQL generation bugs…
Use this agent for Metabase Clojure backend work on the module system itself — adding new modules, splitting/merging modules, configuring .clj-kondo/config/modules/config.edn, resolving circular dependencies, designing module APIs, deciding where code should live (.core vs .api vs .init vs .models.), interpreting…
Review Cypress E2E spec files for Metabase conventions, common gotchas, and flakiness/performance issues. Use when reviewing pull requests or diffs containing Cypress spec files in e2e/test/scenarios/.
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports from components.
Update or build a Metabase design-system component (frontend/src/metabase/ui — Chip, Badge, Alert, Switch, etc.) to match a Figma spec described in a Linear issue. Use when a ticket asks to restyle an existing metabase/ui component or implement a new one from Figma. Covers: checking out the issue, mapping the…
Claude Code instructions for evidence-dev/evidence, a project described as: Business intelligence as code: build fast, interactive data visualizations in SQL and markdown.
Manage a production-like Lightdash deployment on Azure AKS with the Azure Container Apps Sandboxes backend. Args: (none) = status, up = idempotently provision + deploy, deploy = build this branch → ACR → roll the deployment, down = tear everything down to stop spend.
Debug the Lightdash app using PM2 logs, Maple traces, and browser automation. Use when investigating issues, tracking down bugs, understanding request flow, or correlating frontend actions with backend behavior.
Apply the Lightdash frontend style guide and design principles when working on React components or styling frontend code. Use when editing TSX files, building or reviewing UI, fixing styling issues, or when the user mentions Mantine, design, styling, or CSS modules.