agentleFS
Sign inStart free
vasceannievasceannie/slopgate/.cursor/rules/quality.mdc

slopgate / rules

Cursor rule1 starsChanged 51 days agoMITView on GitHub

Quality assurance standards for security (OWASP), performance, accessibility (WCAG), and code quality reviews

We split this quality.mdc into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every finding must include file:line, description, and fix

    line 14
  2. Very specific:

    Run automated tools first: npm audit, bandit, lighthouse

    line 16
  3. Distinctive:

    No false positives — every finding must be reproducible

    line 17

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
quality.mdc
---
description: "Quality assurance standards for security (OWASP), performance, accessibility (WCAG), and code quality reviews"
globs: 
alwaysApply: false
---

<!-- Generated by oh-my-agent. Source: .agents/rules/quality.md -->

# Quality Assurance Standards

## Core Rules

1. Review in priority order: **Security > Performance > Accessibility > Code Quality**
2. Every finding must include file:line, description, and fix
3. Severity levels: CRITICAL (security breach/data loss), HIGH (blocks launch), MEDIUM (this sprint), LOW (backlog)
4. Run automated tools first: `npm audit`, `bandit`, `lighthouse`
5. No false positives — every finding must be reproducible
6. Provide remediation code, not just descriptions

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.

Check your setup, free