agentleFS
Sign inStart free
BibekBhusal0BibekBhusal0/skills/create-project/SKILL.md

create-project

Skill1 starsChanged 59 days agoMITView on GitHub

Use when creating a new project, scaffolding a repo, initializing a repository, bootstrapping boilerplate, or starting a new codebase from scratch. Triggers: new project, create project, new repo, scaffold, boilerplate, initialize project.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use webapp-testing and grill-me.

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.
  • JetBrainsSkill

    webapp-testing

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    Also in 3 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 3

    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:

    Create the project at ~/Code/<name> unless a different path is specified.

    line 12
  2. Very specific:

    When included, add format and lint scripts to package.json and tell the user that build, format, and lint are handled by CI on push.

    line 30
  3. Very specific:

    Write the release notes in release-notes.md.

    line 39
  4. Distinctive:

    Commit and push to main, then wait for the format and lint workflows to pass (if any).

    line 40
  5. Distinctive:

    Always include Tailwind CSS, even for minimal pages.

    line 48
  6. Distinctive:

    If any scaffolded file is adapted from another repository, verify the license allows reuse and credit the source in the new project's …

    line 53

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

Create Project

Scaffold a new project with GitHub remote, baseline files, and CI automation.

Location and remote

  • Create the project at ~/Code/<name> unless a different path is specified.
  • Initialize git and create the GitHub remote with the gh CLI (skip remote setup only if gh is missing or unauthenticated): gh repo create <name> --public --source=. --push
  • Repositories are public unless private is explicitly requested.

Baseline files

Every project gets:

  • README.md: what the project does and how to use it, written for the reader. Keep it user-focused, lead with what the reader can do, and prefer short examples over exhaustive explanations.
  • AGENTS.md: stack, layout, commands, and conventions an agent needs.
  • LICENSE: MIT unless specified otherwise.
  • .gitignore: appropriate for the stack.

Automation

Mirror the standard CI pattern: what CI handles is never done manually.

  • Include lint and formatting workflows only when the project requires them: add lint.yml (runs on pull requests) and format.yml (runs on push to main, auto-commits with chore: ..., pushes) only when the project contains code worth checking. Skip both for docs-only or trivial projects.
  • When included, add format and lint scripts to package.json and tell the user that build, format, and lint are handled by CI on push. Record that hands-off policy in the project's AGENTS.md.

See workflows.md for the reference workflow files.

Releases

Mirror the standard release pattern: version bump plus notes file, published by a manual workflow.

  • Bump the "version" field in the project's version file (package.json, cargo.lock or equivalents). Append a suffix for pre-releases (for example 1.0.0-beta); plain versions are stable releases.
  • Write the release notes in release-notes.md. If the file is missing or empty, no GitHub release is created.
  • Commit and push to main, then wait for the format and lint workflows to pass (if any).
  • Trigger the release workflow manually from the Actions tab. It builds the project (skipped when there is nothing to build), creates the GitHub release from the notes file, then clears release-notes.md.

See workflows.md for the reference release workflow.

Web projects

  • Package manager is Bun (bun init, bun install, bun run).
  • Always include Tailwind CSS, even for minimal pages.
  • Pin GitHub Action versions with commit SHAs.

Credits

If any scaffolded file is adapted from another repository, verify the license allows reuse and credit the source in the new project's README with a repository link, what was taken, and its license. No credit needed for my own projects.

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.

Check your setup, free