agentleFS
zotoiozotoio/CRUX-Compress/.cursor/rules/_CRUX-RULE.mdc

CRUX-Compress / rules

Cursor rule8 starsChanged 2 months agoMITView on GitHub

CRUX Compression of markdown rules

The file

We split this _CRUX-RULE.mdc into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always interpret, understand and adhere to the meaning compressed in CRUX notation!

    line 13
  2. Distinctive:

    When constructing paths, URIs, or tool calls from CRUX references, preserve the literal path, filename, and extension exactly as they exist …

    line 16
  3. Distinctive:

    NEVER edit files that are CRUX compression output.

    line 19
  4. Distinctive:

    Always edit the corresponding SOURCE file instead, then re-generate the derived CRUX output.

    line 24
  5. Very specific:

    If you are about to edit a file and it contains sourceChecksum, sourceUrl, or the generated-file banner, stop and move the change to the …

    line 28

≈ “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
_CRUX-RULE.mdc
---
description: CRUX Compression of markdown rules
alwaysApply: true
version: 1.1
repository: https://github.com/zotoio/CRUX-Compress
---

# CRUX Rules

Load `AGENTS.md` if not in context — its `<CRUX>` block has the foundational rules and agent registry. Load `CRUX.md` only when compressing, decompressing, authoring, or validating CRUX notation.

## CRUX Decompression - CRITICAL
Always interpret, understand and adhere to the meaning compressed in CRUX notation! NEVER forget this.

## Path Construction - CRITICAL
When constructing paths, URIs, or tool calls from CRUX references, preserve the literal path, filename, and extension exactly as they exist in the repository.

## CRUX Compressed File Protection - CRITICAL
NEVER edit files that are CRUX compression output. These are:
- Files with `.crux.md` or `.crux.mdc` extensions
- Files whose frontmatter contains both `generated:` and `sourceChecksum:` or `sourceUrl:`
- Files that carry the banner `> [!IMPORTANT] > Generated file - do not edit!`

Always edit the corresponding SOURCE file instead, then re-generate the derived CRUX output.
- `[name].crux.md` / `[name].crux.mdc` -> edit the real source file such as `[name].md`
- `AGENTS.md` is a source file in this repository; do not invent `AGENTS.source.md`

If you are about to edit a file and it contains `sourceChecksum`, `sourceUrl`, or the generated-file banner, stop and move the change to the source file instead.

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.