Backend · Cursor
.NET 10 & C# 14 Minimal APIs .cursorignore
A .cursorignore for .NET 10 & C# 14 Minimal APIs that keeps build output, large files and secrets out of Cursor's index (best effort).
- Path
- .cursorignore
- Loads
- Indexing and AI features
- Format
- gitignore syntax
- Used by
- Cursor
What this file tells the agent
This .cursorignore keeps .NET 10 & C# 14 Minimal APIs build output, large data files and environment secrets out of Cursor's index and AI features, so context goes to your source code. It is best effort: commands the agent runs in the terminal can still read ignored files, so keep real secrets out of the repo too.
- Use current C# features: primary constructors, collection expressions, file-scoped namespaces, C# 14's field keyword, and nullable reference types (#nullable enable).
- Structure lightweight microservices with ASP.NET Core Minimal APIs using typed route groups and TypedResults return values.
- Enforce AsNoTracking() on read-only EF Core queries to eliminate memory overhead from change trackers.
- Validate request payloads using FluentValidation or MiniValidation before executing business logic.
- Use IHttpClientFactory with typed resilience pipelines (Polly) for outbound HTTP calls.
Code to avoid, and what to write instead
The rule steers the agent away from the left and toward the right.
// Discouraged: Nested namespaces, missing AsNoTracking, untyped object returns
namespace App.Controllers
{
public class UsersController : Controller
{
[HttpGet]
public IActionResult GetUser(Guid id)
{
var user = _context.Users.Find(id); // Untracked query tracking all state!
return Ok(user);
}
}
}namespace App.Features.Users;
using Microsoft.AspNetCore.Http.HttpResults;
using Microsoft.EntityFrameworkCore;
public record CreateUserRequest(string Email, string FullName);
public record UserDto(Guid Id, string Email, string FullName);
public static class UserEndpoints
{
public static RouteGroupBuilder MapUserEndpoints(this RouteGroupBuilder group)
{
group.MapGet("/{id:guid}", async Task<Results<Ok<UserDto>, NotFound>> (Guid id, AppDbContext db) =>
{
var user = await db.Users
.AsNoTracking()
.Where(u => u.Id == id)
.Select(u => new UserDto(u.Id, u.Email, u.FullName))
.FirstOrDefaultAsync();
return user is not null ? TypedResults.Ok(user) : TypedResults.NotFound();
});
return group;
}
}Install it in one command
- 01
Go to your project root
The file goes at .cursorignore, relative to the root.
- 02
Download the file
Run the command on the right. It downloads this preset and writes the file.
- 03
Make sure it gets used
Cursor applies .cursorignore automatically. Matching files leave the index and AI features, but commands the agent runs in the terminal can still read them.
$ curl -fsSL "https://www.devscratchpad.tech/api/raw/cursorignore/csharp-dotnet-10" -o ".cursorignore"
writes .cursorignore
.cursorignore
To write the file from your own code instead, use Read your code or Convert Legacy Rules in the editor above.
More for .NET 10 & C# 14 Minimal APIs
Questions
- How is .cursorignore different from .gitignore?
- .gitignore decides what git tracks. .cursorignore keeps files out of Cursor's codebase index and AI features; Cursor already skips files in .gitignore when it indexes.
- Does .cursorignore reduce wasted context?
- Yes. Ignored files are not indexed or pulled into requests, so build output and large data files do not crowd out your source code.