Spin up new projects in minutes instead of hours with one slash command.

What it is

Every new project starts with the same 30–60 minutes of boilerplate: folder structure, dependencies, config files, git, CLAUDE.md. With Claude Code skills you do it once — then a single slash command like /new-api or /new-bot handles it.

Install / Setup

Option 1 — Terminal:

mkdir -p ~/.claude/commands
nano ~/.claude/commands/new-api.md

Example new-api.md:

# New API Project

Creates a new Flask API project following my conventions.

## Steps
1. Ask the user for a project name
2. Create folders: app.py, routes/, models/, utils/
3. requirements.txt with flask, httpx, python-dotenv
4. Add .env.example
5. CLAUDE.md with stack info (Flask, SQLite, Python 3.11)
6. git init + first commit "initial: setup flask api"

Option 2 — Prompt Claude Code:

Build me a setup skill "/new-api" that spins up a new Flask API project: folder structure (app.py, routes/, models/, utils/), requirements.txt with flask/httpx/python-dotenv, .env.example, CLAUDE.md with my Python conventions, git init + first commit. Drop it in ~/.claude/commands/new-api.md and show me how to call it.

Use cases

• /new-api — Flask/FastAPI project
• /new-bot — Telegram/Discord bot template
• /new-scraper — Python scraper with Playwright or httpx
• /new-web — Next.js + Tailwind landing page
• /new-skill — Meta skill that scaffolds new skills from a template

Pro tip

Don't build one mega skill that does everything — build 3–4 small ones per project type. Once they're written properly, you skip Google, StackOverflow, and the "what folder structure did I use last time" hunt every single start. Commit the skill files (dotfiles repo) so you have them everywhere.

🚀 Inside the community we build full automation systems and real workflows for your day. → Join the Claude Code Mastery Community

Updated regularly — follow @vine.codes for more.