Privacy-friendly analytics only with consent. No ads, no cross-site tracking. Read the privacy policy.
Every Slipstream UI component ships a machine-readable manifest that tells AI agents exactly how to use it.
The COMPONENT_MANIFEST is a JSON file that accompanies every component. It contains structured information about the component that AI agents can read to understand:
Traditional component libraries rely on source code and documentation. AI agents reading source code often:
COMPONENT_MANIFEST solves this by providing a contract that explicitly states how the component should be used.
Every manifest follows this schema. Here is the button manifest as a reference:
{"id": "button","name": "Button","tier": "atom","description": "A clickable button component...","designIntent": "The Button component is a fundamental...","props": [{"name": "variant","type": "'default' | 'destructive' | 'outline' | 'secondary' | 'ghost' | 'link'","defaultValue": "default","required": false,"description": "Visual style variant","enum": ["default", "destructive", "outline", "secondary", "ghost", "link"],"examples": ["default", "destructive", "outline"]},{"name": "size","type": "'sm' | 'default' | 'lg' | 'icon'","defaultValue": "default","required": false,"description": "Button size"}],"examples": [{"title": "Primary action button","code": "<Button>Click me</Button>","description": "Default variant for primary actions"},{"title": "Destructive action","code": "<Button variant=\"destructive\">Delete</Button>","description": "Use for irreversible actions"}],"antiPatterns": [{"title": "Don't use for navigation alone","explanation": "Buttons should trigger actions, not just navigate. Use a Link for pure navigation.","example": "// Avoid\n<Button onClick={() => router.push('/home')}>Home</Button>\n\n// Prefer\n<Link href=\"/home\">Home</Link>"}],"accessibility": [{"feature": "Keyboard navigation","implementation": "Button is natively focusable and activates on Enter/Space","userRequirements": "Ensure visible focus indicator"},{"feature": "Screen reader support","implementation": "Button text is announced as the accessible name","userRequirements": "For icon-only buttons, provide aria-label"}],"contentGuidelines": [{"contentType": "Button text","guidelines": ["Use action verbs (Submit, Save, Delete)","Keep text short and concise","Be specific about what will happen"],"goodExamples": ["Submit form", "Save changes", "Delete account"],"badExamples": ["Click here", "OK", "Do it"]}],"compositionRules": [{"component": "Icon","relationship": "Buttons can contain icons before or after text","example": "<Button><Icon />Text</Button>"},{"component": "Tooltip","relationship": "Wrap icon-only buttons with a Tooltip to name them","example": "<Tooltip content=\"Close\"><Button aria-label=\"Close\">×</Button></Tooltip>"}],"relatedComponents": ["Badge", "Link", "Tooltip"],"package": "@slipstream-ui/core","importPath": "@slipstream-ui/core","version": "0.5.0","sourceDir": "button","exportName": "Button"}
version tracks the published package version; sourceDir and exportName let the drift checker find the TypeScript declaration that this manifest must match.
| Section | What it carries | Why an agent needs it |
|---|---|---|
| id, name, tier, package | Identity and import path | Find the component and the package to import. |
| description, designIntent | What it is and when to reach for it | Pick the right component instead of a near neighbor. |
| props | Type, required, default, enum, description | Write real props and valid enum values. |
| examples | Runnable JSX with titles | Copy a pattern that compiles. |
| antiPatterns | Wrong usage plus the preferred code | Avoid the predictable mistakes. |
| accessibility | Feature, implementation, user requirements | Keep generated UI accessible. |
| contentGuidelines | Tone, length, good/bad examples | Generate appropriate copy, not lorem ipsum. |
| compositionRules | Related components and example wiring | Compose instead of duplicating. |
| relatedComponents | Adjacent component ids | Walk to the next component in the flow. |
The props section provides complete type information for every prop, including:
Each manifest includes both good usage examples and anti-patterns to avoid. This helps AI agents:
Accessibility is built into every manifest with:
For components that display text (buttons, inputs, messages), the manifest includes:
Manifests specify how components work together:
AI agents can access COMPONENT_MANIFEST files through:
The Slipstream UI MCP server provides tools to query manifests:
# List all componentslist_components()# Search by capabilitysearch_components(query="streaming chat")# Get specific component manifestget_component_manifest(componentId="button")# Get examples and composition rulesget_usage_examples(componentId="button")# Validate generated JSX against the manifestvalidate_usage(componentId="button",code="<Button variant='primry'>Save</Button>")# -> { valid: false, issues: [{ severity: "error", message: "Invalid value ..." }] }
Any client that can fetch a URL gets the same contract without an MCP connection:
GET /llms.txt # curated agent indexGET /llms-full.txt # every component in one fileGET /llm/index.md # overview plus component indexGET /llm/components/<id>.md # full reference generated from the manifest
Build tools and shadcn-compatible installers read the generated registry. It carries the manifest plus the component source payload:
GET /registry/all.json # index of every componentGET /registry/<id>.json # manifest + shadcn installer payloadGET /registry/graph.json # component relationship graph (nodes + edges)GET /registry/recommendations.json # intent recipes behind recommend_components
/registry/graph.json turns the manifests' compositionRules and relatedComponents into a traversable edge list, so an agent can choose a coherent set — a Dialog with a Form, a Conversation with Messages — instead of one component at a time. Every edge resolves to a node; the count gate checks that.
In a checkout, manifests are stored alongside component source code:
packages/core/src/manifests/button.manifest.jsonpackages/core/src/manifests/input.manifest.jsonpackages/ai/src/manifests/message.manifest.jsonpackages/ai/src/manifests/conversation.manifest.json
The repository includes llms.txt at the root and serves the same file at https://slipstreamui.com/llms.txt. The component lists inside it are generated between marker comments, so the index cannot drift from the real manifest set.
When adding new components to Slipstream UI:
src/manifests/*Props type in that directorypnpm validate:manifests to validate schema and TypeScript driftpnpm generate:registry and pnpm generate:llm-docspnpm check:llm so stale generated docs fail earlyFour checks run in CI, each covering a different kind of drift:
| Command | Catches |
|---|---|
| pnpm validate:manifests | Schema errors, TypeScript ↔ manifest prop drift, version and component-count mismatches. |
| pnpm generate:registry | Regenerates /registry; a diff means the published contract is stale. |
| pnpm generate:llm-docs | Regenerates /llm, llms.txt, llms-full.txt, and README stats from manifests. |
| pnpm check:llm | Fails when generated markdown no longer matches the manifests. |
The validator is a contract check, not a compiler. It reports unknown props, invalid enum values, and missing required props. Pair it with tsc and your test suite for everything else.