Skip to content

Components

These are composed components, not package exports. Each one is a shadcn registry item: install it with the CLI or copy the source into your project. The CLI writes the file where shadcn expects it and pulls in the shadcn primitives the component uses.

The scene wrappers stay ascii-things imports. The surrounding card, badge, and button belong to your design system. The scene console and scene toolbar are different: they copy the first-party ascii-things/ui composition into your project, so you own the layout while the package supplies the primitives and stylesheet.

Terminal window
npx shadcn@latest add https://ascii-things.dev/r/koi-card.json

Swap the item name for any of the components below. Run the command from the root of a project that already has components.json.

Registry

Browse the components.

Six copyable shadcn items. Preview one, copy the install command, or open the full page for composition notes and source.

CardLive scene

Koi card

A shadcn card with a live koi pond and a re-seed control.

View component ↗

The registry index is at /r/registry.json.

The package primitives themselves — AsciiStage, AsciiPrompt, AsciiReadout, AsciiSceneTabs, AsciiPanel, AsciiToolbar, AsciiToggle, AsciiButton, AsciiStatus, and AsciiDivider — are documented in the UI components guide. The scene console and scene toolbar are the copyable compositions built from them.

Every page links to its source file. The registry JSON is generated from the same files, so the install path and the copy path cannot drift. Use the CLI when you want the shadcn primitives and the ascii-things dependency added for you; copy the source when you want to own the file without a registry request.