What problem does it solve? A Storybook dev server that prints its startup banner but cannot be reached from the browser on port 6006 looks like a hang, when the real cause is usually a missing port bridge between the Docker container and the host. This Skill guides you through diagnosing the compose port configuration and launching Storybook where the browser can actually reach it. ## Core Features & Use Cases - Port-mapping diagnosis: Checks whether the compose service publishes the Storybook port and whether the dev server binds 0.0.0.0 instead of loopback inside the container. - Repository-shape guidance: Applies different fixes per shape — React SPA (already publishes 6006), Next.js (use EXEC_MODE=host with the make target), and component-library (run the dev server on the host via the package manager). - Capability gating: Skips cleanly when the repository profile has no Storybook capability, and distinguishes the dev server from the internal static Storybook service used by visual tests. - Use Case: In a component-library repository, make storybook appears to hang because the compose service declares no ports; the Skill directs you to run bun x storybook dev -p 6006 on the host so the browser can connect. ## Quick Start Ask the assistant to figure out why the Storybook dev server is unreachable from the browser on port 6006 and start it in a way that works.
