uber-engineer

AI/ML Development — invoke the ai-ml-development skill with focused intent.

API Development — invoke the api-development skill with focused intent.

Backend Development — invoke the backend-development skill with focused intent.

Blockchain Development — invoke the blockchain-development skill with focused intent.

Cloud Development — invoke the cloud-development skill with focused intent.

Verifies that a claimed change actually works end-to-end before any "done" claim ships to the user. Use proactively after any edit, deploy, or migration. This agent enforces the user's "Definition of Done" rule: build success ≠ done; visible correct output = done.

Reviews a diff or PR for correctness, security, performance, and maintainability before merge. Use after writing or modifying code. Reports only high-confidence, high-impact issues — not nitpicks.

Routes ambiguous or cross-cutting engineering requests to the right discipline skill(s) inside the uber-engineer plugin. Use when the user asks for something that touches multiple layers (e.g. "ship a feature with UI + API + DB + tests") or when the right discipline isn't obvious from the request.

Audits "done" claims against actual visible output. Use proactively when an agent or human says "shipped", "deployed", "verified", "done", or claims a user can now see something. Catches false completions where build/deploy succeeded but the visible surface is broken.

Experiment workflows, datasets, evals, model packaging, serving, and rollback for AI/ML systems. Use when the user mentions: ML, machine learning, AI, model training, fine-tuning, PyTorch, TensorFlow, JAX, scikit-learn, Hugging Face, LangChain, LlamaIndex, evals, RAG, vector database, embeddings, MLflow, Weights & Biases, prompt engineering, Anthropic API, OpenAI API. Pair with the discipline-router agent for cross-cutting work. Do NOT trigger for: data analysis without model training (use data-science-development); ML infra rollout work without model changes (use devops-and-infrastructure).

Public-facing API contract design: paths, versioning, backward compatibility, error schemas, webhook signing, SDK generation, developer experience. Use when the user mentions: API design, REST design, GraphQL schema, gRPC proto, OpenAPI, Swagger, API versioning, deprecation policy, error schema, RFC 7807, problem details, webhook contract, cursor pagination, API key issuance, OAuth scopes, SDK generation, API gateway, public docs. Pair with the discipline-router agent for cross-cutting work. Do NOT trigger for: implementing the handlers behind the contract (use backend-development — this skill designs the wire; backend-development builds the service); internal-only service-to-service calls without external contract; frontend data fetching strategy without server contract change.

Spatial UX, perf budgets, motion comfort, anchors, hand/eye input, and platform-specific deploy. Use when the user mentions: AR, VR, XR, spatial, Vision Pro, visionOS, Quest, Meta Horizon, ARKit, ARCore, WebXR, OpenXR, Unity XR, Unreal XR, RealityKit, RealityComposer, hand tracking, eye tracking, passthrough, motion sickness. Pair with the discipline-router agent for cross-cutting work. Do NOT trigger for: flat 2D UI work (use frontend-development); mobile non-XR apps (use mobile-development).

Service implementation behind the wire contract: handlers, auth enforcement, persistence integration, idempotency, caching, queues, observability. Use when the user mentions: backend, server, service, handler, Node.js, Python, Go, Java, Spring Boot, Express, Fastify, FastAPI, Django, Rails, authentication enforcement, authorization, JWT verification, OAuth callback, session, rate limiting, idempotency, caching, queue, background job, worker. Pair with the discipline-router agent for cross-cutting work. Do NOT trigger for: public API contract design / versioning / SDK generation (use api-development — this skill implements behind the contract; api-development designs the contract); pure frontend UI work (use frontend-development); database schema migration work (use database-development); container orchestration / deploy pipeline (use devops-and-infrastructure).

Smart contracts, wallet UX, indexers, security review, and on-chain integration. Use when the user mentions: blockchain, Ethereum, Solidity, Foundry, Hardhat, Rust smart contracts, Solana, Anchor, wallet, ERC-20, ERC-721, NFT, DeFi, EVM, subgraph, indexer, RPC, MEV, wagmi, viem, ethers.js. Pair with the discipline-router agent for cross-cutting work. Do NOT trigger for: general web3 frontend without contract code (use frontend-development); trading bots without on-chain integration.

21 hooks across 3 events

Supabase project management — schemas, migrations, RLS, edge functions, branches.

GitHub repos, PRs, issues, actions, gists.

Cloudflare Workers, D1, KV, R2, Pages, Hyperdrive, Durable Objects.

Stripe payments, customers, subscriptions, invoices, webhooks.

PostHog analytics, feature flags, experiments, session replays, error tracking.