ln-770-crosscutting-setup

To bootstrap cross-cutting concerns, this skill detects your stack and checks existing configuration, then invokes unconfigured workers to generate a unified entry point like ServiceExtensions.cs or Python middleware init. It produces a summary report of the setup.

The best way to configure cross-cutting concerns consistently is using a phase-driven detection and validation process that generates a unified aggregation entry point. This approach ensures logging and error handling are standardized across .NET and Python services.

Yes, you can run cross-cutting setup multiple times safely because the process is idempotent. It skips already configured concerns like logging or CORS and only bootstraps workers for missing settings, preventing duplicate configuration entries.

Cross-cutting bootstrap works with both .NET and Python frameworks by detecting the stack from the Context Store. It generates .NET Extensions ServiceExtensions.cs or Python middleware __init__.py depending on the detected framework and project root.

Cross-cutting concerns covered when bootstrapping project settings include logging, error handling, CORS, health checks, and API docs. The setup coordinates these concerns by delegating to specialized workers that configure each missing element.

You need a unified entry point for cross-cutting concerns because settings like logging and CORS are often duplicated across services. Generating a single ServiceExtensions.cs or middleware init file aggregates configuration, ensuring consistent setup and reducing maintenance overhead.