Skip to main content

V2 Migration Orchestrator

The abyss-v2-migration orchestrator automatically detects your migration needs and executes specialized skills in the optimal sequence for upgrading from Abyss v1 to v2.

Recommended model: Claude Sonnet 4.6 or higher.

What it does​

This orchestrator:

  • Auto-detects platform (web/mobile/both) and package versions
  • Scans for component usage, legacy tokens (web only), and v1 component token usage (web only)
  • Installs only the migration skills you need based on detection
  • Executes specialized skills (web/mobile migration, token migration) in optimal order
  • Provides a checklist of additional v2 migration steps

Smart installation: Web-only apps won't install mobile skills. v1.x.x apps won't install token migration skills until needed.

When to use it​

Use this skill when:

  • Migrating from Abyss v1 to v2
  • You want automatic detection and guided migration
  • You need help determining which migration tools to run

Don't use if you want to run individual migration tools separately.

Prerequisites​

Before installing this skill, ensure you have the Abyss CLI set up properly:

npx @uhg-abyss/cli -v

If the command fails, refer to the CLI Setup Guide for installation instructions.

Installation​

Install the orchestrator skill:

npx @uhg-abyss/cli skills add abyss-v2-migration

The orchestrator will automatically install dependent skills on-demand.

Example prompts​

Once installed, you can use prompts like:

  • "Migrate to Abyss v2"
  • "What v2 migration work do I need?"
  • "Run the v2 migration orchestrator"

Migration paths (v1.x.x users)​

If you're on v1.x.x, the orchestrator presents two paths:

Gradual (recommended): Stay on v1.x.x while migrating components incrementally. Use V2ComponentName as ComponentName pattern. Lower risk.

Fast: Upgrade to v2.x.x immediately and run all migrations at once. Faster but higher risk.

What gets automated​

The orchestrator handles:

  • Component imports and API migrations
  • Component token overrides (web v2.x.x only)
  • Legacy token migrations (web v2.x.x only)

Not automated: React version upgrades, theming changes, Stitches → Emotion migration, routing updates. The orchestrator provides a checklist for these.

Dependent skills​

Orchestrator invokes these as needed:

More information​

Table of Contents