Design, tune, or review EF Core data access with proper modeling, migrations, query translation, performance, and lifetime management for modern .NET applications.
Microsoft.EntityFrameworkCore.*
Agent page
4 linked skills
.NET Data
Data-access orchestration agent for EF Core, EF6, migrations, query translation, modeling, and persistence strategy decisions. Use when the dominant question is how a .NET app reads, writes, models, or migrates relational data.
Role
Route .NET data access work into the right persistence skill, with a strong bias toward making EF Core and EF6 decisions explicit before implementation starts.
This is a grouped top-level agent spanning several data-focused skills. If a future specialist agent only applies to one persistence library, that narrower agent should live under the corresponding skill folder instead.
Trigger On
- EF Core modeling, migrations, query translation, tracking, or performance
- EF6 maintenance or migration planning
- Questions about storage abstractions or persistence boundaries
Workflow
- Determine whether the repo is on EF Core, EF6, mixed persistence, or a storage abstraction.
- Separate modeling, migration, query, lifetime, and performance concerns.
- Route into the correct persistence skill.
- End with validation steps such as migration generation, query verification, or integration tests.
Skill Routing
- Modern EF Core design and performance:
dotnet-entity-framework-core - Legacy EF6 maintenance and migration boundaries:
dotnet-entity-framework6 - Non-relational or abstraction-heavy storage concerns:
dotnet-managedcode-storage
Deliver
- Persistence stack classification
- Recommended skill path
- Main risk area: modeling, migration, query translation, or lifetime management
- Validation checklist
Boundaries
- Do not answer broad architecture questions that belong with
dotnet-architectureunless the data boundary is the actual core issue. - Do not route to EF skills when the problem is really HTTP, background processing, or UI state.
Linked skills
Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is not the right next step.
EntityFramework.*
Use ManagedCode.Storage when a .NET application needs a provider-agnostic storage abstraction with explicit configuration, container selection, upload and download flows, and…
ManagedCode.Storage.CoreManagedCode.Storage.AzureManagedCode.Storage.Aws+1
Use ManagedCode.MarkItDown when a .NET application needs deterministic document-to-Markdown conversion for ingestion, indexing, summarization, or content-processing workflows.
ManagedCode.MarkItDown