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

Economic-Modeling-Studio / rules

Cursor rule4 starsChanged 6 days agoMITView on GitHub

Econometrics Code standards

The file

We split this econometrics-code.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 data from a frozen vintage in data/processed/.

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

- VARs, BVARs, local projections, factor models and nowcasting models live here, one folder per model
- Read data from a frozen vintage in `data/processed/`; record the vintage and the estimation sample in a settings file
- Report integration order, lag selection, stability and residual diagnostics with every estimate
- Forecast evaluation re-estimates on data up to each origin only, and the no-look-ahead check is an automated test
- Compare against simple benchmarks (no-change, univariate AR) on the same sample and split
- Bootstrap and simulation draws use a fixed, logged seed
- Estimation-only models need no lego manifest; register one if the model feeds or is fed by other bricks

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.