Magic UI

Add Magic UI on top of an existing shadcn/ui project rather than instead of it — the CLI, registry format and CSS variables are identical, so the two compose without config, but Magic UI ships zero accessible primitives (no dialog, no select, no combobox). Use it for the marketing surface: Marquee for logo walls, Bento Grid for feature sections, Number Ticker for stats, Safari/iPhone mocks for product shots. Nearly every component is a Motion client component, so mark them `'use client'` and keep them out of the critical render path in an RSC app.

Why it is here. It is the default landing-page motion layer for the shadcn ecosystem — the same install flow, the same tokens, and enough components that a marketing page can be assembled entirely from the registry.