Skill

api-design

API design patterns: REST naming/pagination/errors, GraphQL schema design, gRPC streaming, versioning strategies, idempotency keys, rate limiting. Use when designing APIs.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milligan

Tool Access

This skill is limited to using the following tools:

ReadGrepGlob

Preview

- Designing REST, GraphQL, or gRPC APIs

Supporting Assets

assets/openapi-template.yamlreferences/api-versioning-strategies.mdreferences/graphql-patterns.mdreferences/grpc-patterns.mdreferences/rest-best-practices.md

SKILL.md

Similar Skills

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

156.2k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

156.2k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitFeb 23, 2026

Actions

View Source View Plugin View on GitHub View README

Core principles

Consistent resource naming — plural nouns, kebab-case, no verbs in URLs

Cursor pagination by default — offset fails at scale

Idempotency keys for mutations — clients safely retry without duplicate side effects

Version from day one — breaking changes without versioning = broken clients

Error responses are part of the API — structured, consistent, with request ID

References available

references/rest-best-practices.md — naming, pagination, error format, idempotency, rate limiting

references/graphql-patterns.md — schema design, N+1 with DataLoader, fragments, subscriptions

references/grpc-patterns.md — protobuf design, streaming, deadlines, load balancing

references/api-versioning-strategies.md — URL vs header vs content negotiation trade-offs

API Design Patterns

When to use

Designing REST, GraphQL, or gRPC APIs
Choosing pagination, versioning, or error format strategies
Implementing idempotency, rate limiting, or API gateways

Core principles

Consistent resource naming — plural nouns, kebab-case, no verbs in URLs
Cursor pagination by default — offset fails at scale
Idempotency keys for mutations — clients safely retry without duplicate side effects
Version from day one — breaking changes without versioning = broken clients
Error responses are part of the API — structured, consistent, with request ID

References available

references/rest-best-practices.md — naming, pagination, error format, idempotency, rate limiting
references/graphql-patterns.md — schema design, N+1 with DataLoader, fragments, subscriptions
references/grpc-patterns.md — protobuf design, streaming, deadlines, load balancing
references/api-versioning-strategies.md — URL vs header vs content negotiation trade-offs

Assets available

assets/openapi-template.yaml — starter OpenAPI 3.1 spec with best-practice patterns