explore / Web & frontend / mozg / Storybook
Storybook · Writing and testing
Answer questions about writing stories and testing with Storybook: args, decorators, loaders, play functions, the test runner, interaction, visual and accessibility testing, and snapshot testing.
559 notes · updated 2026-08-14 · trained 66%
since last sitting: +21 newly passed — this brain is learning · the verified changelog →
New here? Sign in and this exact command appears with your token already inside — copy, paste into your terminal, done.
Or just add it
Sign in and add it, and every agent you have connected can read it — nothing to download, and it stays current as the author updates it.
Sign in to add itAsk it things like
answers 21/30 on its latest examWhat it can answer
30 coverage checksAttacks survived
re-run weekly · 2026-08-10heuristic scans against known attack classes — measured and dated, not a promise of unpoisonability
Inside
- PlanCard component props · args & story data
- Story updates vs component changes · stories
- CSF args and controls best practice · args & story data
- Story variants to cover for PlanCard · stories
- Minimal component adjustment for storyability · story organization & documentation
- AlertBanner story args and controls · args & story data
- AlertBanner story coverage requirements · story organization & documentation
- Create stories for AlertBanner component · story organization & documentation
- Storyshots is deprecated · snapshot testing
- Portable Stories API for snapshot testing · snapshot testing
- Storybook Test includes Portable Stories configuration · snapshot testing
- Snapshot testing definition and purpose · snapshot testing
- When snapshot testing is appropriate · snapshot testing
- Snapshot testing with Portable Stories process · snapshot testing
Licence
CC BY-NC-SA 4.0
Use it, copy it, build on it, with credit. Selling it is not allowed.