personal-finance / rules
Cursor rule1 starsChanged todayMITView on GitHub
C#/.NET security: secrets, SQL injection, validation, JWT auth and authorisation, safe errors
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,243 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository84 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/angular-coding-style.mdcCursor rule
- .cursor/rules/angular-patterns.mdcCursor rule
- .cursor/rules/angular-security.mdcCursor rule
- .cursor/rules/angular-testing.mdcCursor rule
- .cursor/rules/common-code-review.mdcCursor rule
- .cursor/rules/common-coding-style.mdcCursor rule
- .cursor/rules/common-development-workflow.mdcCursor rule
- .cursor/rules/common-security.mdcCursor rule
- .cursor/rules/common-testing.mdcCursor rule
- .cursor/rules/csharp-coding-style.mdcCursor rule
- .cursor/rules/csharp-data-access.mdcCursor rule
- .cursor/rules/csharp-patterns.mdcCursor rule
- .cursor/rules/csharp-testing.mdcCursor rule
- .cursor/rules/design-design-system.mdcCursor rule
- .cursor/rules/project-backend.mdcCursor rule
- .cursor/rules/project-security.mdcCursor rule
- .cursor/rules/project-testing.mdcCursor rule
- .cursor/rules/project-web.mdcCursor rule
- .cursor/rules/typescript-coding-style.mdcCursor rule
- .cursor/rules/typescript-patterns.mdcCursor rule
- .cursor/rules/typescript-security.mdcCursor rule
- .cursor/rules/typescript-testing.mdcCursor rule
- angular-guideSkill
- break-uiSkill
- dotnet-create-command-querySkill
- dotnet-create-entitySkill
- dotnet-create-moduleSkill
- dotnet-ef-migrationSkill
- emil-design-engSkill
- frontend-designSkill
- impeccableSkill
- review-animationsSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- ui-ux-pro-maxSkill
- angular-guideSkill
- break-uiSkill
- dotnet-create-command-querySkill
- dotnet-create-entitySkill
- dotnet-create-moduleSkill
- dotnet-ef-migrationSkill
- emil-design-engSkill
- frontend-designSkill
- impeccableSkill
- review-animationsSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- The first 60 shown.
The file
We split this csharp-security.mdc into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
No keys, tokens or connection strings in source or appsettings*.json.
- Very specific: line 21
Use the framework handlers (AddAuthentication().AddJwtBearer(...)), never hand-parsed tokens.
≈ “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.
Files
--- description: "C#/.NET security: secrets, SQL injection, validation, JWT auth and authorisation, safe errors" globs: **/*.cs,**/*.csproj,**/appsettings*.json alwaysApply: false --- <!-- Generated by armature from stack-dotnet/rules/csharp/security.md. Edit the source rule, not this file. --> # C# security Extends [common/security.md](common-security.mdc). ## Secrets - No keys, tokens or connection strings in source or `appsettings*.json`. User secrets locally, environment or a secret manager deployed. Read required settings with a fail-fast check at startup. ## Input - Validate requests at the boundary (FluentValidation in a pipeline behaviour, or explicit guards) before business logic runs. Validate sort fields and filter operators against an allow-list before composing dynamic queries. - Parameterised SQL only (EF Core, Dapper parameters, ADO.NET parameters). ## Authentication and authorisation - Use the framework handlers (`AddAuthentication().AddJwtBearer(...)`), never hand-parsed tokens. - JWT bearer: validate issuer, audience (the service's own client id, never `account`), lifetime and signing key; `MapInboundClaims = false` so claim names stay as issued. - Authorise at the endpoint or handler with policies; tenant and roles come from validated token claims, not from headers, query strings or routes. - SignalR over WebSockets reads the token from `access_token` only on hub paths. ## Errors - Clients get Problem Details with a safe message and an error code; logs get the exception with structured context. Never return stack traces, SQL or file paths. Never log raw tokens, passwords or personal data. <!-- Adapted from affaan-m/ECC rules/csharp/security.md (MIT) at d2ef268 (identical to the Ordo frozen copy); merged with NEXUS knowledge/keycloak (audience per service, realm roles) and knowledge/dotnet/signalr. -->
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.

