agentleFS
tatashbartatashbar/Economic-Modeling-Studio/.cursor/rules/model-code.mdc

Economic-Modeling-Studio / rules

Cursor rule4 starsChanged 6 days agoMITView on GitHub

Model Code standards

The file

We split this model-code.mdc into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No hard-coded parameter values in equations or solver code.

    line 9
  2. Distinctive:

    Every model has a documented timing convention, units and base period

    line 10
  3. Distinctive:

    Use fixed random seeds for any stochastic routine.

    line 12
  4. Distinctive:

    Never overwrite a baseline.

    line 13

≈ “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
model-code.mdc
---
description: Model Code standards
globs: models/**
alwaysApply: false
---
<!-- Generated from .claude/rules/model-code.md by tools/sync_agents.py. Edit the source, then run the script. -->
# Rules: Model Code

- No hard-coded parameter values in equations or solver code; parameters come from a parameter file or block with sources
- Every model has a documented timing convention, units and base period
- Assert accounting identities and steady-state residuals in tests
- Use fixed random seeds for any stochastic routine; seeds are logged
- Never overwrite a baseline; write new results to a new, versioned path
- Models must run from a clean checkout with one documented command
- Every run saves its results (tables, charts, simulated paths, impulse responses, forecasts) to `output/<run-id>/` inside the model folder, with a `run-log.md` recording the date, the command, the code version, the data vintage, the parameter file and the seed; results first shown in a chat are saved there too
- Model code lives in files in the model folder, in an approved language (`toolchains` in `studio-config.yaml`), never only in a chat or a notebook

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.