$npx -y skills add faizkhairi/claude-code-blueprint --skill scaffold-projectScaffold a new project with standard structure, configs, and CLAUDE.md
| 1 | > **Before using:** Replace `{PROJECTS_ROOT}` and `{BOILERPLATE_NAME}` with your actual paths in your copy of this skill. (`./memory/` is the built-in memory folder, no replacement needed.) |
| 2 | > |
| 3 | > **Example only, these scaffolds target JS/TS stacks** (Nuxt, Next, Node, npm library). This is a project generator, so its type menu is intentionally stack-specific. Replace the `type:` list and the per-type steps below with your own stack's scaffolds, such as `rails new`, `django-admin startproject`, `cargo new`, `dotnet new`, `go mod init`, `mvn archetype:generate`, etc. |
| 4 | |
| 5 | Initialize a new project at {PROJECTS_ROOT}/$ARGUMENTS: |
| 6 | |
| 7 | 1. **Parse arguments**: Extract project name and type (default: nuxt) |
| 8 | |
| 9 | 2. **Create project** based on type (before copying any boilerplate: verify the template directory exists with `test -d`. If missing, fall back to framework CLI scaffolding, such as npx nuxi, npx create-next-app, etc.): |
| 10 | - **nuxt** (or from template): Use `{PROJECTS_ROOT}/{BOILERPLATE_NAME}` as template, copy or clone into new directory, then replace app name in package.json/README. Alternatively: `npx nuxi@latest init [name]` then add Tailwind, Prisma, Vitest. |
| 11 | - **next**: Use `{PROJECTS_ROOT}/{BOILERPLATE_NAME}` as template, copy into new directory, update package name and README. |
| 12 | - **vue-springboot**: Use `{PROJECTS_ROOT}/{BOILERPLATE_NAME}` as template, copy into new directory, update backend/frontend names and README. |
| 13 | - **expo**: Use `{PROJECTS_ROOT}/{BOILERPLATE_NAME}` as template, copy into new directory, update app.json name and README. |
| 14 | - **node**: Create Express/Fastify project with TypeScript, Prisma, Vitest |
| 15 | - **library**: Create npm package with TypeScript, Vitest, tsup bundler |
| 16 | |
| 17 | 3. **When using a boilerplate template**: Copy the template folder to {PROJECTS_ROOT}/[project-name], then update any project-specific names (package.json name, README title, app.json slug, etc.). Skip step 4 if template already has CLAUDE.md and .env.example. |
| 18 | |
| 19 | 4. **Generate standard files** (if not from template or if template is minimal): |
| 20 | - `CLAUDE.md` with project-specific instructions, commands, and stack description |
| 21 | - `.env.example` with required environment variables |
| 22 | - `.gitignore` tailored to the stack |
| 23 | - `vitest.config.ts` with sensible defaults (for JS/TS projects) |
| 24 | |
| 25 | 5. **Initialize git**: `git init` and create initial commit (if not already a git repo) |
| 26 | |
| 27 | 6. **Register in memory**: Create project entry in `./memory/projects/active/` using the coding template at `./memory/templates/coding-template.md` |
| 28 | |
| 29 | 7. **Report**: Show project structure and next steps. For templates, remind user to set env vars (e.g. DATABASE_URL, NEXTAUTH_SECRET, JWT_SECRET) per template README. |