ikui

A copy-paste React component library distributed as a shadcn-style registry, not an npm package. Components are added as source code into the user's project. ikui has no CLI of its own — installation goes through the shadcn CLI pointed at the @ikui registry.

• Registry: https://ik-ui.pages.dev/r/{name}.json
• Docs: https://ik-ui.pages.dev
• Built on Base UI (@base-ui/react) — never Radix — with Tailwind CSS v4, lucide-react, and motion.

IMPORTANT: Run all CLI commands with the project's package runner — npx shadcn@latest, pnpm dlx shadcn@latest, or bunx --bun shadcn@latest, based on the project's packageManager. Examples below use npx; substitute the correct runner.

Two layers: primitives and blocks

ikui is organized in two tiers — knowing which one the user needs is the single most important routing decision.

• Primitives (registry:component / registry:lib) are small, single-purpose, intentionally "dumb" parts: a waveform, a thumbnail strip, a timeline ruler/element/playhead, a crop box. They own no business logic — the playback clock, seeking, and track wiring are left to the consumer. Reach for these when the user is building their own editor/feature.
• Blocks (registry:block) are business compositions — ikui's signature value. Each block stitches many primitives together into a working feature with all the wiring done: state, playback, readouts, export. Reach for a block when the user wants the finished thing, not the parts.

Current blocks (always confirm against the live registry — see "Current Components" below):