infrastructure-layer-setup

Enforce Clean Architecture rules for .NET Infrastructure layer setup.

Updated Mar 29, 2026

Search Tags:#infrastructure #dotnet #clean-architecture #dependency-injection #ef-core #domain-events #outbox-pattern

Ready to run

npx skills add https://github.com/gerardogarnica/aurora-flowboard-api --skill infrastructure-layer-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: infrastructure-layer-setup
Source: https://github.com/gerardogarnica/aurora-flowboard-api/tree/main/.claude/skills/infrastructure-layer-setup
Command: npx skills add https://github.com/gerardogarnica/aurora-flowboard-api --skill infrastructure-layer-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Infrastructure layer implementation rules and patterns for Clean Architecture in .NET applications. Defines database access, external integrations, dependency injection, and cross-cutting concerns implementation.

Core Features & Use Cases

Centralizes rules and patterns for Infrastructure layer, including EF Core integration, external service adapters, and authentication/authorization scaffolding.
Defines how to wire dependencies, configure cross-cutting concerns such as logging and caching, and implement the Outbox pattern for domain events.
Supports migration-based database configuration, snake_case naming, and isolation of business logic from persistence concerns.

Quick Start

Enforce Clean Architecture rules in the Infrastructure layer and wire up EF Core, DI, and Outbox patterns as described.

Frequently Asked Questions about infrastructure-layer-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up the Infrastructure layer in a .NET Clean Architecture project?▼

To set up the Infrastructure layer in .NET Clean Architecture, define explicit abstractions and implement database access, external service adapters, and dependency injection. This isolates persistence concerns and keeps business logic decoupled from infrastructure.

How does the Outbox pattern work with Domain Events in EF Core?▼

The Outbox pattern works with Domain Events in EF Core by storing events in a dedicated outbox table during the same database transaction as state changes. This guarantees reliable, atomic event dispatch without requiring distributed transactions.

What's the best way to configure EF Core migrations in a Clean Architecture application?▼

The best way to configure EF Core migrations cleanly is to use deterministic schema configuration with snake_case naming conventions. This approach centralizes migration logic in the Infrastructure layer, ensuring safe and testable persistence.

Where should I register dependency injection for cross-cutting concerns like logging and caching?▼

Dependency injection for cross-cutting concerns like logging and caching should be registered within the Infrastructure layer. This centralizes configuration, ensures explicit wiring, and maintains strict separation between domain logic and technical infrastructure.

Can I integrate external services without violating Clean Architecture rules in .NET?▼

Yes, you can integrate external services safely by implementing adapter classes within the Infrastructure layer that depend on explicit abstractions defined in the Application layer. This prevents external dependencies from leaking into your domain.

Why do I need explicit abstractions for database access in .NET Clean Architecture?▼

Explicit abstractions for database access are required to isolate business logic from persistence concerns. By defining clear interfaces, you ensure deterministic EF Core configuration and enable safe, testable persistence without coupling your domain to infrastructure code.