heroui-migration

To migrate HeroUI v2 components to v3, follow a structured agent-focused workflow that provides step-by-step guides for safely transitioning components, providers, and styling. The process includes script-driven documentation retrieval to fetch main and component guides before applying changes.

Upgrading HeroUI providers and styling involves using script-driven documentation access and versioned guides. This validation-friendly process provides clear steps and guardrails to ensure a safe transition during full or incremental migrations.

Yes, you can perform an incremental migration for HeroUI v2 to v3. The workflow supports both full and incremental migration paths, allowing you to update components and styling progressively using step-by-step migration workflows.

Yes, you need to run scripts to fetch documentation before migrating HeroUI. The quick start process requires running the agent migration workflow to fetch main and component guides, ensuring you have the necessary references before applying changes.

The HeroUI migration workflow's limitations are mitigated by built-in guardrails and a validation-friendly process. However, it specifically targets projects upgrading HeroUI components, providers, and styling, meaning its guides may not cover custom or non-standard implementations.