Review a Storybook preview

Use this skill to inspect a product repository's own interactive Storybook preview on a phone and report findings tied to the reviewed revision.

Find and identify the preview

In the owning product repository, inspect the Storybook configuration, package scripts, existing CI and preview deployment workflow, and any published URL. Reuse an existing preview or CI artifact before building one. Follow the repository's actual build steps and applicable repository and host instructions for verification, using CI where they require it. Choose a publishing destination below only when publication is part of the authorized task.

Record the repository and exact commit SHA used to build the preview, plus its CI run or deployment ID when available. A pull request merge ref may differ from the pull request head: verify the relationship or state that the preview revision is unverified.

Choose the publishing destination

For an authorized publication without an explicit destination, choose by the user-facing harness, not a delegated implementer's or reviewer's model. Reuse a suitable existing preview rather than migrating it just to apply a default.

• Codex: default to Sites for the complete static Storybook build. Use the available Sites skill and native tools, retain the build's entry points and assets, reuse the selected Site's identity for updates, and start new Sites private. Preserve an existing audience.
• Claude: default to the session's native Artifact tool for a concise review summary with revision provenance and links to the real Storybook manager and relevant story canvases. Keep the artifact private or preserve its existing audience. An Artifact is one self-contained page; relative files are not deployed alongside it, so it cannot directly host an ordinary multi-file Storybook build. Keep that build on existing authorized hosting. If a complete preview is missing, report the hosting gap rather than replacing Storybook with a recreated UI or screenshot gallery.

Preserve explicit user choices and applicable repository instructions. These defaults choose a destination; they do not grant additional publication, public sharing, account, spending, authentication, permission or baseline-promotion authority. Use supported tools and return their actual published URLs. If a provider is unavailable in the current session, use an existing verified preview when possible and state the limitation; do not launch another harness merely to publish or present a local file as a published preview.