2 api_endpoint_creation {{task}} {{context}} {{#each requirements}} {{this}} {{/each}} {{allowed_libraries}} {{forbidden_approaches}} {{complexity_limits}} {{integration_requirements}} {{http_method}} {{endpoint_path}} {{auth_required}} {{request_format}} {{response_format}} REQUIRED - Tests MUST be written before implementation {{test_framework}} {{coverage_minimum}} - Test success scenario (200/201) - Test validation errors (400) - Test authentication errors (401) - Test authorization errors (403) - Test not found (404) - Test conflict (409) - Test server errors (500) Route Definition Express/Koa/Fastify route registration JavaScript/TypeScript route file YES Controller/Handler Request handling logic JavaScript/TypeScript controller YES Input Validation Request schema validation Joi/Yup/Zod schema or middleware YES Service Layer Business logic (if complex) JavaScript/TypeScript service Conditional Tests Comprehensive test suite (written FIRST) Test file with 10+ test cases YES Error Handler Error handling middleware Middleware function YES Before creating API endpoint: 1. UNDERSTAND THE REQUIREMENT: - What is the endpoint's purpose? - What HTTP method is appropriate? - What is the resource path? - What are the success/error scenarios? 2. DESIGN THE INTERFACE: - What request parameters are needed? - What does the request body look like? - What does the response body look like? - What status codes should be returned? 3. PLAN VALIDATION: - What inputs are required? - What validations are needed? - How are validation errors returned? 4. PLAN AUTHENTICATION/AUTHORIZATION: - Is authentication required? - What authorization checks are needed? - How are auth errors handled? 5. DESIGN TESTS (TDD - RED PHASE): - Test successful request with valid data - Test validation errors for each field - Test authentication failures - Test authorization failures - Test not found scenarios - Test conflict scenarios - Test server error handling 6. IMPLEMENT MINIMALLY (TDD - GREEN PHASE): - Write just enough code to pass tests - Don't add features not tested - Keep it simple 7. REFACTOR (TDD - REFACTOR PHASE): - Extract business logic to service if needed - Improve error handling - Add meaningful error messages - Keep tests passing CRITICAL TDD RULES: - Tests MUST be written first - Every test must fail initially (RED) - Implementation MUST be minimal to pass (GREEN) - Refactor ONLY while tests pass - NO skipping TDD phases {{#if existing_code}} Existing route/controller to extend {{existing_code}} {{/if}} {{#if example}} Reference endpoint implementation {{example}} {{/if}} Tests written before implementation (TDD) Tests fail initially (RED phase confirmed) Route registered correctly Input validation implemented Authentication/authorization checked Success response returns correct data Error responses have appropriate status codes Error responses have descriptive messages Implementation is minimal (no over-engineering) All tests passing (GREEN phase achieved) Code refactored for clarity (REFACTOR phase) Tests still passing after refactor No code duplication Single responsibility principle Consistent with existing API patterns