Privacy-friendly analytics only with consent. No ads, no cross-site tracking. Read the privacy policy.

v0.8.0112 components, MCP validate_usage, streaming-safe Response, and a shadcn-compatible registry.What's new →

Introduction

Slipstream UI is an AI-first React component library. Every component ships with a COMPONENT_MANIFEST — a machine-readable specification that lets coding agents like Claude, Cursor, and Copilot generate correct UI the first time.

What makes it different?

Traditional libraries document for humans and hope models figure it out from training data — which is where hallucinated props come from. Slipstream documents for both of you: humans get this site, agents get manifests over MCP, canonical markdown routes, and a validate_usage tool that checks their output before it ships.

Architecture

One monorepo ships seven published packages and two reference apps. Components live inpackages/core andpackages/ai; theming lives in@slipstream-ui/themes. Every component flows through the same pipeline, and CI enforces it:

text

source + manifest + tests
      │
      ├─ pnpm validate:manifests   # schema + TypeScript↔manifest drift
      ├─ pnpm generate:registry    # /registry/*.json (shadcn-compatible)
      ├─ pnpm generate:llm-docs    # /llm/*.md, llms.txt, README stats
      └─ MCP server                # queries the same manifests at runtime

@slipstream-ui/core on npm (opens in a new tab) — 95 components: atoms, molecules, overlays, forms, data display, app/marketing chrome, content typography
@slipstream-ui/ai on npm (opens in a new tab) — 17 AI chat and agent components (stateless; you own state and transport)
@slipstream-ui/themes on npm (opens in a new tab) — createTheme() and presets over a CSS-variable token contract
@slipstream-ui/cli on npm (opens in a new tab), @slipstream-ui/registry on npm (opens in a new tab), @slipstream-ui/mcp-server on npm (opens in a new tab), @slipstream-ui/i18n on npm (opens in a new tab) — install, registry, agent, and locale helpers sharing the same manifests
apps/docs · apps/app · apps/playground — the docs you are reading and a reference dashboard, both built with this library

Start here

1. Install. Follow the five-step quickstart for a themed screen, or read the installation guide for packages, CLI, and registry tradeoffs.
2. Read one manifest. Open COMPONENT_MANIFEST to see the prop schema, anti-patterns, and accessibility rules your agent will read.
3. Wire up the agent loop. Connect the MCP server and call validate_usage before generated JSX reaches your editor.

Quick start

bash

# Packages
pnpm add @slipstream-ui/core @slipstream-ui/ai

# Or install source copies via the registry
npx shadcn@latest add https://slipstreamui.com/registry/message.json

Full setup instructions live under Installation.

Explore

Installation

Packages, CLI, or shadcn-compatible registry — pick your workflow.

COMPONENT_MANIFEST

The machine-readable spec behind every component: props, anti-patterns, a11y.

Components

112 components across core and AI interaction surfaces.

Templates

Complete copy-paste patterns: streaming chat, agent dashboard, RAG citations.

Versioning & Stability

Slipstream UI follows semantic versioning. The current major version is 0.x, meaning the API may change between minor releases as the library matures toward 1.0.

Patch (0.x.y): Bug fixes, accessibility improvements, documentation updates. No API changes.
Minor (0.x.0): New components, new props, new tokens. Existing props and components remain backward-compatible unless marked deprecated.
Major (1.0.0): Stable API guarantee. After 1.0, breaking changes only in major releases with a migration guide.

Every component ships a COMPONENT_MANIFEST with a version field. The manifest schema is validated in CI — prop schemas, TypeScript types, and manifests are checked for drift on every commit.

Accessibility: All components pass jest-axe automated checks and support keyboard navigation, screen readers, and reduced-motion preferences. Accessibility regressions are treated as bugs.

For agent builders

If you are wiring an agent into Slipstream, start with the MCP server, the canonical markdown index, or the manifest schema. Every component page also links its own markdown reference in the header.

Was this page helpful?