.claude/skills/gen-middleware/SKILL.md
Use when adding custom middleware to an ASP.NET Core pipeline. Generates a middleware class for a single cross-cutting concern (e.g., request logging, correlation ID, tenant resolution) and an IApplicationBuilder extension method. Also invoke when the user mentions: custom middleware, pipeline middleware, request middleware, ASP.NET middleware class. Domain: Code Generation, Infrastructure. Level: Intermediate.
npx skillsauth add klod68/littlerae gen-middlewareInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate an ASP.NET Core middleware for the ${1:ConcernName} concern.
${2:MyApp}${3:Brief description of what the middleware should do}${4:Before or after which existing middleware}${2}.Middleware.${1}Middleware.cs
/// <summary>
/// Middleware that handles ${1:concern} for all HTTP requests.
/// </summary>
public sealed class ${1}Middleware
{
private readonly RequestDelegate _next;
private readonly ILogger<${1}Middleware> _logger;
public ${1}Middleware(RequestDelegate next, ILogger<${1}Middleware> logger)
{
ArgumentNullException.ThrowIfNull(next);
ArgumentNullException.ThrowIfNull(logger);
_next = next;
_logger = logger;
}
public async Task InvokeAsync(HttpContext context)
{
// PRE-processing (before next middleware)
// ...
await _next(context);
// POST-processing (after next middleware)
// ...
}
}
${2}.Middleware.${1}MiddlewareExtensions.cs
/// <summary>
/// Registers the <see cref="${1}Middleware"/> in the application pipeline.
/// </summary>
public static class ${1}MiddlewareExtensions
{
public static IApplicationBuilder Use${1}(this IApplicationBuilder builder)
{
ArgumentNullException.ThrowIfNull(builder);
return builder.UseMiddleware<${1}Middleware>();
}
}
${2}.Configuration.${1}Options.cs
EnsureValid() methodConfigure<${1}Options>public sealed — one concern per middlewareRequestDelegate next as first parameter, then DI servicesInvokeAsync (not Invoke) — always asyncUse${1} on IApplicationBuilderILogger<T> for logging — never Console.WriteLineHttpContext.RequestServices (not constructor)tools
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.
development
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.
development
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.
development
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.