Note

• Copilot prompt files are in public preview and subject to change. Prompt files are only available in VS Code. SeeAbout customizing GitHub Copilot Chat responses.
• For community-contributed examples of prompt files for specific languages and scenarios, see theAwesome GitHub Copilot Customizations repository.

---mode: 'agent'description: 'Generate OpenAPI 3.0 specification for API endpoints'---## TaskAnalyze the API endpoint code and generate a valid OpenAPI 3.0 specification in YAML format.## OpenAPI StructureGenerate a complete OpenAPI spec including:1. **OpenAPI Header**   - OpenAPI version (3.0.3)   - API info (title, description, version)   - Server configuration2. **Path Definitions**   - HTTP method and path   - Operation summary and description   - Tags for organization3. **Parameters Schema**   - Path parameters with type validation   - Query parameters with constraints and defaults   - Request body schema using proper JSON Schema   - Required vs optional parameters4. **Response Schemas**   - Success responses (200, 201, etc.) with schema definitions   - Error responses (400, 401, 404, 500) with error schema   - Content-Type specifications   - Realistic example values5. **Components Section**   - Reusable schemas for request/response models   - Security schemes (Bearer token, API key, etc.)   - Common parameter definitions## Requirements- Generate valid OpenAPI 3.0.3 YAML that passes validation- Use proper JSON Schema for all data models- Include realistic example values, not placeholders- Define reusable components to avoid duplication- Add appropriate data validation (required fields, formats, constraints)- Include security requirements where applicableFocus on: ${input:endpoint_focus:Which specific endpoint or endpoints should be documented?}Generate production-ready OpenAPI specification that can be used with Swagger UI, Postman, and code generators.

---mode: 'agent'description: 'Generate OpenAPI 3.0 specification for API endpoints'---## TaskAnalyze the API endpoint code and generate a valid OpenAPI 3.0 specification in YAML format.## OpenAPI StructureGenerate a complete OpenAPI spec including:1. **OpenAPI Header**   - OpenAPI version (3.0.3)   - API info (title, description, version)   - Server configuration2. **Path Definitions**   - HTTP method and path   - Operation summary and description   - Tags for organization3. **Parameters Schema**   - Path parameters with type validation   - Query parameters with constraints and defaults   - Request body schema using proper JSON Schema   - Required vs optional parameters4. **Response Schemas**   - Success responses (200, 201, etc.) with schema definitions   - Error responses (400, 401, 404, 500) with error schema   - Content-Type specifications   - Realistic example values5. **Components Section**   - Reusable schemas for request/response models   - Security schemes (Bearer token, API key, etc.)   - Common parameter definitions## Requirements- Generate valid OpenAPI 3.0.3 YAML that passes validation- Use proper JSON Schema for all data models- Include realistic example values, not placeholders- Define reusable components to avoid duplication- Add appropriate data validation (required fields, formats, constraints)- Include security requirements where applicableFocus on: ${input:endpoint_focus:Which specific endpoint or endpoints should be documented?}Generate production-ready OpenAPI specification that can be used with Swagger UI, Postman, and code generators.