setup-dev-env
Set up development environments automatically
Manual development environment setup is time-consuming and error-prone. This skill automates dependency installation, database initialization, and environment configuration for consistent, reproducible development environments.
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "setup-dev-env". Set up the complete development environment
Resultado esperado:
- Backend: Java 21 confirmed, Gradle dependencies installed, build successful
- Frontend: Node.js 20 confirmed, pnpm dependencies installed, build successful
- Database: PostgreSQL started, Flyway migrations completed
- Environment: backend/.env and frontend/.env.local verified
- Ready to start: cd backend && ./gradlew bootRun or cd frontend && pnpm dev
A utilizar "setup-dev-env". Verify the current development environment status
Resultado esperado:
- Java: Version 21.0.2 detected - meets requirement
- Node.js: Version 20.10.0 detected - meets requirement
- pnpm: Version 8.14.0 detected - meets requirement
- Docker: Version 24.0.7 detected - meets requirement
- Docker Compose: Version 2.23.3 detected - meets requirement
- All required tools are properly installed
A utilizar "setup-dev-env". Reset the database environment
Resultado esperado:
- Stopping existing database container
- Starting fresh PostgreSQL container with Docker Compose
- Waiting for database to become available
- Running Flyway baseline migration
- Running all migration scripts
- Database reset complete and verified
Auditoria de Segurança
SeguroThis is a documentation-only skill containing markdown documentation for development environment setup procedures. No executable code, scripts, or network operations exist. The bash commands shown are illustrative examples within code blocks, not runtime code. All static findings are false positives: hidden file references are read-only ls commands for verification, cryptographic algorithm alerts are scanner artifacts from Japanese text, and external command alerts are documentation code blocks that cannot be executed.
Fatores de risco
🌐 Acesso à rede (1)
📁 Acesso ao sistema de arquivos (9)
Pontuação de qualidade
O Que Você Pode Construir
Onboard quickly
Get new developers productive on day one with automated, consistent environment setup
Standardize environments
Ensure all team members have identical development environments across machines
Reduce setup time
Eliminate manual environment configuration overhead for new project starts
Tente Estes Prompts
Set up the complete development environment for this project using the setup-dev-env skill. Include backend dependencies, frontend dependencies, and database setup.
Set up only the backend development environment. Run Gradle build and verify database connectivity.
Reset the database environment using Docker Compose and run all Flyway migrations from scratch.
Verify the current development environment status. Check all tool versions and confirm dependencies are properly installed.
Melhores Práticas
- Run the skill after cloning a fresh repository to ensure all dependencies are installed
- Verify environment variables match between backend/.env and frontend/.env.local
- Use the full setup workflow when onboarding new team members
Evitar
- Running setup without checking pre-installed runtime versions first
- Skipping database setup and expecting the application to work
- Modifying environment files while the database container is running