Help us improve
Share bugs, ideas, or general feedback.
From uber-engineer
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).
npx claudepluginhub blaze-sports-intel/uber-engineer --plugin uber-engineerHow this skill is triggered — by the user, by Claude, or both
Slash command
/uber-engineer:backend-developmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Service architecture, API contracts, auth, data persistence, and operational hygiene.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Service architecture, API contracts, auth, data persistence, and operational hygiene.
This skill is part of the uber-engineer plugin's discipline coverage. Pair with the
discipline-router agent when a request crosses disciplines, and the build-validator agent
before claiming any work is done.
Trigger words: backend, API, REST, GraphQL, server, Node.js, Python, Go, Java, Spring Boot, Express, Fastify, FastAPI, Django, Rails, authentication, authorization, JWT, OAuth, rate limiting, idempotency, caching, queue, background job.
Use when the user wants any of:
discipline-router agent before splitting work.references/official-sources.md. Use the Context7 MCP for live doc lookups instead of
relying on training-data memory for fast-moving APIs.{ "error": ... } in the body./backend design-endpoint POST /v1/orders/backend auth-flow oauth2-pkce/backend ratelimit /v1/checkout --tier=premiumreferences/official-sources.md — authoritative documentation URLs.references/workflow-playbook.md — detailed step-by-step playbook.references/anti-patterns.md — anti-pattern catalog with fixes.references/quality-rubric.md — pass/fail rubric for review.references/examples.md — concrete examples, before/after diffs.scripts/validate_skill.py — sanity-checks SKILL.md frontmatter and references.A real user, operator, or downstream system experiences the correct outcome of this work. Build success and deploy success do not equal done. The discipline-specific states below must all hold:
Verification actually happened — no claim of "verified" without evidence.