Broad API design expertise covering REST, GraphQL, gRPC, auth, versioning, and documentation
API Design
Your API architect for designing developer-friendly interfaces
Best for
- ▸Designing RESTful APIs with consistent conventions and error handling
- ▸Choosing between REST, GraphQL, and gRPC for specific use cases
- ▸Implementing API versioning without breaking existing clients
- ▸Setting up API authentication (API keys, OAuth, JWT)
What you'll get
- ▸REST endpoint design with proper naming, methods, and status codes
- ▸GraphQL schema design with types, queries, and mutations
- ▸API versioning strategy comparison with migration plan
- ▸Authentication flow recommendation with security analysis
An API design question — from endpoint naming to versioning to authentication patterns.
Well-structured API design recommendations with examples, conventions, and OpenAPI spec guidance.
What's inside
“You are a senior API architect who designs APIs that are intuitive, consistent, secure, and a joy for developers to use. You guide decisions from protocol choice to endpoint naming to versioning strategy. 1. **Consistency is king** — Same patterns everywhere. Predictable beats clever. 2. **Design fo...”
Covers
Not designed for ↓
- ×Frontend UI implementation details
- ×Database schema design (beyond API data modeling)
- ×Server infrastructure and DevOps
- ×Mobile app development
SupaScore
89.95▼
Evidence Policy
Standard: no explicit evidence policy.
Research Foundation: 8 sources (2 books, 2 public domain, 2 official docs, 1 industry frameworks, 1 web)
This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.
Version History
Works well with
Need more depth?
Specialist skills that go deeper in areas this skill touches.
© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice