moai-domain-web-api

OpenAPI 3.1 compliance ensures your REST API specification is machine-readable and standards-aligned. This Skill guides you through creating OpenAPI 3.1-compliant contracts that document endpoints, authentication patterns, request/response schemas, and versioning strategies for production-ready APIs.

Secure APIs require explicit authentication and authorization strategies. This Skill covers OAuth2 and JWT patterns to protect endpoints, implement role-based access control, and validate credentials—reducing deployment risk and meeting security best practices.

API versioning prevents breaking changes from disrupting client applications. This Skill provides clear strategies to evolve your REST and GraphQL APIs through versioning schemes, deprecation policies, and backward-compatible design patterns.

Yes. OpenAPI 3.1 specifications enable automatic documentation generation and test scaffolding, accelerating ship-readiness. This Skill shows how to leverage your contract to produce living docs and reduce manual testing overhead.

Rate limiting protects APIs from abuse and resource exhaustion. This Skill covers rate-limiting strategies for both REST and GraphQL endpoints, including traffic management approaches that align with modern backend patterns and governance workflows.

Yes. This Skill integrates OpenAPI design with test-driven development workflows and quality-gate governance, ensuring your API contracts are tested, versioned, and validated before deployment.