Where this is going

23 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.

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.

Compose a video from snapcn components in the browser — add clips, edit the text and images, export an MP4. The timeline and the server-side render path already exist; what is left is making an export something you would actually ship.

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.