From limio-skills
Sets up and launches the Limio Storybook component playground with mocked SDK, Claude Prompt addon, and interactive development workflow. Use when user asks to "set up storybook", "launch storybook", "start storybook", "run storybook", "open storybook", "configure storybook playground", or discusses the component-playground environment. Do NOT use for creating components (use limio-component) or creating stories (use limio-story).
How this skill is triggered — by the user, by Claude, or both
Slash command
/limio-skills:limio-storybookThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The component-playground provides a Storybook environment with mocked Limio SDK hooks, a Claude Prompt addon for interactive development, and deployment capabilities.
The component-playground provides a Storybook environment with mocked Limio SDK hooks, a Claude Prompt addon for interactive development, and deployment capabilities.
When setting up Storybook from scratch (no component-playground/.storybook/main.js exists):
.limio.json is in the root .gitignorereferences/storybook-configs.md for all file templatesreferences/sdk-mocks.md for mock implementationsreferences/claude-overlay.md for the overlay componentreferences/addon-prompt.md for manager.js, preset.js, middleware.jsreferences/tool-stories.md for LimioSetup and NewComponent storiesreferences/watch-prompts.md for the watcher scriptcd component-playground && npm installcd component-playground && npx storybook dev -p 6006 (background)node component-playground/scripts/watch-prompts.js (background)When Storybook already exists (quick-launch):
.limio.json is in root .gitignorecd component-playground && npm installcd component-playground && npx storybook dev -p 6006 (background)node component-playground/scripts/watch-prompts.js (background)component-playground/
├── .storybook/
│ ├── main.js # Webpack config with SDK aliases
│ ├── preview.js # Decorators with ClaudeOverlay
│ ├── middleware.js # Express API endpoints
│ ├── claude-overlay.js # Loading/deploy overlay components
│ └── addon-prompt/
│ ├── manager.js # Claude Prompt + Settings panels
│ └── preset.js # Addon registration
├── packages/limio/ # Mocked SDK packages
│ ├── sdk/
│ ├── shop/
│ └── internal-checkout-sdk/
├── scripts/
│ └── watch-prompts.js # File watcher for prompt loop
├── src/stories/ # Story files
│ ├── LimioSetup.stories.js
│ └── NewComponent.stories.js
└── package.json
When the addon already exists, check these markers to determine if it needs updating:
| Feature | File | Marker |
|---|---|---|
| Settings panel | manager.js | SETTINGS_PANEL_ID |
| Deploy endpoint | middleware.js | /api/deploy |
| Limio config | middleware.js | readLimioConfig |
| Build status | middleware.js | /api/build-status |
| Loading overlay | claude-overlay.js | ClaudeOverlay |
| New component tool | NewComponent.stories.js | Tools/New Component |
| Overlay decorator | preview.js | ClaudeOverlay |
| Deploy overlay | claude-overlay.js | DeployOverlay |
| Deploy status | middleware.js | /api/deploy-overlay |
| Smart deploy | middleware.js | smart-deploy |
| Credential safety | root .gitignore | .limio.json |
If any marker is missing, replace both manager.js and middleware.js with current templates.
After starting Storybook and the watcher:
.prompt.jsonnode component-playground/scripts/update-prompt-status.js working "Applying changes..."node component-playground/scripts/update-prompt-status.js completed "Changes applied"| State | Meaning |
|---|---|
listening | Ready for prompts |
queued | Prompt saved, waiting |
received | Watcher picked up prompt |
working | Claude making changes |
completed | Changes applied |
error | Something went wrong |
Root .gitignore — add: .limio.json
component-playground/.gitignore — add: .prompt.json, .prompt-status.json, .deploy-status.json
limio-component — Create componentslimio-story — Create storieslimio-setup — Credentials and deploymentnpx claudepluginhub innovate42/limio-skills --plugin limio-skillsGuides writing, updating, and reviewing Storybook stories with a strict workflow. Pulls story-writing rules from the MCP, ensures a running preview, and prevents unverified stories.
Generates CSF3 Storybook stories for components (React, Vue, shadcn/ui) with variant coverage and state matrices. Invoke when creating component stories.
Integrates Storybook MCP server to discover components via docs manifest, preview stories with embeddable URLs, and run tests/a11y audits. Use for reusing existing components, visual verification, and MCP-based testing in React/Storybook projects.