project-setup

Initialize project scaffolds with vitest configuration and environment separation.

Updated Jan 27, 2026

Search Tags:#typescript #vitest #testing #setup #infrastructure #project #environment-separation

Ready to run

npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill project-setup-brunosantanadeveloper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-setup
Source: https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit/tree/main/skills/project-setup
Command: npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill project-setup-brunosantanadeveloper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Project initialization and infrastructure setup to bootstrap a new software project with a solid foundation for testing and environment separation.

Core Features & Use Cases

Base scaffolding: Create a ready-to-use project structure with src, tests, and config templates.
Test runner setup: Configure vitest and related tooling for immediate TDD workflows.
Environment separation: Enforce development vs production environment guidelines and .env handling.

Quick Start

Run the /new-project command to scaffold a ready-to-use base project with environment separation.

Frequently Asked Questions about project-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up a new TypeScript project with vitest and environment separation?▼

You can scaffold a clean TypeScript project with vitest by initializing a base folder structure for src, tests, and config templates, while enforcing development versus production environment guidelines. This provides immediate test runner integration and mandatory .env handling.

What is the best way to configure vitest for a test-driven development workflow?▼

Configuring vitest for test-driven development involves integrating the test runner during project initialization. This establishes a ready-to-use base scaffold with src and tests directories, enabling immediate TDD workflows alongside proper environment separation.

Can I use this project scaffolding method for legacy migrations and feature expansions?▼

Yes, this initialization approach applies to new web and mobile projects, legacy migrations, and feature expansions. It specifies stack-based initialization commands to create a formal test environment and required folder structure.

Do I need to manually configure environment separation when bootstrapping a project?▼

No, manual configuration is unnecessary because the scaffolding enforces development versus production environment guidelines. It automatically handles .env file separation to ensure a clean infrastructure setup.

Why does my project initialization lack a formal test environment?▼

Your project lacks a formal test environment because it was initialized without stack-based commands and test runner integration. Applying a clean project scaffold with vitest configuration enforces this required structure.

What's included in a clean project scaffold with infrastructure setup?▼

A clean project scaffold includes a ready-to-use folder structure with src, tests, and config templates. It also provides test runner integration via vitest and mandatory environment separation guidelines for development and production.