Audit React and Vite components by import and call-site usage.
npx skills add https://github.com/strongeron/storybook-workbench --skill sb-inventory
Please help me install this Agent Skill. Skill: sb-inventory Source: https://github.com/strongeron/storybook-workbench/tree/main/skills/sb-inventory Command: npx skills add https://github.com/strongeron/storybook-workbench --skill sb-inventory
This skill eliminates the guesswork and drift inherent in documentation like AGENTS.md or DESIGN.md by providing a ground-truth audit of what components are actually imported and rendered in your React+Vite application.
Run the inventory-project script to generate the project-inventory.json file and audit your component usage.
High-intent search queries and answers about installing and using this skill.
To detect dead React components, run an audit script that analyzes actual import and call-site usage to distinguish active components from dead slop. This generates a comprehensive JSON inventory mapping component usage and nesting hierarchies.
You can audit design system adoption by analyzing actual code signals to detect your dominant design system, such as Tailwind or shadcn. This provides a ground-truth audit of what components are actually imported and rendered.
Yes, you need Python3 and Bash to execute the discovery scripts that audit your React component usage. These scripts analyze your Vite application and produce atomic JSON artifacts for consumption.
The best way to generate a component inventory is to run a script that analyzes actual import and call-site usage. This creates a searchable inventory ranked by usage, including nesting hierarchies and specific page appearances.
You map component-to-page relationships by analyzing import graphs and call-site usage across your codebase. This generates a data-driven inventory detailing the specific pages where each active component appears.
Yes, you can identify dead code in a Storybook project by auditing your React and Vite application to distinguish between actively imported components and unused slop. The audit relies on actual call-site usage rather than documentation.
strongeronExtract route maps, navigation edges, and UI chrome from React and Vite codebases.
alissimoreApply Nexus design system and Tailwind CSS tokens to UI components.
not-subhuRun a Vite dev server for live UI component previews on the canvas.
EvaLokEstablish best practices for developer tools using AST parsers over regex.
