Apply Entity Framework Core best practices for DbContext configuration, queries, and migrations.
npx skills add https://github.com/shahdanish/vibepos --skill ef-core-shahdanish
Please help me install this Agent Skill. Skill: ef-core Source: https://github.com/shahdanish/vibepos/tree/main/skills/ef-core Command: npx skills add https://github.com/shahdanish/vibepos --skill ef-core-shahdanish
This Skill helps you build reliable, high-performance data access with Entity Framework Core by preventing common pitfalls that lead to slow queries, excessive loading, and fragile migrations.
IEntityTypeConfiguration<T> and ApplyConfigurationsFromAssembly to keep mappings maintainable and discoverable.Select to DTOs) to avoid over-fetching and N+1 problems, plus pagination patterns for scalable list endpoints.ExecuteUpdateAsync/ExecuteDeleteAsync, interceptors for audit/soft-delete concerns, compiled queries for hot paths, value converters for strongly-typed IDs/enums, and global query filters to enforce invariants.Use Case Example: You are building a sales/reporting screen for a POS system and need a list of orders with item summaries without loading full entities or suffering N+1 queries; you also want bulk status updates and safe schema changes across environments.
Ask the AI to show an EF Core DbContext setup with IEntityTypeConfiguration, then write a projected LINQ query with pagination that avoids N+1 and prepares a migration command workflow.
High-intent search queries and answers about installing and using this skill.
Prevent EF Core N+1 queries by using projection-based querying with `Select` to map entities directly into DTOs. This approach avoids loading full entities and ensures only necessary data is retrieved.
The best way to handle bulk updates and deletes in EF Core is using `ExecuteUpdateAsync` and `ExecuteDeleteAsync`. These methods perform operations directly in the database, bypassing entity tracking overhead for better performance.
Configure DbContext for maintainable mappings by applying `IEntityTypeConfiguration<T>` classes and registering them with `ApplyConfigurationsFromAssembly`. This keeps entity mapping logic discoverable and separated from the DbContext setup.
Use compiled queries in EF Core for hot-path querying scenarios where the same LINQ query executes repeatedly. They improve performance by caching the query translation, reducing the overhead of parsing and compiling on each run.
Manage EF Core migrations safely by treating them as code: review generated SQL before applying, test locally, and generate idempotent SQL for production. Avoid auto-migrating in production to prevent fragile schema changes.
Yes, you can implement audit logging and soft deletes using EF Core interceptors. Interceptors allow you to hook into data access operations to automatically populate audit fields or apply global query filters for excluded records.
microsoftMigrate LINQ to SQL data access layers to Entity Framework Core.
CaptainPhantasyGenerates Up/Down SQL migration scripts for schema changes.
belokonmGuide ASP.NET Core API and EF Core development with C# 12 and .NET 8.
FaysilAlshareefWrite read-optimized SQL queries with Dapper and EF Core.