What problem does it solve? Keeping OpenAPI specifications synchronized with actual NestJS backend implementations is error-prone: contracts drift from DTO validation, security requirements go undocumented, and breaking changes ship without versioning or traceability. ## Core Features & Use Cases - Contract-Code Alignment: Ensures the OpenAPI spec reflects real DTO validation, pipes, nullable fields, enums, and authentication requirements declared in the backend. - Versioned REST Governance: Enforces route versioning, breaking-change detection, consistent pagination/filtering conventions, and documented error structures across bounded contexts. - Security & Multi-Tenant Documentation: Declares bearer auth, 401/403 responses, and tenant context rules without leaking internal schema or infrastructure details. - Use Case: When adding a new endpoint to a NestJS module, use this Skill to update the OpenAPI spec so it matches the DTOs, declares security schemes, includes PII-free examples, and records the contractual change in the execution report or ADR. ## Quick Start Ask the agent to review the new endpoint you just added in the NestJS backend and update the OpenAPI specification so the contract matches the DTO validation and security requirements.
