useVyre component context for AI agents — valid props, variants, anti-patterns, and design tokens.
AI-native design system for humans and agents. Built on semantic CSS variables — no runtime magic, no hallucinations.
Most design systems were built for humans reading documentation. useVyre is built for both — every naming convention, token structure, and component API is designed so that AI coding agents (Claude, Cursor, Copilot, Windsurf) can generate correct, consistent UI without guessing.
| Problem | useVyre solution |
|---|---|
| AI hallucinates component props | Every component has an inline AI context block |
| AI uses raw color values | Semantic tokens replace all raw colors |
| AI generates inconsistent spacing | 4px grid enforced via spacing tokens |
| AI doesn't know valid variants | data-variant API is explicit and enumerated |
| Design system only works in one framework | CSS variables work everywhere |
Core
| Package | Version | Downloads | Description |
|---|---|---|---|
@usevyre/tokens | DTCG-compliant design tokens → CSS variables, JS/TS, JSON | ||
@usevyre/react | React + TypeScript components | ||
@usevyre/vue | Vue 3 + TypeScript components | ||
@usevyre/init | One-command setup CLI (npx @usevyre/init) | ||
@usevyre/all · react-all · vue-all | — | — | Convenience meta-packages (tokens + components in one install) |
AI tooling
| Package | Version | Downloads | Description |
|---|---|---|---|
@usevyre/ai-context | Machine-readable component schema for LLM system prompts | ||
@usevyre/mcp-server | MCP server — gives agents live access to the component schema | ||
@usevyre/eslint-plugin | Lints for invalid variants, raw colors, hallucinated props | ||
@usevyre/validate-ai-context | CI check that the AI context stays in sync with components | ||
@usevyre/prompt-templates | Ready-made prompts for generating UI with useVyre |
40+ production-ready components for React and Vue — buttons, forms (Input, Field, Radio, Checkbox, Select), overlays (Modal, Sheet, Popover, Tooltip), data (DataGrid, Table, Pagination), layout (Sidebar/AppLayout, Card, Tabs), and richer pieces like Kanban, Conversation (chat), DateRangePicker, and a zero-dependency RichTextEditor — plus more on the way.
Every component ships with an inline AI-context block, a machine-readable schema entry, and documented anti-patterns.
Browse the full list with live demos → usevyre.com/docs/components
# React
npm install @usevyre/tokens @usevyre/react
# Vue 3
npm install @usevyre/tokens @usevyre/vue
// Import once at your app entry point
import "@usevyre/react/styles"; // tokens + component styles (one import)
import { Button, Card, DataGrid } from "@usevyre/react";
Full setup guide → usevyre.com/docs/installation
Real, multi-page layouts built entirely from useVyre components:
--vyre-color-semantic-accent not --amber-400usevyre/
├── packages/
│ ├── tokens/ @usevyre/tokens
│ ├── react/ @usevyre/react
│ ├── vue/ @usevyre/vue
│ ├── all/ react-all/ vue-all/ convenience meta-packages
│ ├── ai-context/ @usevyre/ai-context
│ ├── mcp-server/ @usevyre/mcp-server
│ ├── eslint-plugin/ @usevyre/eslint-plugin
│ ├── validate-ai-context/ @usevyre/validate-ai-context
│ └── prompt-templates/ @usevyre/prompt-templates
├── apps/
│ └── docs/ usevyre.com documentation site
└── README.md
Run the docs site locally to browse all component examples and live demos.
Prerequisites: Node.js ≥ 18, pnpm ≥ 9
# 1. Clone and install
git clone https://github.com/gapra/usevyre.git
cd usevyre
pnpm install
# 2. Build design tokens (required — components import CSS variables from here)
pnpm --filter @usevyre/tokens build
# 3. Start the docs dev server
pnpm --filter @usevyre/docs dev
Open http://localhost:4321 in your browser.
Shortcut — tokens build + dev server in one command:
pnpm dev:docs
This project is in early development. Feedback, ideas, and bug reports are very welcome — open an issue to get started.
MIT © Gapra
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @usevyre/mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-gapra-usevyre-context": {
"command": "npx",
"args": [
"-y",
"@usevyre/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@usevyre/mcp-servernpmuseVyre Context works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.