new-endpoint

Adds an API endpoint to an existing feature.

Infers the feature, operation, HTTP method, route, shapes, and auth from context. Asks only if multiple valid approaches exist and the tradeoffs matter.

Templates

Use these as starting points - fill in the specifics from context:

• Controller action template
• Validator template

Steps

1. Determine: feature, operation name, HTTP method, route, request/response shape, auth requirements
2. Check FILEMAP.md for downstream impact if modifying existing endpoints

Create files (match existing feature patterns - read them first):

1. Application DTOs (if new): Application/Features/{Feature}/Dtos/{Operation}Input.cs / {Entity}Output.cs
2. Add method to Application/Features/{Feature}/I{Feature}Service.cs
3. Implement in Infrastructure/Features/{Feature}/Services/{Feature}Service.cs
4. WebApi request/response DTOs (if new): WebApi/Features/{Feature}/Dtos/{Operation}/
5. Add mapper methods to WebApi/Features/{Feature}/{Feature}Mapper.cs
6. Add controller action - include /// <summary>, [ProducesResponseType], CancellationToken
7. Add FluentValidation validator co-located with request DTO
   • If a string path parameter needs format validation, add a route constraint: follow the existing IRouteConstraint implementations in src/backend/MyProject.WebApi/Routing/ and register in Program.cs (options.ConstraintMap)
8. Write tests: component test for service, API integration test for endpoint, validator test

Dockerfile:

1. If a new project was added that WebApi references, add its .csproj COPY line to the Dockerfile restore layer - otherwise dotnet restore fails in Docker builds.

Verify and commit:

1. dotnet build src/backend/MyProject.slnx - fix errors, loop until green
2. dotnet test src/backend/MyProject.slnx -c Release - fix failures, loop until green
3. Commit: feat({feature}): add {operation} endpoint
4. Regenerate frontend types: cd src/frontend && pnpm run api:generate - fix any type errors
5. Commit type changes if applicable