agentleFS
Sign inStart free
craigcossairtcraigcossairt/trellis/.cursor/rules/project.mdc

trellis / rules

Cursor rule5 starsChanged 9 days agoMITView on GitHub

Project conventions - canonical source is AGENTS.md

The file

We split this project.mdc into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read AGENTS.md at the repo root and follow it - it is the canonical instruction file for all AI agents on this project.

    line 6

≈ “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
project.mdc
---
description: Project conventions - canonical source is AGENTS.md
alwaysApply: true
---

Read `AGENTS.md` at the repo root and follow it - it is the canonical instruction file for all
AI agents on this project. Full methodology docs live in `docs/methodology/` (TDD workflow,
bug-fix protocol, session habits). Append bug patterns to `docs/common-gotchas.md` and decisions
to `docs/decision-log.md` as described in AGENTS.md § Autonomous Housekeeping.

Guardrail hooks for Cursor are wired in `.cursor/hooks.json` (same scripts Claude Code runs;
trust the workspace so they load). Honor the rules they enforce even if hooks aren't firing:
never edit secrets or lock files, and run `bash bin/verify-green.sh` before pushing when the
push gate is configured.

Skills in `.cursor/skills/` are routers, not procedures. Each is frontmatter plus one sentence
naming a canonical file under `.claude/` - read that file when a router matches the task, and
never fork its body into the router. Copy the canonical `description` verbatim: in Cursor it is
the trigger, so a reworded one silently stops matching phrases the canonical skill answers to.

While this directory exists, adding a skill or command under `.claude/` means adding its router
in the same commit; hooks CI fails either half of that pair going missing. If the project drops
Cursor support, delete `.cursor/` outright and the rule no longer applies.

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