api-design-architect
RESTful and GraphQL API design expert covering best practices, security, and scalability
When & Why to Use This Skill
The API Design Architect skill provides expert-level guidance for building robust, secure, and scalable APIs. It leverages industry-standard playbooks to assist developers and architects in selecting protocols (REST, GraphQL, gRPC), implementing security best practices like OWASP, and managing the full API lifecycle from versioning to governance.
Use Cases
- Architecting scalable API ecosystems: Guidance on choosing between REST, GraphQL, or gRPC based on specific technical requirements and stakeholder needs.
- Security and Threat Modeling: Applying OWASP API Security Top 10 principles and implementing robust authentication, authorization, and rate-limiting strategies.
- Lifecycle Management and Governance: Planning versioning strategies, documentation workflows, and change management to ensure long-term API consumability.
- Performance Optimization: Implementing observability, telemetry, and design patterns that ensure high availability and low latency for enterprise-grade interfaces.
| name | api-design-architect |
|---|---|
| description | RESTful and GraphQL API design expert covering best practices, security, and scalability |
| license | Proprietary |
API Design Architect
Status: ✅ Research complete Last validated: 2025-11-08 Confidence: 🟡 Medium — Research-backed playbook – refresh quarterly
How to use this skill
- Skim modules/core-guidance.md for framing and triage cues.
- Load protocol-specific patterns from modules/design-foundations.md.
- Use modules/lifecycle-and-governance.md to plan change management and documentation.
- Apply modules/security-and-observability.md before launch.
- Revisit modules/known-gaps.md each quarter and log findings in the modules/research-checklist.md.
Module overview
- Core guidance — decision tree, API style selection, stakeholder prompts.
- Design foundations — REST, GraphQL, gRPC, and event-driven design blueprints.
- Lifecycle & governance — versioning, review ceremonies, documentation, consumability.
- Security & observability — authn/z, rate limiting, threat modelling, telemetry.
- Known gaps — research debt and upcoming RFCs to review.
- Research checklist — renewal workflow with links to canonical sources.
Research status
- Content incorporates Microsoft REST API Guidelines (2024), OWASP API Security Top 10 (2023), CNCF API landscape (2025), and GraphQL June 2024 spec.
- Schedule next validation for 2026-02-01 or sooner if major API standard releases occur.
- Known gaps call out AsyncAPI 3.1 adoption notes and RESTful hypermedia case studies still pending deep dive.