pave-env

Automate local development environment setup with devcontainers and Docker Compose.

69|8|Updated Mar 16, 2026

Search Tags:#devops #iac #docker-compose #devcontainer #local-development #parity #environment-setup

Ready to run

npx skills add https://github.com/tonone-ai/tonone --skill pave-env

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pave-env
Source: https://github.com/tonone-ai/tonone/tree/main/team/pave/skills/pave-env
Command: npx skills add https://github.com/tonone-ai/tonone --skill pave-env

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating and reproducing local development environments across teams and machines is error-prone and time-consuming. This Skill provides a consistent, repeatable setup using devcontainers, Docker Compose, and a single-command workflow to eliminate drift and onboarding friction.

Core Features & Use Cases

Devcontainer support for consistent IDE and runtime environments across editors and machines.
Docker Compose to spin up multi-service stacks locally with parity to production.
One-command setup to bootstrap dependencies, databases, and tooling, reducing setup time for new projects or contributors.
Dev/prod parity guidance to ensure local development mirrors production behavior and configurations.

Quick Start

Run the one-command setup to initialize your local development environment.

Frequently Asked Questions about pave-env

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

FAQPage Schema

How do I set up a local development environment with one command?▼

A one-command setup automates local development environment configuration by initializing devcontainers and Docker Compose. This bootstraps project dependencies, databases, and tooling to eliminate manual setup errors and onboarding friction.

What is dev/prod parity and how do devcontainers help achieve it?▼

Dev/prod parity means your local development environment mirrors production behavior. Devcontainers provide consistent IDE and runtime environments across machines, while Docker Compose spins up multi-service stacks to match production configurations.

Do I need Docker and devcontainer support to use this environment setup?▼

Yes, Docker and devcontainer support are required. The environment setup relies on these project-local tools and configurations to implement and verify the automated dev/prod parity workflow.

How do I spin up multi-service stacks locally with Docker Compose?▼

Docker Compose spins up multi-service stacks locally to achieve parity with production. The one-command setup bootstraps necessary dependencies and tooling to run the full stack consistently across different machines.

Why does my local development environment drift from production?▼

Local development environments drift from production due to inconsistent manual configurations across machines. Using devcontainers and Docker Compose provides a repeatable setup that eliminates drift and ensures dev/prod parity.