How do I install the Add Endpoint skill?

Run npx skillmds@latest add atherio-danp/add-endpoint in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Add Endpoint safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Add Endpoint?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Add Endpoint free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Add Endpoint?

atherio-danp (@atherio-danp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Add Endpoint by atherio-danp — Agent Skill

Name: Add Endpoint
Author: atherio-danp

Add Endpoint

Add a Minimal API endpoint (a feature/use case) to the .NET API — feature folder, IEndpoint self-registration, contract validation, Kommand dispatch, Result→ProblemDetails. Use when adding or changing an HTTP endpoint under apps/api/{{ProjectName}}.Api.

atherio-danp 5b08c9c 2.8 KB Updated Sep 17, 2026

File contents

Serena MCP is mandatory for C# code. First call mcp__serena__initial_instructions to load the Serena tool manual, then use the Serena tools for ALL .cs reading / searching / navigation / creation / editing — prefer symbol navigation (get_symbols_overview / find_symbol / find_referencing_symbols) over whole-file reads. Native Edit/Write on .cs is hook-blocked (the TS/React frontend uses the native tools).

Add a Minimal API endpoint

The procedure for our thin, feature-sliced API layer. Source of truth (the facts — read them): .claude/rules/backend/api-design.md, result-and-errors.md, cqrs-kommand.md. C# (.cs) edits go through Serena (native Edit/Write on .cs is blocked).

Steps

Feature folder, single file. Create {{ProjectName}}.Api/Features/<Feature>/<UseCase>.cs holding the endpoint + request record + response record together (REPR style — one file per use case).
Implement IEndpoint — void MapEndpoint(IEndpointRouteBuilder app) mapping the verb under a MapGroup for the feature (.WithTags("<Feature>")). The endpoint auto-registers via the reflection scan (AddEndpoints/MapEndpoints in Program.cs) — do not edit Program.cs to add a route.
Contract validation only — bind the request; validate shape/required fields and authz inferable from HttpContext.User (JWT/cookie). No database calls here. (Business validation → the Kommand IValidator; invariants → the domain.)
Dispatch Kommand — build the command/query and await mediator.SendAsync(...) (command) or QueryAsync(...) (query). Inject IMediator only. The command/query + handler live in the Application layer — author them with the cqrs-kommand skill (and mirror the feature folder there).
Map the result — the handler returns Result<T>; convert with the ToHttpResult/ToProblem extension (TypedResults). Every failure → RFC 9457 ProblemDetails. Success uses the right typed result (TypedResults.Created(...)/Ok(...)).
Build — dotnet build (warnings = errors); fix before returning.

Conventions (restated)

No business logic, persistence, or model routing in the endpoint — it binds, validates the contract, dispatches.
Records for request/response/command/query; rich classes for entities.
No new library (e.g. FastEndpoints/FluentValidation) — hand-rolled Minimal API only, per the no-library rule.
Tests for the endpoint go through the write-tests skill, per the plan's exact test list.

---name: add-endpointdescription: Add a Minimal API endpoint (a feature/use case) to the .NET API — feature folder, IEndpoint self-registration, contract validation, Kommand dispatch, Result→ProblemDetails. Use when adding or changing an HTTP endpoint under apps/api/{{ProjectName}}.Api.---> **Serena MCP is mandatory for C# code.** First call `mcp__serena__initial_instructions` to load the Serena tool manual, then use the Serena tools for ALL `.cs` reading / searching / navigation / creation / editing — prefer symbol navigation (`get_symbols_overview` / `find_symbol` / `find_referencing_symbols`) over whole-file reads. Native `Edit`/`Write` on `.cs` is hook-blocked (the TS/React frontend uses the native tools).# Add a Minimal API endpointThe procedure for our thin, feature-sliced API layer. Source of truth (the *facts* — read them):`.claude/rules/backend/api-design.md`, `result-and-errors.md`, `cqrs-kommand.md`. C# (`.cs`) edits go through**Serena** (native Edit/Write on `.cs` is blocked).## Steps1. **Feature folder, single file.** Create `{{ProjectName}}.Api/Features/<Feature>/<UseCase>.cs` holding the **endpoint + request record + response record together** (REPR style — one file per use case).2. **Implement `IEndpoint`** — `void MapEndpoint(IEndpointRouteBuilder app)` mapping the verb under a `MapGroup` for the feature (`.WithTags("<Feature>")`). The endpoint **auto-registers** via the reflection scan (`AddEndpoints`/`MapEndpoints` in `Program.cs`) — **do not edit `Program.cs`** to add a route.3. **Contract validation only** — bind the request; validate shape/required fields and authz inferable from `HttpContext.User` (JWT/cookie). **No database calls here.** (Business validation → the Kommand `IValidator`; invariants → the domain.)4. **Dispatch Kommand** — build the command/query and `await mediator.SendAsync(...)` (command) or `QueryAsync(...)` (query). Inject `IMediator` only. The command/query + handler live in the **Application** layer — author them with the **`cqrs-kommand`** skill (and mirror the feature folder there).5. **Map the result** — the handler returns `Result<T>`; convert with the `ToHttpResult`/`ToProblem` extension (`TypedResults`). **Every failure → RFC 9457 ProblemDetails.** Success uses the right typed result (`TypedResults.Created(...)`/`Ok(...)`).6. **Build** — `dotnet build` (warnings = errors); fix before returning.## Conventions (restated)- No business logic, persistence, or model routing in the endpoint — it binds, validates the contract, dispatches.- Records for request/response/command/query; rich classes for entities.- No new library (e.g. FastEndpoints/FluentValidation) — hand-rolled Minimal API only, per the no-library rule.- Tests for the endpoint go through the **`write-tests`** skill, per the plan's exact test list.

Frequently asked questions