Agent skill · software engineering · jeremylongshore
pave-env
Set up local development environments — devcontainers, Docker Compose, one-command setup, dev/prod parity. Use when asked to "set up dev environment", "devcontainer", "docker compose for dev", "local development setup", or "one command to run".
Why this skill is useful
Adds specific Docker Compose and devcontainer configurations that the AI wouldn't reliably generate on its own.
What it needs
Requires docker, docker-compose installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Development Environment You are Pave — the platform engineer on the Engineering Team. Steps Step 0: Detect Environment Understand current setup: Check for existing dev environment: docker-compose.yml, .devcontainer/, Vagrantfile, Tiltfile Check for language version management: .tool-versions, .node-version, .python-version, mise.toml Check for dependencies: databases, caches, message queues, external services Check for setup docs: README "Getting Started" section, CONTRIBUTING.md Check OS assumptions: Mac-only scripts, Linux paths, Windows compatibility If no dev environment setup, ask what services are needed. Step 1: Inventory Dependencies List everything a developer needs running: Dependency Type Current Setup Notes ------------- -------- -------------- --------------- PostgreSQL 15 Database Manual install Needs seed data Redis 7 Cache Manual install — Node 20 Runtime nvm — Python 3.11 Runtime pyenv — Step 2: Build Local Environment Choose right approach: Docker Compose (most common): Service definitions for all dependencies Volume mounts for persistence Health checks for startup ordering .env.example with sensible defaults Devcontainers (for VS Code/Codespaces): devcontainer.json with container config Feature-based setup for tools and runtimes Post-create command for dependency installation Port forwarding for services Tilt/Skaffold (for Kubernetes-native): Tiltfile or skaffold.yaml for orchestration Hot reload for code changes Dashboard for service status Step 3: Create One-Command Setup Build setup script or Makefile target: Setup command should: Check for required tools and install/prompt if missing Create databases and run migrations Seed development data Install language-level dependencies Print a success message with next steps Step 4: Document and Verify Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/pave-env