.claude/skills/ln-770-crosscutting-setup/SKILL.md
Coordinates logging, error handling, CORS, health checks, and API docs
npx skillsauth add cbbkrd-tech/jl-finishes ln-770-crosscutting-setupInstall 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.
Paths: File paths (
shared/,references/,../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.
Type: L2 Domain Coordinator Category: 7XX Project Bootstrap Parent: ln-700-project-bootstrap
Coordinates cross-cutting concerns configuration for .NET and Python projects.
| Aspect | Details | |--------|---------| | Input | Project root directory | | Output | Configured logging, error handling, CORS, health checks, API docs | | Workers | ln-771 to ln-775 | | Stacks | .NET (ASP.NET Core), Python (FastAPI) |
Determine the technology stack by scanning project files.
Detection Rules:
| File Pattern | Stack | Framework |
|--------------|-------|-----------|
| *.csproj | .NET | ASP.NET Core |
| pyproject.toml or requirements.txt + FastAPI | Python | FastAPI |
Actions:
*.csproj filespyproject.toml or requirements.txtContext Store Initial:
{
"STACK": ".NET" | "Python",
"FRAMEWORK": "ASP.NET Core" | "FastAPI",
"PROJECT_ROOT": "/path/to/project",
"FRAMEWORK_VERSION": "8.0" | "0.109.0"
}
Scan for already configured cross-cutting concerns.
Detection Patterns:
| Concern | .NET Pattern | Python Pattern |
|---------|--------------|----------------|
| Logging | Serilog in *.csproj, UseSerilog in Program.cs | structlog in requirements, logging config |
| Error Handling | GlobalExceptionMiddleware, UseExceptionHandler | @app.exception_handler, exception_handlers.py |
| CORS | AddCors, UseCors | CORSMiddleware |
| Health Checks | AddHealthChecks, MapHealthChecks | /health routes |
| API Docs | AddSwaggerGen, UseSwagger | FastAPI auto-generates |
Actions:
skip: trueContext Store Updated:
{
"concerns": {
"logging": { "configured": false },
"errorHandling": { "configured": false },
"cors": { "configured": true, "skip": true },
"healthChecks": { "configured": false },
"apiDocs": { "configured": false }
}
}
Delegate to workers only for unconfigured concerns.
Worker Invocation Order:
| Order | Worker | Condition | Skill Call |
|-------|--------|-----------|------------|
| 1 | ln-771-logging-configurator | logging.configured == false | /skill ln-771-logging-configurator |
| 2 | ln-772-error-handler-setup | errorHandling.configured == false | /skill ln-772-error-handler-setup |
| 3 | ln-773-cors-configurator | cors.configured == false | /skill ln-773-cors-configurator |
| 4 | ln-774-healthcheck-setup | healthChecks.configured == false | /skill ln-774-healthcheck-setup |
| 5 | ln-775-api-docs-generator | apiDocs.configured == false | /skill ln-775-api-docs-generator |
Pass Context Store to each worker.
Worker Response Format:
{
"status": "success" | "skipped" | "error",
"files_created": ["path/to/file.cs"],
"packages_added": ["Serilog.AspNetCore"],
"message": "Configured structured logging with Serilog"
}
Create a single entry point for all cross-cutting services.
Generate based on configured workers:
// Structure only - actual code generated via MCP ref
public static class ServiceExtensions
{
public static IServiceCollection AddCrosscuttingServices(
this IServiceCollection services,
IConfiguration configuration)
{
// Calls added based on configured workers:
// services.AddLogging(configuration); // if ln-771 ran
// services.AddCorsPolicy(configuration); // if ln-773 ran
// services.AddHealthChecks(); // if ln-774 ran
// services.AddSwaggerServices(); // if ln-775 ran
return services;
}
}
Generate based on configured workers:
# Structure only - actual code generated via MCP ref
def configure_middleware(app):
# Middleware added based on configured workers:
# configure_logging(app) # if ln-771 ran
# configure_error_handlers(app) # if ln-772 ran
# configure_cors(app) # if ln-773 ran
# configure_health_routes(app) # if ln-774 ran
pass
Display summary of all configured concerns.
Output Format:
Cross-cutting Setup Complete
============================
Stack: .NET (ASP.NET Core 8.0)
Configured:
✓ Logging (Serilog) - Extensions/LoggingExtensions.cs
✓ Error Handling - Middleware/GlobalExceptionMiddleware.cs
✓ CORS - Extensions/CorsExtensions.cs
✓ Health Checks - Extensions/HealthCheckExtensions.cs
✓ API Docs (Swagger) - Extensions/SwaggerExtensions.cs
Skipped (already configured):
- None
Entry Point: Extensions/ServiceExtensions.cs
Add to Program.cs: builder.Services.AddCrosscuttingServices(builder.Configuration);
Packages to Install:
dotnet add package Serilog.AspNetCore
dotnet add package Swashbuckle.AspNetCore
| Worker | Purpose | Stacks | |--------|---------|--------| | ln-771-logging-configurator | Structured logging | .NET (Serilog), Python (structlog) | | ln-772-error-handler-setup | Global exception middleware | .NET, Python | | ln-773-cors-configurator | CORS policy configuration | .NET, Python | | ln-774-healthcheck-setup | /health endpoints | .NET, Python | | ln-775-api-docs-generator | Swagger/OpenAPI | .NET (Swashbuckle), Python (FastAPI built-in) |
Workers receive and return via Context Store:
Input to Workers:
{
"STACK": ".NET",
"FRAMEWORK": "ASP.NET Core",
"FRAMEWORK_VERSION": "8.0",
"PROJECT_ROOT": "/path/to/project",
"ENVIRONMENT": "Development"
}
Output from Workers:
{
"status": "success",
"files_created": [],
"packages_added": [],
"registration_code": "services.AddLogging(configuration);"
}
This skill is idempotent:
skip: true)STACK, FRAMEWORK, PROJECT_ROOT*.csproj or pyproject.toml/requirements.txt + FastAPIServiceExtensions.cs or middleware/__init__.py)ln-771-logging-configurator/SKILL.md through ln-775-api-docs-generator/SKILL.mdVersion: 2.0.0 Last Updated: 2026-01-10
testing
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
development
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
development
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences.
development
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' or 'involuntary churn.' This skill covers voluntary churn (cancel flows, save offers, exit surveys) and involuntary churn (dunning, payment recovery). For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.