new-endpoint
Skill234 starsChanged 3 months agoMITView on GitHub
Add an API endpoint to an existing feature controller
2 other projects use a version of this.
Adopted by
Most recently taken up by
- fleetdm/fleettheir own version, first seen Oct 8, 2026
- nada-r/agent-templatetheir own version, first seen Jul 22, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- fleetdm/fleet★ 7.2ksame name
- nada-r/agent-template★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-aspire-depSkill
- add-background-jobSkill
- add-ci-areaSkill
- add-email-templateSkill
- add-env-varSkill
- add-options-classSkill
- add-permissionSkill
- add-rate-limitSkill
- address-reviewSkill
- add-testSkill
- backend-conventionsSkill
- create-issueSkill
- create-prSkill
- create-releaseSkill
- frontend-conventionsSkill
- gen-typesSkill
- infra-conventionsSkill
- init-verifySkill
- manage-file-storageSkill
- new-entitySkill
- new-featureSkill
- new-pageSkill
- polish-uiSkill
- review-dependabotSkill
- review-designSkill
- review-prSkill
- security-conventionsSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use these as starting points - fill in the specifics from context:
- Distinctive: line 19
Check FILEMAP.md for downstream impact if modifying existing endpoints
- Very specific: line 24
Add method to Application/Features/{Feature}/I{Feature}Service.cs
- Very specific: line 27
Add mapper methods to WebApi/Features/{Feature}/{Feature}Mapper.cs
- Very specific: line 28
Add controller action - include /// <summary>, [ProducesResponseType], CancellationToken
- Distinctive: line 29
Add FluentValidation validator co-located with request DTO
- Very specific: line 30
If a string path parameter needs format validation, add a route constraint: follow the existing IRouteConstraint implementations in …
- Distinctive: line 31
Write tests: component test for service, API integration test for endpoint, validator test
- Very specific: line 35
If a new project was added that WebApi references, add its .csproj COPY line to the Dockerfile restore layer - otherwise dotnet restore …
- Distinctive: line 43
Commit type changes if applicable
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Determine: feature, operation name, HTTP method, route, request/response shape, auth requirements
- Check FILEMAP.md for downstream impact if modifying existing endpoints
Create files (match existing feature patterns - read them first):
- Application DTOs (if new):
Application/Features/{Feature}/Dtos/{Operation}Input.cs/{Entity}Output.cs - Add method to
Application/Features/{Feature}/I{Feature}Service.cs - Implement in
Infrastructure/Features/{Feature}/Services/{Feature}Service.cs - WebApi request/response DTOs (if new):
WebApi/Features/{Feature}/Dtos/{Operation}/ - Add mapper methods to
WebApi/Features/{Feature}/{Feature}Mapper.cs - Add controller action - include
/// <summary>,[ProducesResponseType],CancellationToken - Add FluentValidation validator co-located with request DTO
- If a string path parameter needs format validation, add a route constraint: follow the existing
IRouteConstraintimplementations insrc/backend/MyProject.WebApi/Routing/and register inProgram.cs(options.ConstraintMap)
- If a string path parameter needs format validation, add a route constraint: follow the existing
- Write tests: component test for service, API integration test for endpoint, validator test
Dockerfile:
- If a new project was added that WebApi references, add its
.csprojCOPY line to the Dockerfile restore layer - otherwisedotnet restorefails in Docker builds.
Verify and commit:
dotnet build src/backend/MyProject.slnx- fix errors, loop until greendotnet test src/backend/MyProject.slnx -c Release- fix failures, loop until green- Commit:
feat({feature}): add {operation} endpoint - Regenerate frontend types:
cd src/frontend && pnpm run api:generate- fix any type errors - Commit type changes if applicable
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.