agentleFS
Sign inStart free
vanthienha199vanthienha199/openclaw-skills/project-kickstart/SKILL.md

project-kickstart

Skill1 starsChanged 8 months agoMITView on GitHub

Scaffold any project in seconds. Generate boilerplate for Next.js, React, Python CLI, Express, FastAPI, static sites, and more. Pre-configured with git, linting, CI, README, and license. Use when the user starts a new project. Triggers on: "new project", "start a project", "scaffold", "create a new app", "init project", "boilerplate", "kickstart".

  • Installs packages

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. cyanluna-git/cyanluna.skills★ 183same name
    2. miovrag/claude-skills★ 1same name
    3. motalim-ai/project-kickstart★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 9

    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:

    When the user describes what they want to build, detect the best stack and generate the project structure with all configuration files.

    line 26
  2. Distinctive:

    Create all files with the appropriate content.

    line 63
  3. Distinctive:

    Write REAL working code, not "TODO" placeholders

    line 89
  4. Distinctive:

    Use the latest stable version of every dependency

    line 90
  5. Distinctive:

    Default to TypeScript for JS projects

    line 91
  6. Distinctive:

    Default to Tailwind for CSS

    line 92
  7. Distinctive:

    Default to MIT license

    line 93
  8. Distinctive:

    Always init git with a clean first commit

    line 94
  9. Distinctive:

    Keep it minimal — don't add auth, database, or features unless asked

    line 95

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

Project Kickstart

You scaffold new projects with best-practice defaults so the user can start coding in 60 seconds.

Core Behavior

When the user describes what they want to build, detect the best stack and generate the project structure with all configuration files.

Supported Stacks

StackTriggerWhat's Generated
Next.js + TypeScript"next app", "react website"next.config.ts, tsconfig, tailwind, eslint, app/ router
React + Vite"react app", "SPA"vite.config, tsconfig, tailwind, src/ structure
Python CLI"python tool", "CLI tool"pyproject.toml, click/typer, src/, tests/
FastAPI"python API", "backend"main.py, requirements.txt, Dockerfile, tests/
Express + TypeScript"node API", "express"tsconfig, src/, routes/, middleware/
Static HTML"landing page", "static site"index.html, styles.css, script.js
OpenClaw Skill"openclaw skill", "agent skill"SKILL.md, README.md with frontmatter

What Every Project Gets

Regardless of stack:

  1. .gitignore — language-appropriate
  2. README.md — project name, description, quick start, license
  3. LICENSE — MIT by default (ask if user wants different)
  4. .github/workflows/ci.yml — basic CI (lint + test)
  5. git init — initialized with first commit

Workflow

Step 1: Ask (if not clear)

What are you building?
1. Web app (Next.js)
2. API (FastAPI/Express)
3. CLI tool (Python)
4. Static site
5. OpenClaw skill
6. Something else (describe it)

Step 2: Generate

Create all files with the appropriate content. Don't use placeholder text — write real, working starter code.

Step 3: Report

Project created: my-awesome-app/

  my-awesome-app/
  ├── .github/workflows/ci.yml
  ├── .gitignore
  ├── LICENSE (MIT)
  ├── README.md
  ├── package.json
  ├── tsconfig.json
  ├── src/
  │   └── app/
  │       ├── layout.tsx
  │       └── page.tsx
  └── tailwind.config.ts

Next steps:
  cd my-awesome-app
  npm install
  npm run dev

Rules

  • Write REAL working code, not "TODO" placeholders
  • Use the latest stable version of every dependency
  • Default to TypeScript for JS projects
  • Default to Tailwind for CSS
  • Default to MIT license
  • Always init git with a clean first commit
  • Keep it minimal — don't add auth, database, or features unless asked

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