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

Economic-Modeling-Studio / rules

Cursor rule4 starsChanged 6 days agoMITView on GitHub

Stata Code standards

The file

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

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

  • 4

    Very specific

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

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

    Use relative paths from the model folder.

    line 11
  2. Very specific:

    Read data from a frozen vintage in data/processed/.

    line 13
  3. Very specific:

    Write a text log for each run (log using "output/<run-id>/stata-log.txt", text replace) next to the run log

    line 14
  4. Very specific:

    Run in batch mode for reproducibility (stata-mp -b do run.do or the edition you have)

    line 17

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

- One master do-file (`run.do`) runs the model from a clean start; it calls the other do-files in order
- Pin the version at the top of every do-file (`version 17` or the version you use) and start with `clear all` and `set more off`
- Use relative paths from the model folder; never `cd` to a personal folder
- Set and log the seed (`set seed`) before any bootstrap, simulation or random split
- Read data from a frozen vintage in `data/processed/`; never overwrite a source `.dta`
- Write a text log for each run (`log using "output/<run-id>/stata-log.txt", text replace`) next to the run log
- Save estimates and tables with `esttab`, `putexcel` or `export delimited` to `output/<run-id>/`, and graphs with `graph export` as PNG or PDF
- Record user-written packages (`ssc install`, `net install`) and their versions in the model README; prefer built-in commands
- Run in batch mode for reproducibility (`stata-mp -b do run.do` or the edition you have)

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.