ef-core-configuration

Generate IEntityTypeConfiguration classes with EF Core Fluent API and snake_case naming.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/hiiamsky/multi-agent-dev-team --skill ef-core-configuration-hiiamsky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ef-core-configuration
Source: https://github.com/hiiamsky/multi-agent-dev-team/tree/main/.github/skills/dotnet-ef-core-configuration
Command: npx skills add https://github.com/hiiamsky/multi-agent-dev-team --skill ef-core-configuration-hiiamsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of EF Core configurations, ensuring that domain entities map to database tables with consistent relationships, constraints, and conventions using Fluent API.

Core Features & Use Cases

  • Generate IEntityTypeConfiguration<T> classes for each entity to keep domain clean and centralized.
  • Enforce snake_case table and column naming, relationship mappings, owned types, and index definitions across the data layer.
  • Use in code-first architectures to produce scalable, repeatable infrastructure configurations for large domain models.

Quick Start

Run the generator to create IEntityTypeConfiguration classes for all domain entities and place them under Infrastructure/Configurations.

Frequently Asked Questions about ef-core-configuration

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

FAQPage Schema
How do I auto-generate EF Core Fluent API configurations for domain entities?

You can auto-generate EF Core Fluent API configurations by using a code-generation tool to identify domain entities and create IEntityTypeConfiguration classes. These files apply snake_case naming, relationship mappings, and indexes automatically.

What is the best way to enforce snake_case naming conventions in EF Core database mappings?

Enforcing snake_case naming conventions in EF Core is best handled by generating IEntityTypeConfiguration classes. This approach centralizes table and column naming rules, ensuring consistent database mappings across your entire Infrastructure layer.

How do I map owned types and relationships using EF Core Fluent API without polluting my domain layer?

To map owned types and relationships without polluting your domain layer, generate IEntityTypeConfiguration classes and place them under Infrastructure/Configurations. This keeps data mapping logic strictly separated from your domain aggregates.

Can I use code generation to create EF Core configurations for a large code-first architecture?

Yes, code generation is ideal for large code-first architectures. It produces scalable and repeatable IEntityTypeConfiguration files for all domain entities, ensuring every table and column aligns with your project conventions.

When do I need IEntityTypeConfiguration classes for my EF Core entities?

You need IEntityTypeConfiguration classes when you want to keep domain entities clean while strictly defining database constraints, relationship mappings, and snake_case column naming across the data layer using Fluent API.