agentleFS
aaronreneaaronrene/knowtation/.cursor/rules/l1-checkpoints-consumer-owned.mdc

knowtation / rules

Cursor rule1 starsChanged 2 months agoMITView on GitHub

Domain-neutral L1 checkpoint reminder — consumer owns verify scripts and policy steps

The file

We split this l1-checkpoints-consumer-owned.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:

    When checkpoints.enabled is true in .overseer/config.yaml:

    line 9
  2. Very specific:

    Run overseer verify-step before advancing work — do not hand-edit verified: true.

    line 12
  3. Very specific:

    Keep verify scripts repo-relative, executable, and exit 0 only with proof.

    line 13

≈ “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
l1-checkpoints-consumer-owned.mdc
---
description: Domain-neutral L1 checkpoint reminder — consumer owns verify scripts and policy steps
globs:
alwaysApply: false
---

# L1 checkpoints (consumer-owned)

When `checkpoints.enabled` is true in `.overseer/config.yaml`:

1. Define steps in consumer `policy/checkpoints.yaml` (not in the kit).
2. Run `overseer verify-step` before advancing work — do not hand-edit `verified: true`.
3. Keep verify scripts repo-relative, executable, and exit `0` only with proof.

The kit orchestrates; your domain pack decides what “pass” means.

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.