agentleFS
flonatflonat/flonat-research/skills/init-project/SKILL.md

init-project

Skill150 starsChanged 9 days agoMITView on GitHub

Bootstrap a new research project. Interview for details, scaffold directory structure, create Overleaf symlink, initialise git, and create project context files.

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 42 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Ask the user these questions using AskUserQuestion (adapt based on what's already known):

    line 16
  2. Distinctive:

    Create the directory structure:

    line 29
  3. Distinctive:

    Update the central context library:

    line 96
  4. Very specific:

    Add the project to .context/projects/_index.md

    line 97
  5. Very specific:

    Create .context/projects/papers/<project-name>.md with metadata

    line 98

“Common” is measured: kept by at least 6 in 10 of the 42 edited versions of this file we could read. “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
SKILL.md

Init Project — Research Project Scaffolder

Interactive project setup: answer questions, get a ready-to-use research project directory.

Protocol

Phase 1: Interview

Ask the user these questions using AskUserQuestion (adapt based on what's already known):

  1. Project name — short name for the directory (e.g., nudge-experiment)
  2. Paper title — working title for the paper
  3. Research question — one sentence
  4. Target journal/venue — where you plan to submit
  5. Co-authors — names and affiliations (if any)
  6. Parent directory — where to create the project (default: ~/Research/)
  7. Overleaf path — path to Overleaf-synced directory for symlink (optional)
  8. Methodology — experimental, observational, theoretical, simulation, mixed

Phase 2: Scaffold

Create the directory structure:

<project-name>/
├── CLAUDE.md               # Project-specific Claude instructions
├── README.md               # Project overview
├── MEMORY.md               # Knowledge base (seeded with template)
├── paper/                  # → Overleaf symlink (or empty dir)
├── code/
│   ├── python/             # Python scripts
│   └── R/                  # R scripts
├── data/
│   ├── raw/                # Original data (never modified)
│   └── processed/          # Cleaned/transformed data
├── results/                # Analysis outputs
├── figures/                # Generated figures
├── docs/                   # Project documentation
├── correspondence/         # Referee reports, cover letters
│   └── referee2/           # Referee 2 agent reports
├── log/                    # Session logs
│   └── plans/              # Saved plans
└── .gitignore

Phase 3: Populate Files

CLAUDE.md — project-specific instructions:

  • Paper title and research question
  • Co-authors and target venue
  • Methodology and key conventions
  • Pointer to project context files

README.md — human-readable overview:

  • Project title and description
  • Directory structure explanation
  • How to compile the paper
  • Co-author information

MEMORY.md — seeded with research project template:

  • Notation Registry (empty)
  • Estimand Registry (empty)
  • Key Decisions (empty)
  • Citations (empty)
  • Anti-Patterns (empty)
  • Code Pitfalls (empty)

.gitignore — standard research project ignores:

  • Build artifacts (out/, *.aux, *.log)
  • Data files (data/raw/*.csv, data/raw/*.xlsx)
  • Python/R artifacts (__pycache__/, .Rhistory)
  • OS files (.DS_Store)

Phase 4: Git & Symlinks

  1. Overleaf symlink — if a path was provided:
    ln -s /path/to/overleaf/dir paper
  2. Git init — initialise the repository:
    git init
    git add .
    git commit -m "Initial project scaffold"

Phase 5: Context Update

Update the central context library:

  1. Add the project to .context/projects/_index.md
  2. Create .context/projects/papers/<project-name>.md with metadata

Output

Print a summary of what was created:

Project created: ~/Research/<project-name>/
  Directories: 12
  Files: 4 (CLAUDE.md, README.md, MEMORY.md, .gitignore)
  Overleaf: linked / not configured
  Git: initialised with initial commit

Next steps:
  1. Start writing in paper/ (or link Overleaf)
  2. Add code to code/python/ or code/R/
  3. Run session-log when you finish working

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.