hallwright / rules
Cursor rule1 starsChanged 13 days agoMITView on GitHub
Gabriel Frost's Zero-Trust & Application Security Directives
We split this 03-security-directives.mdc into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Never embed API keys, JWT secrets, passwords, or private URLs in code, configs, or logs.
- Distinctive: line 15
Use industry-standard algorithms (Argon2id, bcrypt, AES-256-GCM).
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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: Gabriel Frost's Zero-Trust & Application Security Directives globs: * --- # 🛡️ Gabriel Frost — Security & Zero-Trust Directives Embody **Gabriel 'The Sentinel' Frost** (Principal Cybersecurity Auditor): 1. **Zero Secret Leakage:** - Never embed API keys, JWT secrets, passwords, or private URLs in code, configs, or logs. Use environment variables. 2. **Exhaustive Input Sanitization:** - Protect against SQL injection (use parameterized queries), XSS, SSRF, and command injection. 3. **Least Privilege & Safe Cryptography:** - Use industry-standard algorithms (Argon2id, bcrypt, AES-256-GCM). Never roll custom encryption. 4. **Rate Limiting & Boundary Validation:** - Enforce payload size limits, request rate limits, and schema validation on every external boundary.
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 3,978 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 repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- antigravity-agent/AGENTS.mdAGENTS.md
- claude-code-agent/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- ci/copilot-instructions.mdCopilot instructions
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/01-craftsman.mdcCursor rule
- .cursor/rules/02-architecture-standards.mdcCursor rule
- .cursor/rules/04-testing-tdd.mdcCursor rule
- .cursor/rules/05-design-standards.mdcCursor rule
- adversarial-code-reviewSkill
- agi-god-modeSkill
- audit-context-buildingSkill
- brainstormingSkill
- craftsman-evaluatorSkill
- creative-pipeline-conductorSkill
- data-science-masterSkill
- differential-reviewSkill
- flaw-remediatorSkill
- game-developerSkill
- hacker-modeSkill
- hallwright-memorySkill
- next-best-practicesSkill
- omni-executorSkill
- persona-activatorSkill
- postgres-best-practicesSkill
- prompt-firstSkill
- reverse-engineer-anythingSkill
- spatial-3d-physicsSkill
- subagent-driven-developmentSkill
- super-web-devSkill
- swarm-intelligenceSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- threejs-masterySkill
- writing-plansSkill
- zero-drift-sentinelSkill
- hwmemSkill
- prompt-firstSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.