components

Discovers and catalogs design system components from Storybook or static code analysis.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/fullya99/simple-blog-page --skill components-fullya99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: components
Source: https://github.com/fullya99/simple-blog-page/tree/main/.claude/skills/gstack/components
Command: npx skills add https://github.com/fullya99/simple-blog-page --skill components-fullya99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose track of existing UI components and end up duplicating work by rebuilding buttons, modals, or cards that already exist in the codebase. This Skill scans your project to build a searchable component catalog so you can reuse what exists before writing new UI. ## Core Features & Use Cases - Component Discovery: Detects components via Storybook MCP tools when available, falling back to static analysis of .tsx, .jsx, .vue, and .svelte files. - Searchable Catalog: Extracts component names, props interfaces, variants, dependencies, and file paths, organized by category (Layout, Forms, Feedback, Data Display, Actions). - Duplication Detection: Before creating a new component, compares it against the catalog using name similarity and functional overlap, then suggests extending an existing component instead. - Use Case: Before building a new Dialog component, run the skill to discover an existing Modal in src/components with the variants you need, then extend it rather than duplicating code. ## Quick Start Ask the assistant to list all components in this project and show the props and usage for the Button component.

Frequently Asked Questions about components

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

FAQPage Schema
How do I find existing components in a React codebase?▼

Run the components skill to scan src/components, app/components, and similar directories for exported components and their Props interfaces. It builds a catalog with names, props, variants, and file paths you can search by keyword.

How to list Storybook components programmatically?▼

If Storybook MCP tools are available, the skill uses them to list all stories with props, variants, and documentation. This is the preferred source since Storybook metadata is more complete than static analysis.

Does component discovery work without Storybook?▼

Yes, static analysis is the fallback. The skill scans .tsx, .jsx, .vue, and .svelte files, parses export statements and Props interfaces, and detects variants from union type props like variant: "primary" | "secondary".

How do I avoid creating duplicate UI components?▼

Before creating a new component, the skill compares your intent against the catalog using name similarity and functional overlap. If a match exists, it suggests extending the existing component with its current variants instead.

Can this skill modify or refactor my components?▼

No, the skill is strictly read-only. It only reads files and reports findings, never modifying source code. Use it for discovery and analysis, then make changes manually or with a separate editing workflow.