agentleFS
Sign inStart free
Fadi88Fadi88/one-man-startup/.cursor/rules/skill-known-reds.mdc

one-man-startup / rules

Cursor rule16 starsChanged 2 days agoMITView on GitHub

The register of failing checks the founder has decided to live with for now, each matched by its failing line, owned and dated. Use when a red is accepted, rechecked or fixed.

We split this skill-known-reds.mdc into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the check passes again the sweep says "now passes, prune".

    line 26
  2. Very specific:

    Keep reason to one or two sentences.

    line 28
  3. Very specific:

    Only the founder decides an entry.

    line 30

≈ “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
skill-known-reds.mdc
---
description: "The register of failing checks the founder has decided to live with for now, each matched by its failing line, owned and dated. Use when a red is accepted, rechecked or fixed."
alwaysApply: false
---

<!-- Generated by tools/sync_adapters.py from skills/known-reds/SKILL.md. Edit the source, not this file. -->

# Known reds

`tools/known_red.json` is a list. Each entry:

```json
{
  "check": "pricing_check.py",
  "fails": "FAIL  monthly price under the floor",
  "reason": "Launch discount, decided on the 1 March call.",
  "decided_by": "founder",
  "decided_on": "2026-03-01",
  "recheck": "2026-04-01"
}
```

- `fails` is matched against the failing line, not the file. A second, different failure in the
  same check still shows as NEW RED.
- `recheck` is a date, or `null` for a standing decision. An overdue recheck turns the sweep red.
- When the check passes again the sweep says "now passes, prune"; remove the entry in the same
  change.
- Keep `reason` to one or two sentences. The register is a list, not a diary.

Only the founder decides an entry. An agent puts the exact entry to them as a decision card
(`skills/founder-voice/`) and, on their yes, the orchestrator writes it and records the yes in
`p1-closed-decisions.md`; the founder never edits the file. The sweep refuses a malformed
entry, such as an empty `fails`, which would silence every red in its check (TPL-13).

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