adhd-output-style
This skill should be used when the user asks for "ADHD output", "fewer output tokens", "short numbered steps", "limited working…
HeroUI v3 React component library (Tailwind CSS v4 + React Aria). Use when building UIs with HeroUI — creating Buttons, Modals, Forms, Cards; installing @heroui/react; configuring dark/light themes with oklch variables; or fetching component docs. Keywords: HeroUI, Hero UI,
Claude Code
$ npx -y skills add fcakyon/claude-codex-settings --skill heroui-react --agent claude-code
Codex
$ npx skills add fcakyon/claude-codex-settings --skill heroui-react -a codex -y
Cursor
$ npx skills add fcakyon/claude-codex-settings --skill heroui-react -a cursor -y
Gemini CLI
$ npx skills add fcakyon/claude-codex-settings --skill heroui-react -a gemini-cli -y
GitHub Copilot
$ npx skills add fcakyon/claude-codex-settings --skill heroui-react -a github-copilot -y
OpenCode
$ npx skills add fcakyon/claude-codex-settings --skill heroui-react -a opencode -y
Windsurf
$ npx skills add fcakyon/claude-codex-settings --skill heroui-react -a windsurf -y
name: heroui-react description: "HeroUI v3 React component library (Tailwind CSS v4 + React Aria). Use when building UIs with HeroUI — creating Buttons, Modals, Forms, Cards; installing @heroui/react; configuring dark/light themes with oklch variables; or fetching component docs. Keywords: HeroUI, Hero UI, heroui, @heroui/react, @heroui/styles." metadata: author: heroui version: "3.0.1"
> Marketplace adaptation: installation and framework guidance follow the host project.
HeroUI v3 is a component library built on **Tailwind CSS v4** and **React Aria Components**, providing accessible, customizable UI components for React applications.
---
This skill is provided by the marketplace plugin. Install project dependencies using the host project package manager.
---
**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.**
---
---
**For 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: fetch `.mdx` with a concrete kebab-case slug. Run `node scripts/list_components.mjs` when the slug is unknown, and never fetch a URL that still contains a placeholder.
Examples:
Getting started guides: use a concrete topic URL such as `https://heroui.com/docs/react/getting-started/quick-start.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
For a Vite React application, install Tailwind CSS v4 and its Vite plugin alongside HeroUI:
npm install @heroui/react @heroui/styles npm install -D tailwindcss @tailwindcss/vite
Add the Tailwind plugin to the existing Vite configuration, alongside the React plugin:
import tailwindcss from "@tailwindcss/vite";
import react from "@vitejs/plugin-react";
import { defineConfig } from "vite";
export default defineConfig({ plugins: [react(), tailwindcss()] });Import the styles in the application's existing CSS file, with Tailwind first:
@import "tailwindcss"; @import "@heroui/styles";
Import that CSS file from the existing React entry point. HeroUI v3 needs no provider. Use the project's existing framework and package manager when working on an existing app. Vite builds static browser assets that a Go or PocketBase server can serve without Node at runtime.
1. **Tailwind CSS v4 is MANDATORY** - HeroUI v3 will NOT work with Tailwind CSS v3 2. **Use Compound Components** - Components use compound structure (e.g., `Card.Header`, `Card.Content`) 3. **Use onPress, not onClick** - For better accessibility, use `onPress` event handlers 4. **Import Order Matters** - Always import Tailwind CSS before HeroUI styles
---
All 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)
Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support.
This skill should be used when the user asks for "ADHD output", "fewer output tokens", "short numbered steps", "limited working…
This skill should be used when the user asks to "build an AEO strategy", "improve AI search visibility", "track buyer prompts",…
Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating…
Reverse-engineer a website's internal API by recording browser traffic into a HAR file, then generate a standalone client or CLI…
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA",…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.