agentleFS
Sign inStart free
spiriMirrorspiriMirror/libuipc/.cursor/skills/cursor-rules/SKILL.md

cursor-rules

Skill351 starsChanged 3 months agoApache-2.0View on GitHub

How to add or edit Cursor rules in our project

The file

We split this skill 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. Very specific:

    Always place rule files in PROJECT_ROOT/.cursor/rules/:

    line 10
  2. Distinctive:

    Follow the naming convention:

    line 18
  3. Distinctive:

    Use kebab-case for filenames

    line 19
  4. Distinctive:

    Always use .mdc extension

    line 20
  5. Distinctive:

    Never place rule files:

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.md

Cursor Rules Location

How to add new cursor rules to the project

  1. Always place rule files in PROJECT_ROOT/.cursor/rules/:
    .cursor/rules/
├── your-rule-name.mdc
├── another-rule.mdc
└── ...
  2. Follow the naming convention:
    • Use kebab-case for filenames
    • Always use .mdc extension
    • Make names descriptive of the rule's purpose
  3. Directory structure:
    PROJECT_ROOT/
├── .cursor/
│   └── rules/
│       ├── your-rule-name.mdc
│       └── ...
└── ...
  4. Never place rule files:
    • In the project root
    • In subdirectories outside .cursor/rules
    • In any other location
  5. Cursor rules have the following structure:
---
description: Short description of the rule's purpose
globs: optional/path/pattern/**/*
alwaysApply: false
---
# Rule Title

Main content explaining the rule with markdown formatting.

1. Step-by-step instructions
2. Code examples
3. Guidelines

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