Accessible React component library built on Tailwind CSS v4 and React Aria with compound component patterns.
Works with
Provides 20+ pre-built components (Button, Modal, Form, Card, TextField, etc.) using compound composition syntax ( Card.Header , Card.Content )
Requires Tailwind CSS v4 and uses CSS variables with oklch color space for theme customization; no provider wrapper needed in v3
Semantic variant system ( primary , secondary , tertiary , danger , ghost , outline ) for consistent inten
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionheroui-reactExecute the skills CLI command in your project's root directory to begin installation:
Fetches heroui-react from heroui-inc/heroui and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate heroui-react. Access via /heroui-react in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
1
total installs
1
this week
28.8K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
28.8K
stars
HeroUI v3 is a component library built on Tailwind CSS v4 and React Aria Components, providing accessible, customizable UI components for React applications.
curl -fsSL https://heroui.com/install | bash -s heroui-react
This guide is for HeroUI v3 ONLY. Do NOT apply v2 patterns — the provider, styling, and component API all changed:
| Feature | v2 (DO NOT USE) | v3 (USE THIS) |
|---|---|---|
| Provider | <HeroUIProvider> required |
No Provider needed |
| Animations | framer-motion package |
CSS-based, no extra deps |
| Component API | Flat props: <Card title="x"> |
Compound: <Card><Card.Header> |
| Styling | Tailwind v3 + @heroui/theme |
Tailwind v4 + @heroui/styles |
| Packages | @heroui/system, @heroui/theme |
@heroui/react, @heroui/styles |
// DO NOT DO THIS - v2 pattern
import { HeroUIProvider } from "@heroui/react";
import { motion } from "framer-motion";
<HeroUIProvider>
<Card title="Product" description="A great product" />
</HeroUIProvider>;
// DO THIS - v3 pattern (no provider, compound components)
import { Card } from "@heroui/react";
<Card>
<Card.Header>
<Card.Title>Product</Card.Title>
<Card.Description>A great product</Card.Description>
</Card.Header>
</Card>;
Always fetch v3 docs before implementing.
primary, secondary, tertiary) over visual descriptionsoklch color spaceFor component details, examples, props, and implementation patterns, always fetch documentation:
# List all available components
node scripts/list_components.mjs
# Get component documentation (MDX)
node scripts/get_component_docs.mjs Button
node scripts/get_component_docs.mjs Button Card TextField
# Get component source code
node scripts/get_source.mjs Button
# Get component CSS styles (BEM classes)
node scripts/get_styles.mjs Button
# Get theme variables
node scripts/get_theme.mjs
# Get non-component docs (guides, releases)
node scripts/get_docs.mjs /docs/react/getting-started/theming
Component docs: https://heroui.com/docs/react/components/{component-name}.mdx
Examples:
https://heroui.com/docs/react/components/button.mdxhttps://heroui.com/docs/react/components/modal.mdxhttps://heroui.com/docs/react/components/form.mdxGetting started guides: https://heroui.com/docs/react/getting-started/{topic}.mdx
Important: Always fetch component docs before implementing. The MDX docs include complete examples, props, anatomy, and API references.
npm i @heroui/styles @heroui/react tailwind-variants
npm i @heroui/styles @heroui/react tailwind-variants tailwindcss @tailwindcss/postcss postcss
app/globals.css:/* Tailwind CSS v4 - Must be first */
@import "tailwindcss";
/* HeroUI v3 styles - Must be after Tailwind */
@import "@heroui/styles";
app/layout.tsx:import "./globals.css";
export default function RootLayout({
children,
}: {
children: React.ReactNode;
}) {
return (
<html lang="en" suppressHydrationWarning>
<body>
{/* No Provider needed in HeroUI v3! */}
{children}
</body>
</html>
);
}
postcss.config.mjs):export default {
plugins: {
"@tailwindcss/postcss": {},
},
};
Card.Header, Card.Content)onPress event handlersAll components use the compound pattern shown above (dot-notation subcomponents like Card.Header, Card.Content). Don't flatten to props — always compose with subcomponents. Fetch component docs for complete anatomy and examples.
HeroUI uses semantic naming to communicate functional intent:
| Variant | Purpose | Usage |
|---|---|---|
primary |
Main action to move forward | 1 per context |
secondary |
Alternative actions | Multiple |
tertiary |
Dismissive actions (cancel, skip) | Sparingly |
danger |
Destructive actions | When needed |
ghost |
Low-emphasis actions | Minimal weight |
outline |
Secondary actions | Bordered style |
Don't use raw colors - semantic variants adapt to themes and accessibility.
HeroUI v3 uses CSS variables with oklch color space:
:root {
--accent: oklch(0.6204 0.195 253.83);
--accent-foreground: var(--snow);
--background: oklch(0.9702 0 0);
--foreground: var(--eclipse);
}
Get current theme variables:
node scripts/get_theme.mjs
Color naming:
--accent)-foreground = text color (e.g., --accent-foreground)Theme switching:
<html class="dark" data-theme="dark"></html>
For detailed theming, fetch: https://heroui.com/docs/react/getting-started/theming.mdx
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
asyrafhussin/agent-skills
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
Registry listing for heroui-react matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for heroui-react matched our evaluation — installs cleanly and behaves as described in the markdown.
heroui-react reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in heroui-react — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend heroui-react for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for heroui-react matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in heroui-react — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in heroui-react — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: heroui-react is the kind of skill you can hand to a new teammate without a long onboarding doc.
heroui-react is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 61