Generate API contracts, DTOs, and OpenAPI YAML from domain models.
npx skills add https://github.com/YuluoY/nimis --skill api-contract-design-yuluoy
Please help me install this Agent Skill. Skill: api-contract-design Source: https://github.com/YuluoY/nimis/tree/main/skills-en/api-contract-design Command: npx skills add https://github.com/YuluoY/nimis --skill api-contract-design-yuluoy
Transforms domain models and requirement documents into concrete, standardized API interface contracts so engineering teams can implement consistent endpoints, DTOs, and error handling without design ambiguity.
Use the api-contract-design skill to generate an OpenAPI YAML, DTO definitions, and an endpoint table from the provided domain model and requirements.
High-intent search queries and answers about installing and using this skill.
Generate OpenAPI YAML by transforming domain models and requirements into standardized API contracts. This process produces endpoint lists, request/response DTOs, and module-organized OpenAPI specifications with mermaid diagrams and design checklists.
Design RESTful and GraphQL endpoints by extracting resources from domain models and mapping CRUD actions to endpoints. This applies naming and idempotency rules to produce a structured endpoint table for backend engineering tasks.
Standardize API error codes and DTO specifications by generating a unified error code catalog and TypeScript or Java interface examples. This ensures consistent error handling and request/response structures across engineering teams.
API contract design supports API refactoring and versioning by generating versioning strategies and contract test case checklists. It transforms existing models into updated interface contracts to eliminate design ambiguity during public API overhauls.
API contract generation produces importable OpenAPI YAML specs specifically for API gateways and documentation. It scaffolds DTO structures, pagination patterns, and validation artifacts for consumer-provider verification.
An API contract resolves design ambiguity by transforming domain models into concrete, standardized interface specifications. Engineering teams use these contracts to implement consistent endpoints, DTOs, and error handling without misalignment.
TonyQ-AIExtract core business concepts, entity relationships, and domain rules from requirement specifications.
secondskyAutomate API documentation creation from OpenAPI 3.0 specifications.
windyskyScaffold Spring Boot 3.3 microservices using Java 21 virtual threads and pattern matching.
rsmdtApply standardized REST and GraphQL design patterns to API contracts and versioning.
