Skip to content
Back to skills

Project Setup

ASecurity

Set up new projects with proper structure, configuration, and best practices. Use this skill when creating new projects or initializing new codebases.

  • 33 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 10, 2026
developmenttypescriptshellreactnextjsnodegitapidatabase

Works with

  • api

Security analysis

A96/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned February 12, 2026

npx -y skills add lovedragonball/power-ranger-toolkit --skill project-setup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Project Setup?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Project Setup
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/lovedragonball-project-setup/badge)](https://www.skillsdirectory.com/skills/lovedragonball-project-setup)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: project-setup
description: Set up new projects with proper structure, configuration, and best practices. Use this skill when creating new projects or initializing new codebases.
---

# πŸš€ Project Setup Skill

## Web Project Structure

```
πŸ“ project-name/
   πŸ“ src/
      πŸ“ components/    ← UI Components
      πŸ“ pages/         ← Page Components
      πŸ“ hooks/         ← Custom Hooks
      πŸ“ utils/         ← Utility Functions
      πŸ“ types/         ← TypeScript Types
      πŸ“ services/      ← API Services
      πŸ“ stores/        ← State Management
      πŸ“ assets/        ← Images, Fonts
   πŸ“ public/           ← Static files
   πŸ“ tests/            ← Test files
   πŸ“„ .gitignore
   πŸ“„ .env.example
   πŸ“„ package.json
   πŸ“„ README.md
   πŸ“„ tsconfig.json
```

## Essential Files

### .gitignore
```
node_modules/
dist/
.env
*.log
.DS_Store
```

### .env.example
```
# Server
PORT=3000

# Database
DATABASE_URL=

# API Keys (replace with your own)
API_KEY=
```

### package.json scripts
```json
{
  "scripts": {
    "dev": "vite",
    "build": "tsc && vite build",
    "preview": "vite preview",
    "test": "vitest",
    "lint": "eslint src/",
    "format": "prettier --write src/"
  }
}
```

## Setup Checklist

### 1. Initialize
```powershell
# Create project
npx -y create-vite@latest ./ --template react-ts

# Install dependencies
npm install
```

### 2. Configure Linting
```powershell
# ESLint + Prettier
npm install -D eslint prettier eslint-config-prettier
```

### 3. Git Setup
```powershell
git init
git add .
git commit -m "Initial commit"
```

### 4. Environment
```powershell
# Copy example env
Copy-Item .env.example .env
```

## Framework-Specific Setup

### React + Vite
```powershell
npx -y create-vite@latest ./ --template react-ts
```

### Next.js
```powershell
npx -y create-next-app@latest ./ --typescript --tailwind --eslint
```

### Chrome Extension
```
πŸ“ extension/
   πŸ“„ manifest.json   ← V3 manifest
   πŸ“ src/
      πŸ“„ background.js
      πŸ“„ content.js
      πŸ“„ popup.html
```

## Post-Setup Verification

- [ ] `npm run dev` works
- [ ] `npm run build` succeeds
- [ ] `npm run test` passed
- [ ] `.env` is in `.gitignore`
- [ ] README has setup instructions

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…