Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Keep registry base and radix trees in sync when editing shared UI
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | 172% | 0% |
| case-23 | ✓→✗ | ▼ Worse | -81% | 0% |
| case-25 | ✓→✗ | ▼ Worse | -51% | 0% |
| case-16 | ✓→✓ | = Same ✓ | -38% | 0% |
| case-01 | ✗→✗ | = Same ✗ | -46% | 0% |
apps/v4/registry/bases/base and apps/v4/registry/bases/radix are parallel registries. Anything that exists in both trees for the same purpose (preview blocks, mirrored examples, shared card layouts, etc.) must stay in sync.
bases/base/..., apply the same behavioral and visual change to the matching path under bases/radix/... (and the reverse).@/registry/bases/base/ui/* vs @/registry/bases/radix/ui/*, or Base UI vs Radix component props).blocks/preview/** — preview cards and blocksui/* components when both exist for the same componentAfter edits, briefly confirm both trees were updated (or state why one side is intentionally unchanged).
Other measured skills in the registry, with their headline benchmark lift.