klod68/gen-minimal-api-endpoint
.claude/skills/gen-minimal-api-endpoint/SKILL.md
Use when scaffolding a new Minimal API endpoint or route group. Generates request/response records, FluentValidation validators, and handler wiring following the one-concern-per-group rule. Also invoke when the user mentions: new endpoint, new route, minimal API, MapGroup, add HTTP endpoint. Domain: Code Generation, API. Level: Intermediate.
$ install --global
skillsauthnpx skillsauth add klod68/littlerae gen-minimal-api-endpointInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 2:07 AM39.5s1 file scanned
SKILL.md
name: gen-minimal-api-endpoint description: "Use when scaffolding a new Minimal API endpoint or route group. Generates request/response records, FluentValidation validators, and handler wiring following the one-concern-per-group rule. Also invoke when the user mentions: new endpoint, new route, minimal API, MapGroup, add HTTP endpoint. Domain: Code Generation, API. Level: Intermediate."
Generate a Minimal API endpoint group for resource: ${1:ResourceName}.
Context
- Namespace root:
${2:MyApp} - HTTP methods needed:
${3|GET,POST,PUT,DELETE,GET+POST,GET+POST+PUT+DELETE|} - Application handler class:
${4:ResourceNameHandler}(already exists — wire to it) - Route prefix:
${5:/api/resource-name} - Auth policy:
${6:RequireAuthorization("PolicyName") or AllowAnonymous}
Required output — generate ALL of the following:
1. Endpoint definition class
${2}.Api.Endpoints.${1}Endpoints.cs
internal sealedclass implementingIEndpointDefinition(or equivalent extension method pattern used in this codebase).MapGroup("${5}")with explicit${6}.- One method per HTTP verb — delegate delegates immediately to handler, no inline logic.
- Returns typed
IResultusingResults<T1, T2>union for OpenAPI correctness.
2. Request records (one per verb with a body)
${2}.Api.Endpoints.Models.${1}{Verb}Request.cs
- Sealed records,
init-only properties. [AsParameters]for route/query; body param typed separately.
3. Response records
${2}.Api.Endpoints.Models.${1}Response.cs
- Sealed record,
init-only properties. - Include only what the client needs — no internal or domain fields.
4. FluentValidation validators (one per request record)
${2}.Api.Validators.${1}{Verb}RequestValidator.cs
internal sealedclass extendingAbstractValidator<T>.- Validate every property with a meaningful message.
5. DI & route registration
Show where to call the endpoint definition registration in Program.cs or the app's IEndpointDefinition scan.
HTTP conventions
POST→201 Created+Results.CreatedAtRoutePUT/PATCH→204 No ContentDELETE→204 No Contentor404 Not FoundGET(collection) →200 OKwith paged resultGET(single) →200 OKor404 Not Found- All errors →
Results.Problem(RFC 7807)
Constraints
- Follow all rules in the workspace root instruction file and
ef-core.instructions.mdif applicable. - No business logic in endpoint delegates.
- No domain entities or EF types in request/response models.
- Every endpoint has an explicit auth declaration.
Related Skills
klod68/interceptor-pipeline
tools
VerifiedTrustedCommunity
Use when cross-cutting concerns (logging, metrics, validation, authorization) are tangled into command handlers or service methods, when building database command pipelines with reorderable concerns, or when HTTP client pipelines or message handlers need composable, independently-replaceable processing stages. Covers ICommandInterceptor interface, InterceptorPipeline with reverse-chain construction, zero-cost Empty sentinel to skip overhead when no interceptors are registered, and ConfigureAwait(false) discipline for library code. Domain: Architecture, Cross-Cutting Concerns. Level: Intermediate. Tags: interceptor, pipeline, middleware, decorator, cross-cutting-concerns.
1SKILL.mdUpdated Apr 17, 2026
klod68/integration-testing-webapplicationfactory
development
VerifiedTrustedCommunity
Use when writing integration tests for Razor Pages, MVC, or Minimal API applications to validate routing, middleware, page rendering, and HTTP behavior without a browser or live server, or when adding fast smoke tests to a CI pipeline. Covers WebApplicationFactory<Program> setup with public partial class Program, in-memory test server, AngleSharp HTML parsing, CSS selector assertions, redirect and status code testing, and a shared static fixture pattern for minimal per-test startup overhead. Domain: Testing, ASP.NET Core. Level: Intermediate. Tags: integration-testing, webapplicationfactory, razor-pages, anglesharp, http-testing.
1SKILL.mdUpdated Apr 17, 2026
klod68/index-design-strategy
development
VerifiedTrustedCommunity
Use when designing indexes for new tables, diagnosing slow queries that are not using indexes efficiently, reviewing index fragmentation and maintenance, or when the current indexing strategy results in key lookups, table scans, or missing index warnings. Covers clustered index key selection (narrow, unique, ever-increasing), non-clustered index design for query patterns, covering indexes with INCLUDE columns, filtered indexes for subset queries, composite index column ordering, DMV-based monitoring for missing and unused indexes, and rebuild vs reorganize maintenance thresholds. Domain: Database, Performance. Level: Intermediate. Tags: index, sql-server, covering-index, filtered-index, performance, dmv, maintenance.
1SKILL.mdUpdated Apr 17, 2026
klod68/in-memory-search-registry
development
VerifiedTrustedCommunity
Use when building a searchable in-memory catalog or registry for documentation sites, admin panels, or type/API browsers where you need keyword matching, fuzzy search, and ranked results without an external search engine or database. Covers RegistryService with weighted scoring across name, description, keywords, and method names; Levenshtein fuzzy matching; synonym expansion; category and subcategory filtering; and singleton DI registration for datasets of hundreds to low thousands of items. Domain: Search, Data Access Patterns. Level: Intermediate. Tags: search, registry, fuzzy-matching, in-memory, catalog, filtering.
1SKILL.mdUpdated Apr 17, 2026