'Works on my machine' is the most expensive engineering bug because it never reproduces on the engineer who has to fix it. The team that ships fast is the team where every engineer has the same environment, the local stack matches production closely enough to debug, and a new hire goes from clone to running in under 30 minutes. The team that does not have this loses days per onboarding and weeks per debug session that turns out to be an environment quirk.
The /pave-env skill produces the local development environment. Devcontainer configuration so VS Code spins up the right stack. Docker Compose for the supporting services (database, cache, queue) matched to production behavior. One-command startup script. Documentation that tells the new engineer the three commands they actually need to know.
What the env includes
Four parts. Devcontainer: VS Code dev container with the runtime and tooling pre-installed. Docker Compose: services with images pinned to production versions. Setup script: clone, build, seed, start, with progress visible. Docs: the three commands to know (start, stop, reset).
Tonone's /pave-env skill produces local dev environments with devcontainer, Docker Compose, and one-command startup.
Related skills
Install
/pave-env ships with the Pave agent in Tonone for Claude Code.
1. Add to marketplace
2. Install Pave
Frequently asked questions
- What does /pave-env do?
- It produces the local dev environment with devcontainer, Docker Compose, one-command setup, and documentation.
- How do I install /pave-env?
- Install Tonone for Claude Code via tonone.ai/get-started.