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

Economic-Modeling-Studio / rules

Cursor rule4 starsChanged 6 days agoMITView on GitHub

EViews Code standards

The file

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

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

  • 3

    Very specific

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

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

    Write equations, model objects, add factors and scenarios in programs (model, append, addassign, scenario), not by clicking in the interface

    line 11
  2. Very specific:

    Use relative paths from the model folder (%0 or cd to the program's own folder).

    line 12
  3. Very specific:

    Run in batch from the command line (EViews.exe /run run.prg or the executable you have) or from Python with pyeviews, and end the program …

    line 16

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

- One master program (`run.prg`) runs the model from scratch; it calls the other programs in order (`include` or `exec`)
- The workfile is an output, never the source: `run.prg` creates it (`wfcreate`), imports data from a frozen vintage in `data/processed/` and rebuilds every object; never edit a `.wf1` by hand or keep results only in it
- Write equations, model objects, add factors and scenarios in programs (`model`, `append`, `addassign`, `scenario`), not by clicking in the interface
- Use relative paths from the model folder (`%0` or `cd` to the program's own folder); never a personal folder
- Set and log the seed (`rndseed`) before any bootstrap, stochastic simulation or random draw; record the EViews version in the run log
- Save results to `output/<run-id>/`: tables with `freeze` then `save` or `wfsave` to CSV, graphs with `graph.save` as PNG or PDF, series and forecasts with `wfsave` or `pagesave` to CSV
- Store parameter values and calibration choices in a scalar or table block at the top of the program with sources, not inside equations
- Run in batch from the command line (`EViews.exe /run run.prg` or the executable you have) or from Python with `pyeviews`, and end the program with `exit` so batch runs close

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.