agentleFS
edenbuildsedenbuilds/agentloop/.cursor/rules/verification-law.mdc

agentloop / rules

Cursor rule0 starsChanged 4 months agoMITView on GitHub

External verification required before claiming completion

The file

We split this verification-law.mdc into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    Do not claim done without running or explicitly waiving an external gate.

    line 7
  2. Distinctive:

    Prefer actionable tool/test errors as the next prompt over vague re-checks.

    line 8
  3. Distinctive:

    Avoid redundant "double-check" instructions on models that already self-correct.

    line 10
  4. Distinctive:

    If gates cannot run, state the gap and the smallest missing check.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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
verification-law.mdc
---
description: External verification required before claiming completion
alwaysApply: true
---

Verification law:
- Do not claim done without running or explicitly waiving an external gate.
- Prefer actionable tool/test errors as the next prompt over vague re-checks.
- On review tasks, report real issues first; severity-filter in a second pass if requested.
- Avoid redundant "double-check" instructions on models that already self-correct; spend tokens on gates instead.
- If gates cannot run, state the gap and the smallest missing check.

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.