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.
npx skills add https://github.com/incept5/eve-skillpacks --skill eve-local-dev-loop