jpe-tables-figures

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpe-tables-figures --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# Tables & Figures (jpe-tables-figures) ## When to trigger - Tables are overloaded with columns; the reader cannot find the economic point - Figures are decorative rather than carrying the argument - Notes are thin — a reader cannot reconstruct units, sample, or specification from the exhibit alone - You are deciding what belongs in the main text vs. the online appendix ## The JPE exhibit philosophy A JPE table or figure should be **self-contained and economically legible**: a referee skimming exhibits should grasp the result, the magnitude, and what it means. As a **University of Chicago Press** journal, JPE typesets accepted exhibits to Chicago Press production standards — no chartjunk, no gratuitous color, units and economic magnitudes front and center. Every exhibit must also be regenerated by the master script in the **JPE Dataverse** replication deposit, so the numbers in the paper and the numbers the code produces must match exactly when the **JPE Data Editor** verifies them at conditional accept (see `jpe-replication-package`). The headline result usually deserves a *figure* (an event-study plot, a fit-of-model plot, a counterfactual) because magnitudes and dynamics read fa