zhukang 1c7abd81d1 All 310 Manus skill-hub community skills as a Kortix marketplace registry

- 310 registry:skill items, 1528 files, 7 categories (hub tags)
- registry.json generated by @kortix/registry buildRegistry
- nested SKILL.md in sn-da-* renamed SUBSKILL.md (no phantom skills)
- provenance + licenses: SOURCES.md

2026-09-15 13:37:20 +08:00

7.1 KiB

Raw Permalink Blame History

Radix UI Migration Guide - Spark App Template

Context

Radix UI, the foundation of shadcn/ui, has received fewer updates since its acquisition by WorkOS. While Radix remains stable, the ecosystem is evolving with new alternatives.

Current Status (January 2026)

Radix UI:

✅ Mature, stable, production-ready
✅ Powers shadcn/ui (45+ components)
✅ Used by millions of production apps
⚠️ Slower update cadence
⚠️ Uncertainty about long-term roadmap

Recommendation for New Projects: Use Radix with confidence, but be aware of migration paths.

Migration Options

Option 1: Stay with Radix (Recommended for Most)

When to choose:

Building production apps today
Need stability over cutting-edge features
Want proven components with wide adoption
Using shadcn/ui ecosystem

Action: No changes needed. Continue using Radix-based shadcn components.

Monitoring: Watch for shadcn/ui announcements about alternative foundations.

Option 2: Migrate to Base UI

What is Base UI?

Built by original Radix team (now at Vercel/MUI)
Currently in beta, but "looking really good" per shadcn
Designed for easy migration from Radix
Similar API and component structure

Status: Beta (as of January 2026)

Migration Path:

Wait for shadcn/ui Support shadcn/ui now supports Base UI components. You can choose Radix or Base UI when installing:
```
pnpm dlx shadcn@latest init
# Choose Base UI when prompted
```
Gradual Component Migration shadcn components are framework-agnostic. When Base UI components are added to shadcn, you can:
```
# Install Base UI version of component
pnpm dlx shadcn@latest add button --base-ui
```
Auto-Detection The shadcn CLI auto-detects your library and applies the right transformations.

Trade-offs:

✅ Future-proof choice
✅ Active development
✅ Backed by Vercel/MUI
⚠️ Still in beta
⚠️ Smaller ecosystem currently

Option 3: Migrate to React Aria

What is React Aria?

Built by Adobe
Powers React Spectrum (Adobe's design system)
Superior accessibility implementation
Behavior-first hooks implementing WAI-ARIA spec
Production-ready and actively maintained

When to choose:

Accessibility is top priority
Need advanced customization
Want long-term Adobe backing
Building design systems

Migration Effort: Moderate to High

React Aria has different API patterns
Requires rewriting component wrappers
More control, but more work

Example Migration:

Before (Radix via shadcn):

import { Dialog, DialogContent, DialogHeader, DialogTitle } from '@/components/ui/dialog';

<Dialog>
  <DialogTrigger>Open</DialogTrigger>
  <DialogContent>
    <DialogHeader>
      <DialogTitle>Title</DialogTitle>
    </DialogHeader>
  </DialogContent>
</Dialog>

After (React Aria):

import { DialogTrigger, Modal, Dialog, Heading } from 'react-aria-components';

<DialogTrigger>
  <Button>Open</Button>
  <Modal>
    <Dialog>
      <Heading slot="title">Title</Heading>
      {/* Content */}
    </Dialog>
  </Modal>
</DialogTrigger>

Resources:

Practical Migration Strategy

Phase 1: Assessment (Now)

Inventory your Radix usage
```
grep -r "@radix-ui" src/
```
Identify critical components
- Dialog/Modal
- Dropdown Menu
- Select
- Popover
- Tooltip
- etc.
Evaluate impact
- How many components use Radix?
- Are they heavily customized?
- What's the migration cost vs. benefit?

Phase 2: Monitoring (Ongoing)

Watch for:

shadcn/ui announcements about Base UI support
Radix UI update frequency
Community migration patterns
Base UI stable release

Action Items:

Subscribe to shadcn/ui GitHub releases
Follow @shadcn on Twitter/X
Monitor Radix UI GitHub activity

Phase 3: Migration (When Ready)

Trigger Migration When:

Base UI reaches stable v1.0
shadcn/ui fully supports Base UI
Radix UI shows signs of abandonment
Security vulnerabilities go unpatched

Migration Approach:

Test Environment First
- Set up new branch
- Migrate one component at a time
- Test thoroughly before production

Gradual Rollout

# Migrate component by component
pnpm dlx shadcn@latest add button --base-ui
pnpm dlx shadcn@latest add dialog --base-ui

Coexistence
- Both Radix and Base UI can coexist temporarily
- Migrate high-traffic components first
- Monitor for issues

Phase 4: Complete Migration (Future)

Timeline: Likely 2026-2027

Steps:

All new components use Base UI
Gradual migration of existing components
Remove Radix dependencies when complete
Update documentation

For Spark App Template Users

Current Recommendation

Default: Use Radix-based shadcn/ui

Production-ready today
Extensive component library (45+)
Proven track record
Wide community support

Exception: If building from scratch in Q3 2026+, consider Base UI if stable.

Staying Updated

Spark App Template will be updated when:

Base UI reaches stable v1.0
shadcn/ui completes Base UI integration
Migration path is proven and low-risk

Check for updates:

Spark App Template GitHub releases
shadcn/ui changelog
This migration guide (will be updated)

FAQ

Q: Should I worry about Radix today? A: No. Radix is stable and production-ready. Use it with confidence.

Q: When should I migrate? A: When Base UI is stable (v1.0+) and shadcn/ui fully supports it, likely mid-to-late 2026.

Q: Can I use Radix for new projects now? A: Yes. The migration path will be straightforward when Base UI is ready.

Q: What about React Aria? A: Excellent choice for accessibility-first projects, but requires more custom work.

Q: Will shadcn/ui abandon Radix? A: No indication of abandonment. shadcn is adding Base UI as an option, not replacing Radix.

Q: How much work is the migration? A: Minimal if using shadcn/ui. Components can be swapped one at a time with CLI.

Resources