lens-aspnet-structure

What problem does it solve?

LENS ASP.NET Core services require strict adherence to a 5-layer architecture with unidirectional dependencies, specific design patterns (handler, repository, DI registration), and anti-pattern avoidance to maintain governance compliance, reduce technical debt, and ensure consistent, maintainable codebases. Without enforced standards, teams introduce layer violations, business logic in incorrect layers, and inconsistent wiring that creates fragile, hard-to-debug services.

Core Features & Use Cases

• Layer Boundary Enforcement: Validates and scaffolds the canonical 5-layer LENS structure (API, BusinessLogic, DataAccess, Common, DependencyInjection) with strict dependency rules, preventing layer skipping and circular references.
• Pattern Compliance & Anti-Pattern Detection: Identifies violations like business logic in controllers, missing handler patterns, incorrect DI registration, and infrastructure exceptions leaking across layer boundaries, with explicit fixes for each issue.
• Migration Planning: Generates phased, minimum-disruption remediation plans for existing non-compliant LENS services, prioritizing structural fixes before code quality improvements to avoid wasted refactoring work.
• Use Case Example: A team onboarding to the LENS governance model can use this skill to scaffold a new service with correct project structure and wiring from day one, while a team maintaining a legacy LENS service can use it to audit all architectural violations and produce a step-by-step fix plan aligned with LENS standards.

Quick Start

Invoke the lens-aspnet-structure skill to analyze your LENS ASP.NET Core service codebase, identify all architectural violations, and generate a phased migration plan to align with LENS structure standards.