Quick Project Scaffolder

Generates a complete project structure with boilerplate files, configuration, and initial setup for any framework or language stack.

When to Use This Command

Run this command when you need to:

• Bootstrap a new project with best-practice directory structure, configuration files, and development tooling for a specific technology stack
• Generate consistent project scaffolding that follows your organization's standards across multiple repositories and teams
• Create starter templates with pre-configured linting, testing, CI/CD pipelines, and documentation structure

Consider alternatives when:

• The framework has its own official scaffolding tool (create-next-app, rails new) that you want to use directly
• You need to add scaffolding to a specific subdirectory of an existing project rather than creating a new project root

Quick Start

Configuration

Copy
name: quick-project-scaffolder
type: command
category: development

Example Invocation

Copy
claude command:run quick-project-scaffolder --stack nextjs-typescript --name my-app

Example Output

Project Scaffolding Report
==========================
Stack: Next.js + TypeScript
Name: my-app
Location: ./my-app/

Generated Structure:
  my-app/
  ├── src/
  │   ├── app/          (App Router pages)
  │   ├── components/   (React components)
  │   ├── hooks/        (Custom hooks)
  │   ├── lib/          (Utilities)
  │   └── types/        (TypeScript types)
  ├── tests/            (Jest + RTL)
  ├── public/           (Static assets)
  ├── .github/workflows/ (CI pipeline)
  ├── package.json      (Dependencies configured)
  ├── tsconfig.json     (Strict mode)
  ├── tailwind.config.ts
  ├── .eslintrc.json
  ├── .prettierrc
  └── README.md

Dependencies installed: 24 packages
Git initialized with initial commit
Ready to develop: cd my-app && npm run dev

Core Concepts

Scaffolding Overview

Aspect	Details
Stack Templates	Pre-defined project structures for common stacks: Next.js, Express, FastAPI, Spring Boot, Rails, Go, Rust, and more
Configuration Files	Generates linting, formatting, testing, and build configuration tuned to the selected stack with strict defaults
CI/CD Pipeline	Creates GitHub Actions or GitLab CI workflow files with build, test, lint, and deploy stages appropriate to the stack
Documentation	Scaffolds README with setup instructions, contributing guide, and architecture overview sections

Scaffolding Workflow

┌──────────────┐     ┌──────────────┐     ┌──────────────┐
│  Select      │────▶│  Generate    │────▶│  Configure   │
│  Stack       │     │  Directory   │     │  Tooling     │
└──────────────┘     └──────────────┘     └──────────────┘
       │                    │                     │
       ▼                    ▼                     ▼
┌──────────────┐     ┌──────────────┐     ┌──────────────┐
│  Install     │────▶│  Initialize  │────▶│  Verify      │
│  Dependencies│     │  Git Repo    │     │  Build Works │
└──────────────┘     └──────────────┘     └──────────────┘

Configuration

Parameter	Type	Default	Description
stack	string	-	Technology stack template to use (e.g., nextjs-typescript, fastapi, spring-boot)
name	string	my-project	Project directory name and package name
package_manager	enum	auto	Package manager: npm, yarn, pnpm, bun, or auto-detect from system
include_ci	boolean	true	Generate CI/CD pipeline configuration files
git_init	boolean	true	Initialize git repository with initial commit

Best Practices

1. Start With Strict Configurations The scaffolder generates strict linting and TypeScript configurations by default. Keep these strict settings and only relax specific rules when you encounter legitimate use cases rather than starting permissive and trying to tighten later.

2. Customize Templates for Your Organization Fork the default stack templates and add your organization's conventions: specific ESLint rules, shared component libraries, internal package registry configuration, and team-specific documentation sections.

3. Include Environment Example Files The scaffolder creates .env.example with all required environment variables documented. Keep this file updated as you add new environment dependencies so new developers can set up quickly.

4. Verify the Generated Build Pipeline After scaffolding, run the full build and test suite immediately to confirm everything works. Fix any issues before writing application code so the generated baseline is always a known-good state.

5. Use Monorepo Templates for Multi-Package Projects For projects that will grow into multiple packages, start with a monorepo template (turborepo, nx) from the beginning rather than trying to restructure a single-package project later.

Common Issues

1. Package manager version mismatch The scaffolder installs dependencies with the detected package manager, but lockfile formats differ between versions. Specify the exact package_manager version or include an .npmrc/.yarnrc with the engine-strict setting to prevent version mismatches across team members.

2. Port conflict on first run The default development server port (3000, 8000, 8080) may already be in use. The scaffolder configures a PORT environment variable in .env.example that developers can override without modifying configuration files.

3. Git hooks not installing automatically If husky or lint-staged is included in the scaffold but hooks do not run, verify that the prepare script in package.json executed during npm install. Run npx husky install manually if the automatic setup was skipped.