Changelog
What changed in Keyframery, newest first: new components, UI SDK upgrades, templates, motion styles and fixes.
Backroom: the first admin template
November 2026
- Backroom is a complete store admin, and it is free. 27 working pages: dashboard, orders, a new order, products, customers, discounts, inbox, apps, notifications, help, settings, sign-in and error pages. Install it with
npx shadcn@latest add @keyframery/backroom. - UI SDK end to end. Every control in it is a Keyframery component, so AI agents can read and use each page through UI SDK's agent bridge.
- Six new components came out of it: Data Table, Description List, Filter, Sparkline, Stat and Stepper. Chart gains stacked bars.
- Segmented Control keeps an item's own classes on its label, so items can stretch to fill the control.
UI SDK 0.1.0-beta.9
November 2026
- Built and tested on UI SDK
0.1.0-beta.9. The registry pins it, so adding a component brings a project up to beta.9. - Dialog and Popover take
inline. The content (and a dialog's backdrop) renders where it sits in the page instead of the top layer, so it can stay inside a frame. - Controllers can move the highlight. Combobox, Autocomplete and Listbox controllers take
highlight(value)andgetHighlighted(). - Pagination takes
disabled, which turns off every page and step at once. - Autocomplete's
onValueChangetells suggestions apart. Its details carry the chosenitem, typed asAutocompleteValueChangeDetails. - Safer agent actions. An agent that removes an item marked
data-agent-confirmnow needs a person's OK, as adding one already did.
Customization, UI SDK core and clearer docs
November 2026
- 82 components, all built on UI SDK. Additional components use
definePrimitiveon UI SDK's core, with the React adapter for their rendered parts. - Customize below every preview. Colors, sizes, content and behavior controls are open by default. Animation speed is separate from the four motion styles; 1× is normal and higher is faster.
- State callbacks and exports preserved. Both primitive and styled imports retain UI SDK exports and state-based
className,style,childrenandrendersupport. - Searchable docs. Filter components by category, follow related components and inspect documented CSS theme variables. Theme colors remain unchanged until overridden.
2.0: Every UI SDK component, on 0.1.0-beta.5
November 2026
Keyframery now has an animated version of every UI SDK component, all 55, and each one takes everything its UI SDK counterpart takes. With the 8 components UI SDK doesn't have, that makes 63.
- Preferences is new, the last UI SDK component Keyframery was missing. It comes with
PreferenceSwitcher, a segmented control for any preference. The motion style switcher is built on it. - Built and tested on UI SDK
0.1.0-beta.5. The registry pins that version. - Every UI SDK part, prop and helper works from both layers. The finished components gain
TabsTabIcon,TabsIndicatorandCommandItems, and pass through every controller (createTabsControllerand the rest),confirm,sheetPhysicsand the tree helpers. Parts that add an element of their own (a chevron, the moving key) now takechildrenas a function of their state too. - Menus, listboxes and command lists written as data (
items) render with Keyframery's rows. A data menu renders its own content, as in UI SDK. - Menu handles context menus by itself. A Menu that opens from a
MenuContextTrigger, as in UI SDK, unfolds from the pointer. Context Menu is still there under its own name.
1.3: Speed, Table and fuller docs
November 2026
speedon every component. Passspeed="fast","slow"or a multiplier like0.8to change how fast one component moves, popups included.KeyframeryProvidersets it, and the motion style, for a whole app. Both come from a new shared file,lib/keyframery.tsx, installed with the motion tokens.- Table, the 62nd component, with shadcn's part names. Rows cascade in, a sortable header's arrow turns over on a spring, selected rows fade in, and a wide table scrolls sideways on a phone with a soft edge.
- Sidebar highlight is quicker: the key now glides to the item you click in 260ms instead of 460ms.
- Every component page has more to it: a short usage snippet, how the parts fit together, small live examples you can open as code, a props table for each part (read from the types), a keyboard table, and manual install steps next to the CLI.
1.2: Phone layouts
November 2026
- Every demo has a phone layout. Demos are fluid and respond to their own width with container queries, so on a phone they rearrange instead of shrinking. The navigation menu turns into a breadcrumb and a menu button, panels stack, and keyboard hints step aside.
- Sidebar sheet: below
mobileBreakpoint(640px by default) the sidebar slides in over the page, over a scrim. The trigger opens it, and the scrim, Escape or choosing a page closes it.useSidebar()now also returnsisMobile,openMobileandsetOpenMobile. - Mobile preview in the docs: each component page can show its demo at a phone's width, next to the desktop view.
1.1: Sidebar
November 2026
- Sidebar, the 61st component. UI SDK has no sidebar, so it uses shadcn's part names on plain elements, like Card. The current page's key glides between items, groups fold away with the collapsible's height, and the whole sidebar narrows to an icon rail.
- Demos use real photos in place of drawn stand-ins.
1.0: Keyframery for UI SDK
November 2026
Keyframery is now a set of animated components for UI SDK.
- 60 components, each built on its UI SDK counterpart with the same parts and props.
- Two layers per component: a primitive that adds motion only, and a finished component with a look.
- Four motion styles: Calm, Springy, Snappy and Playful, switched with
data-motion. - Plain CSS: no animation library. Springs are CSS easings.
- Installs with the shadcn CLI from the
@keyframeryregistry. - A skill for Claude Code and a prompt for other coding agents.
If you used the earlier Keyframery
The earlier Keyframery was a motion layer for shadcn/ui, built around a <Cuts /> component. It has been retired, and its registry items (cuts, value-cut, list-cut, load-cut, state-cut, match-cut and icon-moves) are no longer served. The code already copied into your project keeps working, because the shadcn CLI copies source rather than linking to it.