brycewang-stanford/Auto-Empirical-Research-Skills / skills/13-scunning1975-MixtapeTools/skills/newproject
newproject
VerifiedScaffold 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.
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
-
Get the project name from the argument. If none provided, ask.
- Convert spaces to hyphens, lowercase
-
Determine location — default is current working directory. Confirm if unclear.
-
Create all directories:
mkdir -p [project-name]/{code/{R,stata,python},data/{raw,clean},output/{figures,tables},documents,decks,notes,progress_logs} -
Copy CLAUDE.md from
~/mixtapetools/claude/CLAUDE.md:- Replace
[Your Name]withScott - Update project name in the overview section
- Replace
-
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 ``` -
Create initial progress log at
progress_logs/YYYY-MM-DD_setup.md:- Record the creation date
- List next steps as a checklist
-
Report success — show structure with
ls, remind user to update CLAUDE.md.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |