review-storybook

Featured

Review Paperclip stories for a feature or change using the Storybook catalog, production source, and existing browser tests. Report component, mock, interaction, and visual evidence separately.

AI & Automation 114,742 stars 19046 forks Updated today MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Review Storybook Read the [catalog contract](../../../maps/storybook-map/README.md) and find the requested capability in its generated index. Check the relevant feature recipe, production subject, and story before driving it. Catalog status is prior review context, not proof of the current revision. This skill consumes the maps/catalog; corrections belong to `maintain-storybook` or `maintain-verification-skill`. Choose discriminating states for the requested change: the normal action and result, relevant failure/retry, gate/permission presentation, and mobile/theme variants where affected. Record chosen files/exports and omitted scope. For a full source review, account for every file; do not describe sampling as full render or interaction coverage. When reviewing navigation/index changes, compare the guide and sidebar with the full ordered index generated from feature recipes' navigation metadata. Open a feature without examples and a feature whose related suite lives elsewhere; check capability order, gap messages, classifications, recipe links, and actual suite navigation. Compare built entry IDs before/after so existing links survive. Generated Overview pages do not establish new example coverage. Use [the existing Storybook commands](../../../doc/DEVELOPING.md#storybook): `pnpm build-storybook`, or an owned Storybook dev server on an available local port. Use the built `ui/storybook-static/index.json` for actual story IDs and links. Do not trust an unrelated server ...

Details

Author
paperclipai
Repository
paperclipai/paperclip
Created
8 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

maintain-storybook

Keep Paperclip stories and their downstream catalog aligned with the feature map and production UI. Use to reconcile story drift, classify prototypes, update fixtures, or maintain feature coverage.

114,742 Updated today
paperclipai
Web & Frontend Listed

storybook

Scaffolds, audits, and tests Storybook stories for React (web) and React Native / Expo (native) component libraries. Generates three artefacts in two files per invocation: a visual regression `*.stories.tsx` file containing a `Default` story (variants grouped into a single snapshot) and a `Playground` story (interactive `args` / `argTypes`), plus a sibling `*.test.stories.tsx` interaction test file under a `/Tests` namespace. Supports an opt-in, per-pathname auth flow whose credentials live in the OS keychain (not in the repo). Iteration loop uses the Playwright CLI against the running Storybook URL; visual evidence delegates to the `pr-reviewer` agent and the `screen-recorder` skill. An opt-in `--validate` phase drives Playwright adversarially against the rendered story to find edge cases and break the component, then fixes the defects it finds behind a confidence gate. Triggers on "scaffold stories", "add storybook", "story for this component", "interaction test for this story", "validate this story", "/sto

21 Updated today
mthines
Code & Development Listed

code-review

Review code changes adversarially. Use when the user says "review", "code review", or "review story {X}". Also run by the lw-story-reviewer subagent after every /dev-story, as the independent review.

2 Updated yesterday
rterakedis