メニュー
Scaffold a complete FastEndpoints endpoint for the Grants Applicant Portal backend — creates the endpoint class, request, response, and validator files, then registers it within the domain folder.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | new-endpoint |
| description | Scaffold a complete FastEndpoints endpoint for the Grants Applicant Portal backend — creates the endpoint class, request, response, and validator files, then registers it within the domain folder. |
Scaffold a complete FastEndpoints endpoint for the Grants Applicant Portal backend.
Arguments (space-separated): <Domain> <Action>
Examples: Addresses Create, Contacts Update, Payments Retrieve
If $ARGUMENTS is empty, ask the user for the domain and action before doing anything else.
Read an existing endpoint for patterns — read a comparable endpoint in src/Grants.ApplicantPortal.API.Web/<Domain>/. For example, read Addresses/Create.cs and Addresses/Create.Request.cs to understand constructor injection, Configure() structure, result mapping, and naming conventions before writing anything.
Determine the domain folder — the endpoint files go in src/Grants.ApplicantPortal.API.Web/<Domain>/. Create the folder if it does not exist.
Create four files following the existing pattern:
<Action>.cs — endpoint class:
<Action> in namespace Grants.ApplicantPortal.API.Web.<Domain>IMediator _mediatorEndpoint<<Action>Request, <Action>Response>Configure(): sets HTTP verb + route from <Action>Request.Route, applies Policies(AuthPolicies.RequireAuthenticatedUser), adds Summary(...) with response codes 200/201, 400, 401, 403, 404, 422HandleAsync(): calls _mediator.Send() with a new Command/Query, then maps Result<T> to HTTP responses using the standard result-mapping pattern (IsSuccess → return value; NotFound → SendNotFoundAsync; Forbidden → SendForbiddenAsync; Invalid → AddError + SendErrorsAsync(422); Errors → SendErrorsAsync(400))<Action>.Request.cs — request record:
public const string Route = "/api/v1/<domain-plural>/<path>";required or nullable strings/Guids matching the use case<Action>.Response.cs — response record:
<Action>.Validator.cs — FluentValidation validator:
AbstractValidator<<Action>Request>RuleFor rules: NotEmpty for required fields, MaximumLength where applicableAsk whether to also scaffold the use case — if no matching UseCases/<Domain>/<Action>/ folder exists, ask if the user also wants to run /new-use-case for it.
Report — list every file created with its full path and show the route that was registered.
Policies(AuthPolicies.RequireAuthenticatedUser) in Configure()_mediator.Send()/api/v1/<plural-domain> for collections, /api/v1/<plural-domain>/{id} for single resourcesDiagnose and fix a bug in the Grants Applicant Portal — takes a bug report or stack trace, locates the root cause, implements a targeted fix, and verifies with tests.
End-to-end ticket implementation for the Grants Applicant Portal — parses ticket details, architects a solution across frontend and/or backend, implements using specialist sub-agents in parallel, runs tests, and produces a PR-ready summary.
New developer orientation for the Grants Applicant Portal — tours the codebase, explains key architecture patterns, answers "how do I..." questions, and produces a personalised cheat sheet.
Refactor a component, service, or domain area in the Grants Applicant Portal — understands existing code, plans changes, implements via specialist sub-agents, and verifies nothing broke.
Full PR review for the Grants Applicant Portal — runs security, architecture/conventions, and test coverage reviews in parallel and produces a structured report ready to paste into GitHub.
Create a new Entity Framework Core migration for the Grants Applicant Portal backend — runs dotnet ef migrations add, then summarises the generated Up/Down SQL.