What problem does it solve? When a project has no demo configuration, the /demo command seeds starter files and aborts, leaving the user to figure out the correct launch command, port, and VM image setup. This Skill inspects the repository, proposes a candidate launch command, confirms it with the user, and then fills in .junie/demo.md and .junie/vms/<vm>/Dockerfile correctly. ## Core Features & Use Cases - Repository inspection: Detects the dev/start command, runtime, package manager, and port from manifests like package.json, lockfiles, pyproject.toml, go.mod, or Gemfile. - Confirmation-first workflow: Never writes files before the user approves the proposed launch command, preventing wrong guesses from being committed. - Dockerfile derivation and verification: Extends the official demo base image with only the layers the confirmed command needs, then builds the image with BuildKit to catch errors early. - Use Case: After running /demo on a Nuxt project for the first time and seeing it abort, ask the agent to finish the setup; it detects pnpm dev, confirms port 3000 with you, writes demo.md, and validates the Dockerfile build. ## Quick Start Ask the agent to set up and finish the /demo configuration for this project by inspecting the repo and confirming the launch command with you.