observability-engineer

Use when adding/changing LLM providers, models, routing, fallback, cost or capability policy.

Use when adding a free/low-cost third-party API or replacing a paid dependency during development.

Use when exposing or consuming reusable tools/resources through MCP.

Use when a feature needs generation, classification, extraction, RAG, vision or tool use.

Use before release and whenever auth, personal data, external content, tools, payments or write side effects change.

Use before material implementation or when a change crosses UI, AI, tools, data, security or deployment boundaries.

Use for schema, Auth, RLS, Storage, Realtime, pgvector, Edge Functions or Supabase performance/security work.

Use for product flows, information architecture, interaction design and visual system decisions.

Use for route handlers, business logic, queues, caching, rate limits and external integrations.

Use only when a workflow requires iterative planning, tools, handoffs or state beyond one model call.

Use for Vercel project setup, preview/production deployments, environment separation, domains, logs and rollback.

Use for Next.js/React UI implementation, state, forms, routes, performance and accessibility.