neo-dotnet-ef-core
Skill7 starsChanged 6 months agoMITView on GitHub
Use this skill when the task involves Entity Framework Core models, DbContext, migrations, LINQ queries, change tracking, database providers, performance tuning, or data access review in .NET projects.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- generate-skillSkill
- neo-azure-pipelinesSkill
- neo-clarificationSkill
- neo-clean-architectureSkill
- neo-code-reviewSkill
- neo-csharp-interface-generatorSkill
- neo-csharpSkill
- neo-dotnet-minimal-apisSkill
- neo-dotnet-mvcSkill
- neo-dotnetSkill
- neo-dotnet-tag-helperSkill
- neo-dotnet-webapiSkill
- neo-harness-projectSkill
- neo-harnessSkill
- neo-javascriptSkill
- neo-opentelemetrySkill
- neo-prSkill
- neo-python-managerSkill
- neo-pythonSkill
- neo-rabbitmqSkill
- neo-rustSkill
- neo-stop-slopSkill
- neo-sub-agentSkill
- neo-swiftSkill
- neo-swift-uiSkill
- neo-typescriptSkill
- neo-vueSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Check .csproj to identify the EF Core version and database provider.
- Distinctive: line 31
Write efficient and safe Linq queries.
- Distinctive: line 33
Create and execute database migration commands.
- Distinctive: line 35
Check if the generated SQL meets performance expectations (avoiding full table scans).
- Distinctive: line 37
Ensure all database accesses follow asynchronous patterns.
- Very specific: line 43
Bulk Operations: Use ExecuteUpdate/Delete for high-performance updates.
- Distinctive: line 48
Primitive Collections: Use simple type collections in queries.
- Distinctive: line 65
Async Always: All I/O operations must be asynchronous.
- Very specific: line 66
No-Tracking by Default: Read-only queries must always use .AsNoTracking().
- Distinctive: line 75
Ensure the provided code complies with EF Core performance best practices.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
EF Core Expert Skill
Trigger On
- The user requests database modeling, writing Linq queries, or handling database migrations.
- The project contains a
DbContextclass or references theMicrosoft.EntityFrameworkCorepackage. - There is a need to optimize database access performance or solve N+1 query problems.
- The task involves complex data relationship design (one-to-many, many-to-many, inheritance mapping).
Workflow
- Perceive (Model Awareness):
- Check
.csprojto identify the EF Core version and database provider. - Analyze
DbContextand entity configurations to confirm whether the Fluent API pattern is adopted. - Identify the current state of Migrations.
- Check
- Reason (Planning Phase):
- Evaluate whether queries need
.AsNoTracking()or.AsSplitQuery(). - Determine whether custom interceptors are needed to handle audit fields.
- Evaluate whether to use
ExecuteUpdate/Delete(.NET 7+) for massive data updates.
- Evaluate whether queries need
- Act (Execution Phase):
- Write efficient and safe Linq queries.
- Implement entity configuration classes (
IEntityTypeConfiguration). - Create and execute database migration commands.
- Validate (Standard Validation):
- Check if the generated SQL meets performance expectations (avoiding full table scans).
- Validate concurrency conflict handling logic.
- Ensure all database accesses follow asynchronous patterns.
Feature Roadmap (.NET 6 - 11)
.NET 6 & 7 (Foundation)
- Split Queries: Solve the Cartesian product problem.
- Bulk Operations: Use
ExecuteUpdate/Deletefor high-performance updates. - JSON Columns: Built-in JSON mapping support.
- Compiled Models: Reduce startup time for large models.
.NET 8 & 9 (Productivity)
- Primitive Collections: Use simple type collections in queries.
- HierarchyId: Support for SQL Server hierarchical data.
- Auto-compiled Queries: Further optimize the query compilation process.
- Complex Types: Better support for Value Objects.
.NET 10 (Interceptors & AOT)
- Advanced Interceptors: More query lifecycle hooks.
- Optimized AOT Support: AOT pre-compilation optimization for cloud-native environments.
.NET 11 (Advanced Querying & AI Vector Integration)
- Complex Types & JSON Columns in TPT/TPC: Full modeling support for complex types and JSON columns across Table-Per-Type and Table-Per-Concrete-Type hierarchies.
- LINQ Translation Enhancements:
Queryable.FullJointranslating directly to SQLFULL OUTER JOIN,NULLIFtranslation, andEF.Functions.JsonPathExists(). - Approximate Vector Search (SQL Server 2025): Native
.VectorSearch().WithApproximate()leveragingWITH APPROXIMATEvector index searches; default SQL Server compatibility level upgraded to 160 (SQL Server 2022+). - Breaking Changes Awareness:
SqlVector<T>columns returnnullby default on queries without explicit projection; Cosmos DB synchronous I/O and__jObjectshadow property removed; genericCoreTypeMapping<T>for NativeAOT.
Coding Standards
- Fluent API Preference: Prioritize entity configuration classes over Data Annotations.
- Async Always: All I/O operations must be asynchronous.
- No-Tracking by Default: Read-only queries must always use
.AsNoTracking(). - Naming: Entity names correspond to tables, foreign key names have clear semantics.
Deliver
- Optimized Linq Queries: Provide query code with the potential for high-performance SQL translation.
- Migration Scripts & Guidance: Provide correct migration commands and manual adjustment suggestions.
- Database Schema Design: Design normalized entity relationships based on business requirements.
Validate
- Ensure the provided code complies with EF Core performance best practices.
- Validate whether the code correctly handles Nulls and database constraints.
- Confirm database connection and resource release logic is correct (using
usingor Scoped DI).
Documentation
Official References
- What's new in EF Core 11
- Entity Framework Core Overview
- Performance Optimization in EF Core
- Supported Database Providers
Internal References
- EF Core Coding Style and Naming Conventions
- EF Core Anti-Patterns and Best Practices
- EF Core Modern Patterns Guide
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

