agentleFS
lgzarturolgzarturo/codeconductor/.cursor/rules/context-budget.mdc

codeconductor / rules

Cursor rule0 starsChanged 25 days agoMITView on GitHub

Context budget and token optimization — use when conversation is long or switching tasks.

The file

We split this context-budget.mdc into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 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.

  • 2

    Very specific

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

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

    Use /summarize or /compress before re-delegating with large context.

    line 9
  2. Very specific:

    Prefer @filename references over pasting full file contents.

    line 11

≈ “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
context-budget.mdc
---
description: Context budget and token optimization — use when conversation is long or switching tasks.
alwaysApply: false
---

# Context Budget

- Execute `/clear` when switching to an unrelated task type.
- Use `/summarize` or `/compress` before re-delegating with large context.
- Delegate verbose exploration to background subagents (`repo-explorer`).
- Prefer `@filename` references over pasting full file contents.
- Respect `.cursorignore` — do not read excluded paths unless explicitly required.

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.