agentleFS
BenknightdarkBenknightdark/neo-skills/skills/neo-dotnet-ef-core/SKILL.md

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.

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
  1. Very specific:

    Check .csproj to identify the EF Core version and database provider.

    line 23
  2. Distinctive:

    Write efficient and safe Linq queries.

    line 31
  3. Distinctive:

    Create and execute database migration commands.

    line 33
  4. Distinctive:

    Check if the generated SQL meets performance expectations (avoiding full table scans).

    line 35
  5. Distinctive:

    Ensure all database accesses follow asynchronous patterns.

    line 37
  6. Very specific:

    Bulk Operations: Use ExecuteUpdate/Delete for high-performance updates.

    line 43
  7. Distinctive:

    Primitive Collections: Use simple type collections in queries.

    line 48
  8. Distinctive:

    Async Always: All I/O operations must be asynchronous.

    line 65
  9. Very specific:

    No-Tracking by Default: Read-only queries must always use .AsNoTracking().

    line 66
  10. Distinctive:

    Ensure the provided code complies with EF Core performance best practices.

    line 75

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

EF Core Expert Skill

Trigger On

  • The user requests database modeling, writing Linq queries, or handling database migrations.
  • The project contains a DbContext class or references the Microsoft.EntityFrameworkCore package.
  • 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

  1. Perceive (Model Awareness):
    • Check .csproj to identify the EF Core version and database provider.
    • Analyze DbContext and entity configurations to confirm whether the Fluent API pattern is adopted.
    • Identify the current state of Migrations.
  2. 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.
  3. Act (Execution Phase):
    • Write efficient and safe Linq queries.
    • Implement entity configuration classes (IEntityTypeConfiguration).
    • Create and execute database migration commands.
  4. 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/Delete for 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.FullJoin translating directly to SQL FULL OUTER JOIN, NULLIF translation, and EF.Functions.JsonPathExists().
  • Approximate Vector Search (SQL Server 2025): Native .VectorSearch().WithApproximate() leveraging WITH APPROXIMATE vector index searches; default SQL Server compatibility level upgraded to 160 (SQL Server 2022+).
  • Breaking Changes Awareness: SqlVector<T> columns return null by default on queries without explicit projection; Cosmos DB synchronous I/O and __jObject shadow property removed; generic CoreTypeMapping<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 using or Scoped DI).

Documentation

Official References

Internal References

  • EF Core Coding Style and Naming Conventions
  • EF Core Anti-Patterns and Best Practices
  • EF Core Modern Patterns Guide

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.