Eve Local Dev Loop

This sets up a local Docker Compose loop that mirrors your Eve staging environment, so you're not debugging environment drift at deploy time. You run Postgres and migrations locally using the same eve-migrate image that runs in production, then npm run dev for hot reload on your API and web apps. The smart bit is keeping compose.yaml and .eve/manifest.yaml in sync so services, ports, and secrets match. When local works, you promote to staging with eve env deploy and track the job. It's opinionated about structure (timestamp-prefixed SQL migrations, Vite proxy config) but that opinion saves you from the usual local-versus-remote config hell.

skills.sh installs: 313
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add incept5/eve-skillpacks --skill eve-local-dev-loop --agent claude-code

Installs into .claude/skills of the current project.

Files

Eve Local Dev Loop (Docker Compose)

Use this skill to run and test the app locally with Docker Compose, then hand off to Eve for staging deploys.

Preconditions

A compose.yaml or docker-compose.yml exists in the repo.
The Eve manifest (.eve/manifest.yaml) reflects the same services and ports.

Local Run

# Start local services (DB + migrations)
docker compose up -d

# Start API in dev mode (hot reload)
cd apps/api && npm run dev

# Start web in dev mode (Vite dev server with /api proxy)
cd apps/web && npm run dev

# View DB logs
docker compose logs -f

# Reset DB (drop + recreate + migrate)
docker compose down -v && docker compose up -d

Recommended docker-compose.yml

Use the Eve-migrate image locally for migration parity with staging:

services:
  db:
    image: postgres:16-alpine
    ports:
      - "5432:5432"
    environment:
      POSTGRES_USER: app
      POSTGRES_PASSWORD: app
      POSTGRES_DB: myapp
    volumes:
      - pgdata:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U app -d myapp"]
      interval: 5s
      timeout: 5s
      retries: 5

SKILL.md on GitHub