storybook

Organize and visualize Svelte UI component documentation with CSF-based stories.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/gzp79/shine-web-v2 --skill storybook-gzp79
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: storybook
Source: https://github.com/gzp79/shine-web-v2/tree/main/.claude/skills/storybook
Command: npx skills add https://github.com/gzp79/shine-web-v2 --skill storybook-gzp79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Storybook visualizes and documents UI components, enabling teams to communicate usage and states without heavy code changes.

Core Features & Use Cases

  • CSF-based stories in Svelte using .stories.svelte files and TypeScript, with defineMeta for component metadata.
  • Visual documentation of component states, variants, and design-system guidelines to support design reviewers and developers.
  • Live examples, contextual rendering, and reusable snippets to demonstrate usage in real scenarios.

Quick Start

Create a CSF-style story by defining metadata with defineMeta and a Story that renders your component, then view it in Storybook to document UI.

Frequently Asked Questions about storybook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document Svelte UI components visually in Storybook?

Visual component documentation in Svelte is created using CSF-based .stories.svelte files where you define component metadata with defineMeta and render variants in a Story block to display states and design-system guidelines in Storybook.

What is the best way to show UI component variants and states during design review?

Showing UI component variants during design review is best achieved by creating live Storybook examples that contextually render different component states, enabling teams to communicate usage without heavy code changes.

Does Storybook work with Svelte and TypeScript for design-system documentation?

Storybook supports Svelte and TypeScript for design-system documentation by using CSF-based .stories.svelte files and the defineMeta function to visually document component states, variants, and usage guidelines.

How do I set up a CSF story for a Svelte component?

Setting up a CSF story for a Svelte component requires adding YAML frontmatter with a name and description, defining metadata via defineMeta, and creating a Story block that renders your component to view in Storybook.

When do I need visual documentation for UI components?

You need visual documentation for UI components when you want to demonstrate usage in real scenarios, document design-system guidelines, and support design reviewers and developers during UI development and debugging.