project-setup

Project Setup Skill

Overview

This skill standardizes the initialization of new projects by always asking which architecture skills to apply and providing setup commands instead of generating the project directly. It ensures libraries are installed at their latest versions without hardcoding version numbers that may become outdated.

Keywords: project setup, initialization, scaffolding, new project, boilerplate, create project, setup commands, project structure

Critical Rules

Rule 1: Never Generate Project Files Directly

This skill must NEVER generate project files, create directories, or write code directly.

Instead, always provide the commands the user needs to run in their terminal. The user is responsible for executing these commands in their environment.

Rule 2: Never Hardcode Library Versions

Never specify exact version numbers for libraries or dependencies.

Always use the latest version by omitting the version number or using the appropriate syntax to get the latest:

# Correct - Always gets latest
pnpm add react
pnpm add @nestjs/core
pip install fastapi
composer require laravel/framework

# Incorrect - Version may be outdated
pnpm add [email protected]
pnpm add @nestjs/[email protected]
pip install fastapi==0.109.0
composer require laravel/framework:10.0.0

If the package manager requires a version or the user asks for a specific one, use version ranges:

# Only if necessary
pnpm add react@^18
pnpm add @nestjs/core@^10

Rule 3: Always Ask Which Architecture Skills to Apply

Before providing setup commands, always ask the user which architecture or standards skills they want to apply.

Rule 4: Prefer pnpm Over npm

For any Node.js / JavaScript / TypeScript project, default to pnpm instead of npm.

pnpm is faster, uses a content-addressable store to save disk space, and provides stricter, more reliable dependency resolution. Always provide pnpm commands by default and only fall back to npm (or yarn) if the user explicitly requests it.