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

Economic-Modeling-Studio / rules

Cursor rule4 starsChanged 6 days agoMITView on GitHub

GEMPACK and GTAP Code standards

The file

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

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Distinctive:

    Check the benchmark before any shock: a zero-shock run (homogeneity test with a numeraire shock) reproduces the database

    line 13
  2. Distinctive:

    Keep the aggregation mapping (GTAPAgg or FlexAgg sectors, regions and endowments) with the model and record the database version and base …

    line 14
  3. Very specific:

    The GTAP database is licensed: Keep it in data/raw/gtap/ (outside git), never commit, share or upload the database or files derived from it …

    line 18
  4. Very specific:

    Run in batch from the command line (the compiled model with -cmf, or gemsim) so every experiment reruns with one command

    line 19

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

- The model code is the TABLO file (`.tab`); record which model and version it is (for example standard GTAP 7, GTAP-E, GTAP-POWER) and every change made to it
- One command file (`.cmf`) per experiment holds the files used, the closure, the shocks and the solution method; never run an experiment from settings saved only in RunGTAP or another interface
- The closure is written out in the `.cmf` and justified; report results under a second closure where they matter
- Solve with a multi-step method (Gragg with extrapolation, for example 2-4-6 steps) and report the extrapolation accuracy; a one-step Johansen solution is for checks only
- Check the benchmark before any shock: a zero-shock run (homogeneity test with a numeraire shock) reproduces the database
- Keep the aggregation mapping (GTAPAgg or FlexAgg sectors, regions and endowments) with the model and record the database version and base year (for example GTAP 11, 2017)
- Elasticities are sourced; report systematic sensitivity on the key ones (Armington, CET, factor mobility)
- Report welfare as equivalent variation with its decomposition (allocative, terms of trade, endowment, technical change), and use subtotals to split results by shock
- Export results from the solution file (`.sl4`) to CSV with SLTOHT or ViewHAR into `output/<run-id>/`, together with the `.cmf` and the log of the run
- **The GTAP database is licensed.** Keep it in `data/raw/gtap/` (outside git), never commit, share or upload the database or files derived from it at full detail, and record the license holder; only aggregated results may leave the studio
- Run in batch from the command line (the compiled model with `-cmf`, or `gemsim`) so every experiment reruns with one command

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.