Skip to content
cccskills
FreePublished on GitHub

newproject

Set up a research project with separate folders for code, source data, cleaned datasets, results, and documents. Create a research rules file from a template, a project README, and an initial progress log.

OriginalShow the original description

Scaffold a new research project with standard directory structure, CLAUDE.md template, and documented README. Use this at the start of every new project to ensure consistent organization.

Run score Not tested

See how to install

Good for

  • Starting a new research project
  • Standardizing folders across research projects
  • Separating source data from cleaned datasets
  • Keeping progress records across Claude sessions

Files included (1)

  • SKILL.md3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

New Project Scaffold

Create a new research project folder with Scott's standard structure. This skill is invoked at the start of every project.

What Gets Created

[project-name]/
├── CLAUDE.md              # Permanent research rules (copied from template)
├── README.md              # Project-specific overview (auto-generated)
├── code/
│   ├── R/
│   ├── python/
│   └── stata/
├── data/
│   ├── raw/               # Original source data (never modify)
│   └── clean/             # Cleaned/merged datasets
├── output/
│   ├── tables/
│   └── figures/
├── documents/             # Outside PDFs, papers (use /split-pdf on these)
├── decks/                 # Beamer presentations (rhetoric of decks)
├── notes/                 # Scratch notes, random ideas, misc
└── progress_logs/         # Session continuity across Claude conversations

Execution

  1. Get the project name from the argument. If none provided, ask.

    • Convert spaces to hyphens, lowercase
  2. Determine location — default is current working directory. Confirm if unclear.

  3. Create all directories:

    mkdir -p [project-name]/{code/{R,stata,python},data/{raw,clean},output/{figures,tables},documents,decks,notes,progress_logs}
    
  4. Copy CLAUDE.md from ~/mixtapetools/claude/CLAUDE.md:

    • Replace [Your Name] with Scott
    • Update project name in the overview section
  5. Generate README.md with:

    • Project title
    • Visual directory tree in a fenced code block (monospace)
    • Explanation of each folder's purpose
    • Note that CLAUDE.md is copied from a permanent template and edited per-project
    • Note that README.md is for project-specific documentation
    • Note that progress_logs/ maintains continuity across Claude sessions
    • Placeholder sections: Overview, Collaborators, Status, Key Files

    The README must include this tree block:

    ```
    [project-name]/
    ├── CLAUDE.md              # Research rules & estimation philosophy (permanent)
    ├── README.md              # This file — project-specific notes
    ├── code/
    │   ├── R/                 # R scripts
    │   ├── python/            # Python scripts
    │   └── stata/             # Stata do-files
    ├── data/
    │   ├── raw/               # Original source data (never modify these)
    │   └── clean/             # Cleaned and merged datasets
    ├── output/
    │   ├── tables/            # Generated tables (LaTeX, CSV)
    │   └── figures/           # Generated figures (PDF, PNG)
    ├── documents/             # Outside papers and PDFs (split with /split-pdf)
    ├── decks/                 # Beamer presentations (rhetoric of decks philosophy)
    ├── notes/                 # Scratch notes, ideas, miscellaneous
    └── progress_logs/         # Session logs for continuity across Claude conversations
    ```
    
  6. Create initial progress log at progress_logs/YYYY-MM-DD_setup.md:

    • Record the creation date
    • List next steps as a checklist
  7. Report success — show structure with ls, remind user to update CLAUDE.md.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a1

FreeSummary

Turn a broad research idea into clear, testable questions. Compare familiar and less conventional approaches, structure the selected question around its population and methods, and assess variables, feasibility, and potential theoretical contributions.

  • Turn a research topic into testable questions
  • Narrow an overly broad research question
  • Compare alternative research angles
brycewang-stanford/Auto-Empirical-Research-Skills4.7KUpdated Oct 20, 2026

a2

FreeSummary

Helps build a research framework by comparing theories, mapping relationships between variables, and deriving testable hypotheses. Explores less conventional options, examines weaknesses and competing explanations, and produces diagrams with anticipated reviewer objections.

  • Comparing theories for a research question
  • Deriving hypotheses from relationships between variables
  • Examining weaknesses and anticipated reviewer objections
brycewang-stanford/Auto-Empirical-Research-Skills4.7KUpdated Oct 20, 2026

a5

FreeSummary

Clarify the philosophical assumptions behind a research project and check whether they fit the proposed methods. Get a reasoned research stance, draft proposal wording, and guidance for explaining how the researcher's background and values shape the study.

  • Clarifying philosophical foundations for a research proposal
  • Explaining why the chosen research methods fit the study
  • Drafting a statement about the researcher's position
brycewang-stanford/Auto-Empirical-Research-Skills4.7KUpdated Oct 20, 2026

academic-paper

FreeSummary

Plan and draft academic papers through specialized agent roles covering literature, arguments, citations, and review. Get chapter guidance, revision roadmaps, Traditional Chinese and English abstracts, and documents formatted as LaTeX, DOCX, PDF, or Markdown.

  • Planning a paper chapter by chapter
  • Drafting a paper from research materials
  • Turning reviewer comments into a revision roadmap
brycewang-stanford/Auto-Empirical-Research-Skills4.7KUpdated Oct 20, 2026

Turn a detailed outline into a philosophy or interdisciplinary manuscript. Draft chapters with repeated quality reviews, check terminology and arguments across sections, and prepare the manuscript, evaluation reports, abstract, and metadata for submission.

  • Draft a full paper from a detailed outline
  • Review argument and citation quality chapter by chapter
  • Check terminology and argument flow across chapters
brycewang-stanford/Auto-Empirical-Research-Skills4.7KUpdated Oct 20, 2026

Simulate academic peer review through five reviewer roles tailored to the paper's field. Receive separate critiques, an editorial decision, and a prioritized revision roadmap, or check whether a revised manuscript addresses earlier comments.

  • Review a manuscript before journal submission
  • Examine research methods and statistical validity
  • Challenge core arguments and alternative explanations
brycewang-stanford/Auto-Empirical-Research-Skills4.7KUpdated Oct 20, 2026

See all skills by brycewang-stanford

Report a problem with this skill