Add three .github prompts for API, code, tests

Add three prompt templates under .github/prompts: document-api.prompt.md, explain-code.prompt.md, and generate-unit-tests.prompt.md. Each file provides an agent prompt and guidance for automated content generation: document-api guides generation of OpenAPI 3.0.3 YAML specs (paths, components, schemas, security, examples); explain-code produces beginner-friendly code explanations with breakdowns and examples; generate-unit-tests outlines strategies and templates for creating 5–8 focused unit tests following AAA and project test framework conventions. Includes input placeholders to target specific endpoints, code snippets, or functions.

Author: mercyblitz

.github/prompts/document-api.prompt.md

@@ -0,0 +1,52 @@
+---
+agent: 'agent'
+description: 'Generate OpenAPI 3.0 specification for API endpoints'
+---
+
+## Task
+
+Analyze the API endpoint code and generate a valid OpenAPI 3.0 specification in YAML format.
+
+## OpenAPI Structure
+
+Generate a complete OpenAPI spec including:
+
+1. **OpenAPI Header**
+    - OpenAPI version (3.0.3)
+    - API info (title, description, version)
+    - Server configuration
+
+2. **Path Definitions**
+    - HTTP method and path
+    - Operation summary and description
+    - Tags for organization
+
+3. **Parameters Schema**
+    - Path parameters with type validation
+    - Query parameters with constraints and defaults
+    - Request body schema using proper JSON Schema
+    - Required vs optional parameters
+
+4. **Response Schemas**
+    - Success responses (200, 201, etc.) with schema definitions
+    - Error responses (400, 401, 404, 500) with error schema
+    - Content-Type specifications
+    - Realistic example values
+
+5. **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 applicable
+
+Focus 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.

.github/prompts/explain-code.prompt.md

@@ -0,0 +1,19 @@
+---
+agent: 'agent'
+description: 'Generate a clear code explanation with examples'
+---
+
+Explain the following code in a clear, beginner-friendly way:
+
+Code to explain: ${input:code:Paste your code here}
+Target audience: ${input:audience:Who is this explanation for? (e.g., beginners, intermediate developers, etc.)}
+
+Please provide:
+
+* A brief overview of what the code does
+* A step-by-step breakdown of the main parts
+* Explanation of any key concepts or terminology
+* A simple example showing how it works
+* Common use cases or when you might use this approach
+
+Use clear, simple language and avoid unnecessary jargon.

.github/prompts/generate-unit-tests.prompt.md

@@ -0,0 +1,52 @@
+---
+agent: 'agent'
+description: 'Generate unit tests for selected functions or methods'
+---
+
+## Task
+
+Analyze the selected function/method and generate focused unit tests that thoroughly validate its behavior.
+
+## Test Generation Strategy
+
+1. **Core Functionality Tests**
+    - Test the main purpose/expected behavior
+    - Verify return values with typical inputs
+    - Test with realistic data scenarios
+
+2. **Input Validation Tests**
+    - Test with invalid input types
+    - Test with null/undefined values
+    - Test with empty strings/arrays/objects
+    - Test boundary values (min/max, zero, negative numbers)
+
+3. **Error Handling Tests**
+    - Test expected exceptions are thrown
+    - Verify error messages are meaningful
+    - Test graceful handling of edge cases
+
+4. **Side Effects Tests** (if applicable)
+    - Verify external calls are made correctly
+    - Test state changes
+    - Validate interactions with dependencies
+
+## Test Structure Requirements
+
+- Use existing project testing framework and patterns
+- Follow AAA pattern: Arrange, Act, Assert
+- Write descriptive test names that explain the scenario
+- Group related tests in describe/context blocks
+- Mock external dependencies cleanly
+
+Target function: ${input:function_name:Which function or method should be tested?}
+Testing framework: ${input:framework:Which framework? (jest/vitest/mocha/pytest/rspec/etc)}
+
+## Guidelines
+
+- Generate 5-8 focused test cases covering the most important scenarios
+- Include realistic test data, not just simple examples
+- Add comments for complex test setup or assertions
+- Ensure tests are independent and can run in any order
+- Focus on testing behavior, not implementation details
+
+Create tests that give confidence the function works correctly and help catch regressions.