agentleFS
tatashbartatashbar/Economic-Modeling-Studio/.cursor/rules/lego-manifests.mdc

Economic-Modeling-Studio / rules

Cursor rule4 starsChanged 6 days agoMITView on GitHub

Lego Manifests standards

The file

We split this lego-manifests.mdc into the rules it gives an agent

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

  • 1

    Very specific

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

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

    Every variable exchanged between bricks is a declared port with a unit from lego/ports.json

    line 9
  2. Distinctive:

    Every required input has a source brick or a documented stub.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 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
lego-manifests.mdc
---
description: Lego Manifests standards
globs: models/**/model.lego.json,lego/**
alwaysApply: false
---
<!-- Generated from .claude/rules/lego-manifests.md by tools/sync_agents.py. Edit the source, then run the script. -->
# Rules: Lego Manifests

- Every variable exchanged between bricks is a declared port with a unit from `lego/ports.json`
- Every required input has a source brick or a documented stub; a requirement without a stub is intentional
- Declare lags explicitly; same-period dependencies form simultaneous blocks that the solver must handle jointly
- A brick on a different frequency from the core declares a bridge
- Change the set of bricks only with `python tools/lego.py attach|detach|swap --apply`, and record validation results only with `python tools/lego.py validate`, so the history, revision and stale markers stay correct
- Ports, required slots and identities may be edited by hand; run `python tools/lego.py check` afterwards
- Picture positions (`place`) come from `python tools/lego.py arrange` or are edited by hand; they never change the wiring, and `check` warns if bricks overlap or float
- A brick is marked validated only with a validation report as evidence (`validate --report <path>`)
- A brick changed since validation is stale and is re-validated, with its neighbours, before release
- Declare each brick's elements (variables, equations, parameters, shocks, data, constraints) with `python tools/lego.py elements`, counted from the code where possible; mark unsourced parameters as `assumed` and constraints as `verified` only after a run confirms them

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.