What problem does it solve? After changing a Dockerfile, base image, Node version, or package manager, the dev container often keeps running stale code: tools go missing (exit 127), the dev server throws "Cannot find module" or HTTP 500 for correct code, and dependencies resolve to versions the lockfile no longer pins. This Skill diagnoses and fixes that stale-container state. ## Core Features & Use Cases - Ordered rebuild procedure: Rebuilds the image with docker compose build dev, refreshes named or anonymous node_modules volumes, clears bundler build caches, then restarts and verifies the dev service. - Repository-shape awareness: Adapts the procedure for React SPA, Next.js, and component-library shapes based on profile keys like make.start, make.build, framework.bundler, and framework.package_manager. - Root-owned artifact recovery: Explains how to stop the container and remove root-owned build-artifact directories that a host user cannot delete. - Use Case: After bumping the Node version in the Dockerfile, the dev server returns HTTP 500 despite correct code on disk — follow the procedure to rebuild the image, recreate the module volume, clear the bundler cache, and verify with docker compose ps and a curl health check. ## Quick Start Ask the assistant to rebuild the dev container and refresh stale volumes because the dev server is serving old code after a Dockerfile change.
