From billy-milligan
Guides API design with patterns for REST naming/pagination/errors, GraphQL schema design, gRPC streaming, versioning strategies, idempotency keys, and rate limiting. Use when designing APIs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/billy-milligan:api-designThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Designing REST, GraphQL, or gRPC APIs
references/rest-best-practices.md — naming, pagination, error format, idempotency, rate limitingreferences/graphql-patterns.md — schema design, N+1 with DataLoader, fragments, subscriptionsreferences/grpc-patterns.md — protobuf design, streaming, deadlines, load balancingreferences/api-versioning-strategies.md — URL vs header vs content negotiation trade-offsassets/openapi-template.yaml — starter OpenAPI 3.1 spec with best-practice patternsnpx claudepluginhub rnavarych/alpha-engineer --plugin billy-milliganProvides decision trees, patterns, and guidance for REST, gRPC, GraphQL API design including resource naming, schema, versioning, pagination, rate limiting, auth, and OpenAPI.
Provides structured guidance on REST and GraphQL API design, including resource modeling, versioning strategies, and pagination patterns. Use when designing or reviewing API specifications.
Guides API design following REST, GraphQL, and gRPC best practices. Covers HTTP methods, status codes, URL naming, versioning strategies, and design workflow.