agentleFS
joaoguimaraesprojoaoguimaraespro/personal-finance/.cursor/rules/angular-security.mdc

personal-finance / rules

Cursor rule1 starsChanged todayMITView on GitHub

Angular security: sanitiser bypasses, HttpClient and interceptors, secrets in environment files, guards, SSR

The file

We split this angular-security.mdc into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 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.

  • 3

    Very specific

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

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

    Never bypassSecurityTrust* on user-controlled input.

    line 9
  2. Very specific:

    All HTTP through HttpClient, so auth, XSRF and error interceptors apply.

    line 11
  3. Very specific:

    Every authenticated or role-restricted route has a guard (canMatch for sensitive ones).

    line 14

≈ “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
angular-security.mdc
---
description: "Angular security: sanitiser bypasses, HttpClient and interceptors, secrets in environment files, guards, SSR"
globs: **/src/app/**/*.ts,**/src/app/**/*.html,**/*.component.ts,**/*.service.ts,**/*.interceptor.ts,**/environments/*.ts
alwaysApply: false
---
<!-- Generated by armature from stack-angular/rules/angular/security.md. Edit the source rule, not this file. -->
# Angular security

- Never `bypassSecurityTrust*` on user-controlled input; avoid `[innerHTML]` with untrusted content; never build
  templates from user data; validate URLs before binding `[href]`.
- All HTTP through `HttpClient`, so auth, XSRF and error interceptors apply. Treat responses as `unknown` at the
  boundary when they are not from your own typed API.
- `environment.ts` is public: no secrets in it, no tokens in `localStorage`. Session cookies are httpOnly.
- Every authenticated or role-restricted route has a guard (`canMatch` for sensitive ones); the API enforces the same
  rule.
- Interceptors and logs never print tokens, personal data or response bodies.
- SSR: no server environment values in `TransferState` unless public; gate `window`/`document` with the platform.
- CSP is set server-side; no `unsafe-inline` in `script-src`.

<!-- Adapted from affaan-m/ECC rules/angular/security.md (MIT) at d2ef268; merged with the owner's conventions (personal-finance-sdd: XSRF interceptor, httpOnly session, no personal data). -->

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.