agentleFS
mykyta-lytvynenkomykyta-lytvynenko/claude-code-starter-kit/skills/project-setup/SKILL.md

project-setup

Skill0 starsChanged 7 months agoMITView on GitHub

Scaffold a new project: create the folder structure, initialize git, connect to GitHub, and get it to a state where real work can begin. Before creating anything, ask: 1. What is the project name? (used for the folder and repo name — use hyphens, no spaces) 2. What type of project? (Python script / web app / content workspace / data / other) 3. Public or private GitHub repo? 4. Any specific folders or files needed beyond the defaults? Don't…

48 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use creative-writing-craft, creative-writing-muse 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.
  • Abdullokh-NSkill

    creative-writing-craft

    Справочник ремесла: проза, сцена, стиль, голос. Загружать, когда нужно знание "как писать", а не режим производства.

    Also in 3 projects that use this

  • Abdullokh-NSkill

    creative-writing-muse

    Точка входа в набор скилов для длинной прозы. Включается, когда автор просит спланировать, написать, продолжить, переписать или разобрать художественный текст — роман, повесть, цикл рассказов. Ведёт маршрут от замысла к готовому куску и держит базу знаний проекта.

    Also in 3 projects that use this

  • badgidsSkill

    character-sim

    Pressure-test a character by speaking or reasoning strictly from that character's current voice, goals, relationships, emotional pressure, and knowledge boundary without creating canon by accident.

    Also in 3 projects that use this

  • jpsweeney97Skill

    writing-principles

    Enforces writing principles for instruction documents (SKILL.md, skill supporting files, subagents, CLAUDE.md). Use when writing, reviewing, or editing any file in **/skills/**/*.md, **/agents/*.md, or **/CLAUDE.md. Triggers on skill creation, skill file updates, CLAUDE.md changes, subagent authoring, or instruction document review.

    Also in 3 projects that use this

  • ItsSidharthaSkill

    story-planning

    Collaborative planning skill for a GitHub issue. Takes issue content and codebase context as input. Runs an iterative clarification loop until the user explicitly agrees to a plan, then saves it to docs/<story_number>/plan.md. Used by the user-story-implementation skill — load this skill at the start of Phase 1 and follow it completely before returning to the orchestrator.

    Also in 3 projects that use this

  • badgidsSkill

    story-review

    Diagnose existing prose at a chosen editorial level, from whole-story and developmental problems through scene, line, copy, and proof passes, without rewriting until the diagnosis is accepted.

    Also in 3 projects that use this

  • +4 more from Abdullokh-N

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before creating anything, ask:

    line 7
  2. Distinctive:

    Don't start creating files until you have answers to 1 and 3.

    line 13
  3. Distinctive:

    Create this structure under the user's specified base directory:

    line 17
  4. Distinctive:

    Leave the bracketed placeholders for the user to fill in — note which ones need their input.

    line 51
  5. Distinctive:

    Always confirm: "I'm about to create a public GitHub repo at github.com/[username]/[name].

    line 65
  6. Distinctive:

    Don't skip this even if they said public earlier.

    line 67

“Common” is measured: kept by at least 6 in 10 of the 40 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

Skill: Project Setup

Scaffold a new project: create the folder structure, initialize git, connect to GitHub, and get it to a state where real work can begin.

Gather Requirements First

Before creating anything, ask:

  1. What is the project name? (used for the folder and repo name — use hyphens, no spaces)
  2. What type of project? (Python script / web app / content workspace / data / other)
  3. Public or private GitHub repo?
  4. Any specific folders or files needed beyond the defaults?

Don't start creating files until you have answers to 1 and 3. You can infer the rest.

Default Structure

Create this structure under the user's specified base directory:

[project-name]/
├── CLAUDE.md          ← project context (copy from core/CLAUDE.md.template)
├── .gitignore         ← appropriate for the project type
└── README.md          ← one paragraph: what this is and why it exists

For Python projects, also add:

├── src/               ← source code goes here
└── requirements.txt   ← empty, ready to fill

Git + GitHub Steps

cd [project-path]
git init
git add .
git commit -m "Initial project scaffold"
gh repo create [project-name] --[public|private] --source=. --remote=origin --push

Confirm the repo visibility (public/private) with the user before creating. Default is private unless they say otherwise.

CLAUDE.md

Copy core/CLAUDE.md.template into the new project and fill in:

  • Project name and one-line description
  • Working directory path
  • Any external services or tools involved

Leave the bracketed placeholders for the user to fill in — note which ones need their input.

Confirm and Hand Off

Report back:

  • Folder created at: [path]
  • GitHub repo live at: [URL]
  • Files created: [list]
  • What the user needs to fill in: [list of placeholders in CLAUDE.md]

End with: "Ready to start building?"

Before Creating a Public Repo

Always confirm: "I'm about to create a public GitHub repo at github.com/[username]/[name]. Is that right, or should it be private?"

Don't skip this even if they said public earlier. One extra confirmation prevents a hard-to-fix mistake.

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.