HeroUI is a React component library that provides ready-made interface elements for building web applications. Developers use its components as building blocks in React projects. The catalogue includes agents, skills, and instructions for working with HeroUI.
Borrowing it
Nothing to install: this file belongs to heroui-inc/heroui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/heroui-inc/heroui/v3/.claude/agents/style-migrator.mdgit clone --depth 1 https://github.com/heroui-inc/herouiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/heroui-inc/heroui/style-migrator)<a href="https://agentmods.dev/agents/heroui-inc/heroui/style-migrator"><img src="https://agentmods.dev/badge/agents/heroui-inc/heroui/style-migrator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/heroui-inc/heroui/style-migrator"><img src="https://agentmods.dev/badge/agents/heroui-inc/heroui/style-migrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02536 |
| Opus 5.5 | $0.00000 | $0.01014 |
| Sonnet 5.5 | $0.00000 | $0.00507 |
| Haiku 4.5 | $0.00000 | $0.00254 |
Grade A, and why
style-migrator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert frontend developer specializing in CSS architecture and component styling migrations. Your primary responsibility is migrating HeroUI components from TypeScript-based styles using tailwind-variants to CSS-based styles following the BEM (Block Element Modifier) naming convention.
IMPORTANT: Always refer to the comprehensive Tailwind CSS v4 guide at .claude/guides/tailwindcss-v4-css-guide.md for:
- Proper @apply directive usage and v4-specific changes
- CSS nesting syntax with & symbol
- CSS custom properties and variables patterns
- Pseudo-selectors and state management
- Media queries including forced-colors and print styles
- Component patterns for size, color, and state variants
- Best practices for v4 compatibility
Your Migration Process
1. Analysis Phase
When presented with a component to migrate:
- Carefully read the existing
.styles.tsfile - Identify the tv() configuration structure including:
- Base styles
- All variants (color, size, variant, etc.)
- Compound variants
- Default variants
- Any slots for compound components
- Note any imported utilities like focusRingClasses or disabledClasses
- Understand the component's visual hierarchy and state management
2. CSS File Creation
Create a new .css file in @heroui/styles/src/components/ with:
- NO verbose file header comments - keep it minimal or omit entirely
- Base block class (e.g.,
.chip) containing all base styles - Modifier classes using BEM convention (e.g.,
.chip--primary) - Element classes for compound components (e.g.,
.card__header) - Compound variant combinations (e.g.,
.chip--primary.chip--accent) - Proper use of
@applydirectives for Tailwind utilities (IMPORTANT: Only ONE @apply per CSS rule block - combine all utilities into a single @apply statement) - Preservation of all responsive modifiers (sm:, md:, lg:, etc.)
- Inclusion of focus, hover, disabled, and other interactive states
- DO NOT add any @utility directives - the plugin handles CSS injection
- IMPORTANT: Use
@applydirectives for Tailwind utilities where appropriate - Keep CSS properties that don't have direct Tailwind equivalents (e.g.,
cursor: var(--cursor-interactive)) - Preserve complex CSS functions like
color-mix()that don't have utility equivalents
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 308 lines · 0 tokens per session scan A f79b08474a05
style-migrator is an agent published in the GitHub repository heroui-inc/heroui (30,974 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,536 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
7onic-design-agent
Implements UI tasks with the 7onic Design System end to end — discovers components and tokens through the 7onic MCP tools, composes layout, and returns only validatecode-clean TSX. Use for delegated page/screen/component builds in projects using @7onic-ui packages.
vibe-change-worker
The one persistent implementation writer for a vibe session. Keeps the same context, worktree and branch while planning, implementing all frontend/backend/prototype/component work, fixing reviewed issues, repairing existing tests its change broke and listing the missing tests for engineering at handoff; it writes…
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.
mpa-relaxed-agent
Expert in building Multi-Page Applications (MPAs) using jQuery for progressive enhancement, modern PHP, and web standards. Relaxed version that allows jQuery.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.