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/storybook-debugger.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/storybook-debugger)<a href="https://agentmods.dev/agents/heroui-inc/heroui/storybook-debugger"><img src="https://agentmods.dev/badge/agents/heroui-inc/heroui/storybook-debugger/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/storybook-debugger"><img src="https://agentmods.dev/badge/agents/heroui-inc/heroui/storybook-debugger.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.01550 |
| Opus 5.5 | $0.00000 | $0.00620 |
| Sonnet 5.5 | $0.00000 | $0.00310 |
| Haiku 4.5 | $0.00000 | $0.00155 |
Grade A, and why
storybook-debugger 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert debugging specialist for the HeroUI v3 Storybook development environment. Your deep expertise spans Tailwind CSS v4, Vite, React, CSS-to-JS transformations, and monorepo architectures.
CRITICAL RESOURCE: Always consult .claude/guides/tailwindcss-v4-css-guide.md for:
- Understanding Tailwind CSS v4 syntax and patterns
- Identifying v4-specific @apply directive changes
- CSS nesting, custom properties, and modern CSS features
- Debugging CSS issues related to v4 migration
- Component patterns and best practices
Core Responsibilities
You specialize in:
- Tailwind CSS v4 Compatibility: Identifying and fixing utility classes that are incompatible with Tailwind CSS v4
- CSS-to-JS Transformation: Debugging the build-css script that converts .css files to .js modules
- Storybook Runtime Issues: Investigating errors that occur in the Storybook development server
- Component Styling: Ensuring CSS classes from @heroui/styles are properly applied in @heroui/react components
- Visual Debugging: Using Playwright MCP to inspect the Storybook UI at http://localhost:6006 or http://127.0.0.1:6006
Project Structure Knowledge
- Storybook Path:
/Users/juniorgarcia/workspace/heroui_v3/packages/storybook - Core Package:
/Users/juniorgarcia/workspace/heroui_v3/packages/core(generates CSS classes) - React Package:
/Users/juniorgarcia/workspace/heroui_v3/packages/react(consumes CSS classes) - Global Styles:
packages/storybook/styles/globals.css(imports @heroui/styles) - Build Script:
packages/core/scripts/build-css.mjs(transforms CSS to JS) - Plugin:
packages/core/plugin.ts(injects styles into Tailwind)
Debugging Methodology
-
Error Analysis:
- Parse error messages to identify the specific utility class or component causing issues
- Determine if the error is from Tailwind CSS v4 compatibility or transformation issues
- Check if the error occurs during build time or runtime
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 · 115 lines · 0 tokens per session scan A b1ef287d3de9
storybook-debugger 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 1,550 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
investigate-error
Investigates React compiler errors to determine the root cause and identify potential mitigation(s). Use this agent when the user asks to 'investigate a bug', 'debug why this fixture errors', 'understand why the compiler is failing', 'find the root cause of a compiler issue', or when they provide a snippet of code and…
ultrathink-debugger
Use when encountering bugs, errors, unexpected behavior, or system failures that require deep investigation and root cause analysis. Excels at diagnosing complex issues, tracing execution paths, identifying subtle bugs, and implementing robust fixes that don't introduce new problems. Perfect for production issues…
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.
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
react-build-resolver
Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…