sb-explore

Isolate UI component experiments from production directories in Storybook.

18|Updated Jun 16, 2026

Search Tags:#ui #components #figma #prototyping #storybook #design-system

Ready to run

npx skills add https://github.com/strongeron/storybook-workbench --skill sb-explore

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sb-explore
Source: https://github.com/strongeron/storybook-workbench/tree/main/skills/sb-explore
Command: npx skills add https://github.com/strongeron/storybook-workbench --skill sb-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of design and component drift by providing a dedicated, sandboxed space to iterate on new or redesigned UI components without polluting your production codebase.

Core Features & Use Cases

Isolated Prototyping: Build and test components in a dedicated Explore track that is excluded from production bundles.
Figma Integration: Seamlessly sync Figma frames with Storybook stories to ensure design-to-code fidelity.
Graduation Gate: Use a structured workflow to promote experimental components to production only after they meet stability and design criteria.

Quick Start

Use the sb-explore skill to scaffold a new sandboxed component experiment for the hero section redesign.

Frequently Asked Questions about sb-explore

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

FAQPage Schema

How do I prototype UI components without polluting my production codebase?▼

You can prototype UI components in a sandboxed Explore track that isolates experimental code from production directories, preventing design and component drift. This dedicated space allows you to iterate on redesigns safely.

Does this sandboxed prototyping workflow integrate with Figma and Storybook?▼

Yes, Figma integration syncs Figma frames directly with Storybook stories to ensure design-to-code fidelity. A configured Storybook environment is required to leverage this workflow.

How do I promote an experimental component to production?▼

You promote experimental components through a structured graduation gate workflow. Components are only moved to production directories after they meet specific stability and design criteria.

What is the best way to isolate experimental code for a hero section redesign?▼

The best way is to scaffold a new sandboxed component experiment within the dedicated Explore track. This isolates the hero section redesign code from your main production bundles.

Do I need a specific directory structure for isolated component iteration?▼

Yes, you must adhere to a defined Explore and Labs directory structure. This specific structure ensures experimental components are properly isolated and excluded from production bundles.

Why should I use a sandboxed environment for UI component iteration?▼

You should use a sandboxed environment to prevent design and component drift. It provides a dedicated space to test new components safely before they are promoted to production code.