Where this is going

46 free components — text animators, captions, logo stings, device frames, social proof and full scenes — installable with one shadcn command. Listed in the shadcn registry directory, so the CLI resolves @snapcn with nothing to configure.

Timeline-driven versions of the shadcn atoms — input, caret, and the theme and colour core the scenes paint from — so a component drops in next to your own Input and Button and belongs there.

A reference an AI coding agent can read: every component, its props, and the archetypes they compose into. Point Claude at it and ask for a product demo.

51 paid components on top of the free 46, shown in the same grid and playing the same way — you can watch every one of them before deciding. Bought whole, never per component: a year of the catalogue, or the catalogue outright.

Compose a video from snapcn components in the browser — add clips, edit the text and images, export an MP4. No install and no account needed to try it.

The registry is the product and it is not finished. One new clip, published every day — the gap between what a demo video needs and what is in here closes by cadence rather than in batches. The changelog is the receipt.

Whole videos rather than single scenes — a launch film, a feature walkthrough, a changelog clip — composed from the registry and ready to render once you drop your own copy in. Around ten land on 20 October, included in Pro.

Leave the editor with a Remotion project rather than only a file — the timeline you built, emitted as a <Composition> and the components it uses, in your repo. The editor composes and renders today; what it cannot yet do is hand you the source.

A place for components that are not ours — other people's scenes, installed the same way. Only worth building once there are enough authors to fill it.