heroui-inc/heroui's Claude Code Plugin: What's Actually Inside
By Flowy · Updated 2026-08-28
heroui-inc/heroui is the GitHub repository for HeroUI, a React and React Native UI library formerly called NextUI, with 30,480 stars. Flowy indexes 8 Claude Code components inside it: 3 skills for building interfaces with HeroUI React and HeroUI Native, and 5 agents for maintaining HeroUI's own documentation, Storybook setup, and Tailwind CSS v4 styles.
What is the heroui-inc/heroui plugin, actually
heroui-inc/heroui is the source repository for HeroUI, a React and React Native component library with 30,480 GitHub stars, previously named NextUI. Its own summary describes it as a beautiful, fast, modern UI library. The Claude Code plugin Flowy indexes inside that repository is not the component library itself. It is 8 components, 3 skills and 5 agents, split between two different audiences.
The 3 skills fire when you are building an app with HeroUI's components, in React or React Native. The 5 agents exist for people working on HeroUI's own codebase: writing its documentation, debugging its Storybook setup, or migrating its styling system. Which half matters to you depends on whether you are a HeroUI user or a HeroUI contributor.
The three skills, for building with HeroUI
heroui-react covers the main library: HeroUI v3 for React, built on Tailwind CSS v4 and React Aria. It fires when you are creating buttons, modals, forms, or cards with HeroUI, installing the package, setting up dark and light themes with oklch color variables, or looking up a component's documentation.
heroui-native is the React Native counterpart, styled with Tailwind v4 through Uniwind rather than the web build. It fires for the same kind of work on mobile: buttons, cards, text fields, and dialogs, installing the package, and configuring dark and light themes, plus fetching component docs.
heroui-migration is a reference for moving an existing app from HeroUI v2 to v3: upgrading components and finding the right migration documentation, rather than building something new. Reach for it when a v2 app needs to move forward, not when a project already starts on v3.
The five agents, for working on HeroUI's own codebase
Two of the five are about documentation. docs-curator reviews and improves documentation files inside HeroUI's /apps/docs/content directory: adding practical examples, tightening unclear passages, and keeping code samples consistent with HeroUI v3 patterns. heroui-docs-writer writes documentation rather than editing what exists: component API references, usage examples, installation guides, and migration guides.
The other three are about styling and the build. storybook-debugger fixes problems in HeroUI's own Storybook setup: CSS transformation errors, Tailwind CSS v4 compatibility issues, component styling problems, and build or runtime errors (the indexed description trails off before naming exactly where those runtime errors show up). style-migrator moves HeroUI's own components off TypeScript-based style files that use tailwind-variants and onto plain CSS files that follow the BEM naming convention, converting tv() configurations into CSS classes along the way. tailwind-v4-css-expert analyzes, creates, and debugs Tailwind CSS v4 component CSS files directly; its indexed description also says it helps other agents, including storybook-debugger, though that sentence is cut off before saying with what.
None of these five name a use outside HeroUI's own repository. If you are not editing HeroUI's source, they are unlikely to do anything for you.
Do I need all 8 components, or just the skills
Most people who open this listing want one thing: a way to build a UI with HeroUI's components. That is the 3 skills. The 5 agents are contributor tooling, each scoped to one narrow part of HeroUI's own repository, a docs folder, a Storybook setup, a styles migration, rather than general purpose helpers. Read the two family descriptions above and rely on whichever half matches what you are actually doing.
How do I install it
Flowy indexes heroui-inc/heroui from its public GitHub repository. It does not host, own, or bundle these components. Install from the listing page linked at the top of this guide rather than from a command copied out of this one, since that page generates the current install command from the plugin's own manifest. Once installed, the 3 skills and 5 agents described above become available in that session, though most people building with HeroUI will only need the skills.
Common questions
- What is the heroui-inc/heroui Claude Code plugin for?
- It indexes 8 components from HeroUI's own GitHub repository: 3 skills for building UIs with HeroUI's React and React Native libraries, and 5 agents for working on HeroUI's own codebase, its documentation, its Storybook setup, and its styling system. Most people building an app with HeroUI only need the 3 skills.
- What is the difference between heroui-react and heroui-native?
- heroui-react covers HeroUI v3 for the web, built on Tailwind CSS v4 and React Aria, for creating components like buttons, modals, forms, and cards. heroui-native is the React Native version of the same library, styled through Tailwind v4 via Uniwind instead of the web build, for equivalent mobile components such as buttons, cards, text fields, and dialogs.
- Are the 5 agents useful if I just want to build with HeroUI?
- Not directly. All five, docs-curator, heroui-docs-writer, storybook-debugger, style-migrator, and tailwind-v4-css-expert, are described as tools for working inside HeroUI's own repository: its documentation folder, its Storybook configuration, and its styling system. None of their indexed descriptions mention a use outside that codebase.
- What does the heroui-migration skill do?
- It is a reference for moving an existing HeroUI app from v2 to v3: upgrading components and pointing to the right migration documentation. It is meant for an app already built on v2 that needs to move forward, not for a project already starting on v3.
- How do I install the heroui-inc/heroui plugin through Flowy?
- Flowy indexes it directly from the public heroui-inc/heroui GitHub repository. It does not host or bundle the plugin. Install it from the listing page linked at the top of this guide, since that page generates the current install command from the plugin's own manifest rather than a copy that could drift.