agentleFS
joaoguimaraesprojoaoguimaraespro/personal-finance/.cursor/rules/csharp-data-access.mdc

personal-finance / rules

Cursor rule1 starsChanged todayMITView on GitHub

EF Core rules: one DbContext per module, migrations per module, tenant filters, PostgreSQL specifics

The file

We split this csharp-data-access.mdc into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read paths: AsNoTracking() and projection.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule 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
csharp-data-access.mdc
---
description: "EF Core rules: one DbContext per module, migrations per module, tenant filters, PostgreSQL specifics"
globs: **/*.cs,**/Migrations/**
alwaysApply: false
---
<!-- Generated by armature from stack-dotnet/rules/csharp/data-access.md. Edit the source rule, not this file. -->
# EF Core and data access

## Contexts and migrations
- One `DbContext` per module, with its own default schema (`modelBuilder.HasDefaultSchema(...)`) and
  `ApplyConfigurationsFromAssembly`. Entity configuration lives in `IEntityTypeConfiguration<T>` classes, not
  attributes.
- Migrations are per module and generated by the tool, never written by hand:
  `dotnet ef migrations add <Name> --project <Module>.Infrastructure --startup-project <Host> --context <Module>DbContext --output-dir Database/Migrations`
  (the `dotnet-ef-migration` skill). Review `Up()` and `Down()` before committing.
- Migration names say what changed: `AddInvoiceTable`, `AddStatusToInvoice`, `RenameXToY`.
- A model change ships with its migration in the same commit. Migrations are generated code: exclude them from
  analyzers, do not reformat them.
- Production applies an idempotent SQL script (`dotnet ef migrations script --idempotent`), reviewed like code.

## Queries
- Parameterised always; `FromSqlInterpolated`/`FromSql` only with interpolation that EF parameterises, never
  `FromSqlRaw` with concatenated input.
- Read paths: `AsNoTracking()` and projection. Paginate every list; no unbounded `ToListAsync()` on user-facing
  queries. Watch for N+1 (use `Include` or projection deliberately).

## Multi-tenancy
- Tenant-scoped entities implement the repo's tenant marker and are filtered by a global query filter set in the
  base context; handlers do not hand-write tenant `Where` clauses, and never take the tenant from a request header,
  query or route when a token claim exists.
- `IgnoreQueryFilters()` only in code that must cross tenants, with a comment saying why.

## PostgreSQL (Npgsql)
- `UseSnakeCaseNamingConvention()` with `ComplexProperty(...).ToJson()` conflicts: clear the column names of the
  complex type's properties after `ToJson()`.
- `timestamptz` with `DateTimeOffset` or UTC `DateTime`; never local time.

## Packages
- Pin package versions (no floating `*`). Enable `NuGetAudit` in `Directory.Build.props`. Do not commit NuGet
  `packages.lock.json` in a cross-platform team.

<!-- Sources: ordo-api CLAUDE.md and commands/add-migration.md (migration command, output dir), NEXUS knowledge/dotnet ef-core, ef-core-json-npgsql-snake-case, nuget-lock-files-cross-platform; personal-finance-sdd constitution (migration with each database change). No ECC counterpart. -->

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.