heroui-migration

This skill helps agents migrate HeroUI v2 applications to v3. HeroUI v3 introduces breaking changes: compound components, no Provider, Tailwind v4, and removed hooks. Do NOT assume v2 patterns work in v3. Always fetch migration guides before implementing changes. For migration details, examples, and step-by-step guides, always fetch documentation: Migration docs (preview): Examples: Override base URL with HEROUI_MIGRATION_DOCS_BASE when docs are merged to production. When using Cursor or other MCP clients, configure the Migration MCP server for tool-based access: Always fetch the agent guide before starting: node scripts/get_migration_guide.mjs full or incremental This skill targets the staging deployment of the docs/migration branch. Once docs are merged to main and live on heroui.com, set HEROUI_MIGRATION_DOCS_BASE= or update the default in scripts. - Full migration: .../agent-guide-full.mdx - Incremental: .../agent-guide-incremental.mdx - Button: .../button.mdx - Styling: .../styling.mdx - Hooks: .../hooks.mdx - Best for: Projects that can dedicate focused time; teams comfortable with temporarily broken code - Migrate all component code first (project broken during migration) - Switch dependencies to v3 - Complete styling migration - Best for: Projects that must stay functional; large codebases migrating gradually - Set up coexistence (pnpm aliases or component packages) -...