Fetches and applies HeroUI v2-to-v3 breaking-change MDX guides via Node scripts.
npx skills add https://github.com/junevm/avtoolz --skill heroui-migration-junevm
Please help me install this Agent Skill. Skill: heroui-migration Source: https://github.com/junevm/avtoolz/tree/main/.agents/skills/heroui-migration Command: npx skills add https://github.com/junevm/avtoolz --skill heroui-migration-junevm
Migrating a HeroUI v2 application to HeroUI v3 is error-prone because the component APIs and runtime patterns change in breaking ways, causing build failures and incorrect UI behavior.
Tell your agent to fetch the full migration workflow and then retrieve the specific component guides for the components your codebase uses.
High-intent search queries and answers about installing and using this skill.
To migrate HeroUI v2 to v3, you fetch breaking-change MDX documentation using bundled Node scripts and apply the v2-to-v3 transformation rules for component upgrades, event handler renaming, and styling changes. This workflow supports both full and incremental migration scenarios.
HeroUI v3 component upgrades involve transitioning from flat props to compound components, renaming event handlers, migrating Tailwind v4 styling, and removing hooks and Provider patterns. The Skill fetches per-component MDX guides detailing these specific API and runtime pattern transformations.
Yes, you can perform an incremental HeroUI migration by fetching specific component guides and applying transformation rules individually. The migration workflow supports planning and executing targeted steps for each component your codebase uses, rather than requiring a single full migration.
Yes, the HeroUI v3 migration workflow provides targeted steps for Tailwind v4 styling changes. It fetches MDX guides that document how to update styling patterns from v2 to v3, ensuring your component styles remain compatible after the migration.
Removing hooks and Provider patterns during HeroUI v3 migration requires following the hooks-to-compound migration steps in the fetched MDX guides. The documentation provides specific transformation rules to replace removed Provider patterns with the new v3 compound component APIs.
Yes, the HeroUI migration workflow requires using bundled Node scripts to fetch MDX guides from the configured documentation base. These scripts retrieve the per-component breaking-change documentation that agents follow to apply the correct v2-to-v3 transformations.
Insik-HanFetch HeroUI Native component docs, theming, and usage guides via Node scripts.
ruchernchongBuild accessible React interfaces with HeroUI v3 compound components and Tailwind v4.
remiconnessonEnforce Tailwind CSS v4 migration-safe utilities, build settings, and design-token patterns.
beemanImplement HeroUI v3 components in React with Tailwind CSS v4 theming.
