Help us improve
Share bugs, ideas, or general feedback.
From uber-engineer
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.
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:api-developmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
API contracts, versioning, backward compatibility, error schemas, and developer experience.
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.
API contracts, versioning, backward compatibility, error schemas, and developer experience.
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: API design, REST, GraphQL, gRPC, OpenAPI, Swagger, API versioning, deprecation, error schema, RFC 7807, problem details, webhook, pagination, rate limit, API key, OAuth scopes, SDK, API gateway.
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.page=N&size=M over data that mutates between requests./api design-resource users/api version-bump --from=v1 --to=v2/api webhook-contract subscription.createdreferences/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.