Openapi To Application Code

1---2name: openapi-to-application-code3description: 'Generate a complete, production-ready application from an OpenAPI specification'4---5 6# Generate Application from OpenAPI Spec7 8Your goal is to generate a complete, working application from an OpenAPI specification using the active framework's conventions and best practices.9 10## Input Requirements11 121. **OpenAPI Specification**: Provide either:13   - A URL to the OpenAPI spec (e.g., `https://api.example.com/openapi.json`)14   - A local file path to the OpenAPI spec15   - The full OpenAPI specification content pasted directly16 172. **Project Details** (if not in spec):18   - Project name and description19   - Target framework and version20   - Package/namespace naming conventions21   - Authentication method (if not specified in OpenAPI)22 23## Generation Process24 25### Step 1: Analyze the OpenAPI Specification26- Validate the OpenAPI spec for completeness and correctness27- Identify all endpoints, HTTP methods, request/response schemas28- Extract authentication requirements and security schemes29- Note data model relationships and constraints30- Flag any ambiguities or incomplete definitions31 32### Step 2: Design Application Architecture33- Plan directory structure appropriate for the framework34- Identify controller/handler grouping by resource or domain35- Design service layer organization for business logic36- Plan data models and entity relationships37- Design configuration and initialization strategy38 39### Step 3: Generate Application Code40- Create project structure with build/package configuration files41- Generate models/DTOs from OpenAPI schemas42- Generate controllers/handlers with route mappings43- Generate service layer with business logic44- Generate repository/data access layer if applicable45- Add error handling, validation, and logging46- Generate configuration and startup code47 48### Step 4: Add Supporting Files49- Generate appropriate unit tests for services and controllers50- Create README with setup and running instructions51- Add .gitignore and environment configuration templates52- Generate API documentation files53- Create example requests/integration tests54 55## Output Structure56 57The generated application will include:58 59```60project-name/61├── README.md                      # Setup and usage instructions62├── [build-config]                 # Framework-specific build files (pom.xml, build.gradle, package.json, etc.)63├── src/64│   ├── main/65│   │   ├── [language]/66│   │   │   ├── controllers/       # HTTP endpoint handlers67│   │   │   ├── services/          # Business logic68│   │   │   ├── models/            # Data models and DTOs69│   │   │   ├── repositories/      # Data access (if applicable)70│   │   │   └── config/            # Application configuration71│   │   └── resources/             # Configuration files72│   └── test/73│       ├── [language]/74│       │   ├── controllers/       # Controller tests75│       │   └── services/          # Service tests76│       └── resources/             # Test configuration77├── .gitignore78├── .env.example                   # Environment variables template79└── docker-compose.yml             # Optional: Docker setup (if applicable)80```81 82## Best Practices Applied83 84- **Framework Conventions**: Follows framework-specific naming, structure, and patterns85- **Separation of Concerns**: Clear layers with controllers, services, and repositories86- **Error Handling**: Comprehensive error handling with meaningful responses87- **Validation**: Input validation and schema validation throughout88- **Logging**: Structured logging for debugging and monitoring89- **Testing**: Unit tests for services and controllers90- **Documentation**: Inline code documentation and setup instructions91- **Security**: Implements authentication/authorization from OpenAPI spec92- **Scalability**: Design patterns support growth and maintenance93 94## Next Steps95 96After generation:97 981. Review the generated code structure and make customizations as needed992. Install dependencies according to framework requirements1003. Configure environment variables and database connections1014. Run tests to verify generated code1025. Start the development server1036. Test endpoints using the provided examples104 105## Questions to Ask if Needed106 107- Should the application include database/ORM setup, or just in-memory/mock data?108- Do you want Docker configuration for containerization?109- Should authentication be JWT, OAuth2, API keys, or basic auth?110- Do you need integration tests or just unit tests?111- Any specific database technology preferences?112- Should the API include pagination, filtering, and sorting examples?