What problem does it solve? Research repositories accumulate scripts, datasets, tables, and scratch files until no one can tell deliverables from diagnostics, making results irreproducible for collaborators and future you. ## Core Features & Use Cases - Paper-centric structure: Enforces a stage-first layout separating raw, intermediate, and output data from code, results, sandbox, and per-category archives. - Naming and git conventions: Standardizes snake_case filenames, bans dates and version suffixes, and defines what to track versus gitignore, including shrinking oversized data to parquet. - Phase-boundary checkpoints: Commits local checkpoints at milestones like a clean dataset or validated result, and promotes durable lessons to docs/LESSONS.md. - Use Case: Before pushing a week of difference-in-differences analysis, inventory every artifact, move superseded runs to archive/, rename outputs to traceable conventions, and commit a labeled checkpoint. ## Quick Start Ask the assistant to clean up and organize the research repository before committing, standardizing file names and archiving scratch files.