storybook

storybook is a skill for Claude Code from fubits1/svelte-skills. It costs 27 tokens per session (788 once invoked), scanned A, original, MIT.

A Storybook workflow for building and checking isolated previews of user-interface components. It covers test data, browser previews, API mocks, and CSS imports, including Svelte-specific cases.

In plain words
What is it for?
Use it to write and preview Storybook stories, provide fixture data, mock APIs, trace CSS imports, and handle Svelte 4 stores or Svelte 5 components.
Why use it?
It helps prevent stories from looking correct while hiding broken data, styles, or interactions. It also gives clear checks for changes that can otherwise fail only in Storybook.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { myWritableStore } from '../stores' // Svelte 4 writable().

Part of the svelte-5 plugin — 7 skills shipped together

Good fit Use it to write and preview Storybook stories, provide fixture data, mock APIs, trace CSS imports, and handle Svelte 4 stores or Svelte 5 components.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/fubits1/svelte-skills
agentmods
npx agentmods add skills/fubits1/svelte-skills/storybook

Made for: Claude Code.

Or install svelte-5, the plugin that ships this one along with the rest of its 7 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for storybook

README.md
[![agentmods](https://agentmods.dev/badge/skills/fubits1/svelte-skills/storybook/github.svg)](https://agentmods.dev/skills/fubits1/svelte-skills/storybook)
Your own site
<a href="https://agentmods.dev/skills/fubits1/svelte-skills/storybook"><img src="https://agentmods.dev/badge/skills/fubits1/svelte-skills/storybook/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for storybook

Your own site · 80×15
<a href="https://agentmods.dev/skills/fubits1/svelte-skills/storybook"><img src="https://agentmods.dev/badge/skills/fubits1/svelte-skills/storybook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 788 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00788
Opus 5 $0.00014 $0.00394
Sonnet 5 $0.00005 $0.00158
Haiku 4.5 $0.00003 $0.00079

Measured 12d ago against content hash 4c0335bdeaad, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

storybook scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/svelte-5/skills/storybook/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Storybook

  • ALWAYS use mcp__storybook__get-storybook-story-instructions before writing stories.
  • ALWAYS use mcp__storybook__preview-stories to preview stories after writing them.
  • Stories use parameters.fixtures for fixture overrides.
  • API mocking (handlers, fixtures, story-scoped overrides, msw-storybook-addon wiring and its v2→v3 break): svelte-5:msw skill.
  • Storybook is usually already running: just navigate with Playwright MCP.
  • Verify every story in the browser via Playwright MCP: don't assume it works.
  • CSS imports: trace chains through BOTH App.svelte AND .storybook/preview.ts. Moving imports out of the SCSS chain breaks Storybook unless also added to preview.ts or storybook.scss.

Svelte 4 writable stores need wrapper components in stories

Components that import and read from Svelte 4 module-level writable() stores (from svelte/store) render with default/ empty data in Storybook unless the stores are populated before the component mounts. This does NOT apply to Svelte 5 runes- based state in .svelte.ts modules, those are reactive on their own.

Pattern: Create a <ComponentName>Wrapper.svelte that:

  1. Calls setContext() for any required Svelte contexts
  2. Calls store.set() with mock data for every Svelte 4 writable() store the component imports
  3. Wraps children in a layout div with sensible dimensions

Use asChild in the story, NEVER decorators for components that depend on Svelte 4 writable stores. Decorators lose complex args (Writable stores, objects with methods) through Storybook's arg serialization.

<!-- stories/MyComponentWrapper.svelte -->
<script lang="ts">
  import { setContext } from 'svelte'
  import { writable } from 'svelte/store'
  import { myWritableStore } from '../stores'  // Svelte 4 writable()
  setContext('myContext', true)
  myWritableStore.set({ /* mock data */ })
</script>
<div style="max-width: 600px; padding: 1rem;">
  <slot />
</div>
<!-- stories/MyComponent.stories.svelte -->
<Story name="Default" asChild>
  <MyComponentWrapper>
    <MyComponent />
  </MyComponentWrapper>
</Story>

Read the full file on GitHub · 86 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 86 lines · 27 tokens per session scan A 4c0335bdeaad

Subscribe to this mod's changes

storybook is a skill published in the GitHub repository fubits1/svelte-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 788 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 52 tokens

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

create-site

Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…

microsoft/power-platform-skills · 73 tokens

prototype-web

A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.

nexu-io/html-anything · 24 tokens

menu-transitions-rtl

Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…

asmyshlyaev177/react-horizontal-scrolling-menu · 137 tokens