radix-to-baseui-migration

Migrate React components from Radix UI to Base UI within shadcn architectures.

7|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Cobalt-Money/Cobalt --skill radix-to-baseui-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: radix-to-baseui-migration
Source: https://github.com/Cobalt-Money/Cobalt/tree/main/.agents/skills/radix-to-baseui-migration
Command: npx skills add https://github.com/Cobalt-Money/Cobalt --skill radix-to-baseui-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill streamlines the complex, error-prone process of migrating shadcn components from Radix UI primitives to Base UI, ensuring architectural consistency and type safety.

Core Features & Use Cases

  • Structured Migration Workflow: Provides a four-pass execution strategy to handle imports, composition, types, and positioning.
  • Pattern Mapping: Includes reference guides for converting asChild patterns to render-based composition and updating API prop names.
  • Use Case: Use this skill when refactoring a large component library to Base UI to ensure that keyboard interactions, focus management, and floating element positioning remain intact across the codebase.

Quick Start

Initiate the migration process for the dropdown component family by following the four-pass workflow outlined in the skill documentation.

Frequently Asked Questions about radix-to-baseui-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate shadcn components from Radix UI to Base UI?

Migrate shadcn components from Radix UI to Base UI by replacing imports, converting asChild composition patterns, updating TypeScript prop definitions, and reconfiguring floating element positioning through a structured four-pass workflow.

What is the best way to replace asChild patterns when moving to Base UI?

Replace asChild patterns when moving to Base UI by utilizing reference guides to convert them into render-based composition, ensuring that component APIs and TypeScript definitions are updated simultaneously for type safety.

How does the Radix UI to Base UI migration process handle accessibility compliance?

The Radix UI to Base UI migration process handles accessibility compliance by employing a multi-pass validation and build-check strategy that ensures keyboard interactions and focus management remain intact across the refactored component library.

Can I use this migration workflow for large React component libraries?

Yes, you can use this migration workflow for large React component libraries as it provides a systematic four-pass execution strategy designed to maintain functional parity and architectural consistency across the entire codebase.

Why do TypeScript prop definitions need updating during a Base UI migration?

TypeScript prop definitions need updating during a Base UI migration because Base UI components utilize different API prop names and structures compared to Radix UI primitives, requiring definition reconfiguration to maintain type safety.

What are the limitations of manually refactoring Radix UI primitives to Base UI?

Manually refactoring Radix UI primitives to Base UI risks breaking floating element positioning and keyboard interactions, making an automated multi-pass validation strategy necessary to ensure functional parity and avoid architectural inconsistencies.