AI coding tools are fast—but they don't know your design system. They'll write #3b82f6 when you have --color-primary. They'll use padding: 17px when your spacing scale is multiples of 4.
Buoy watches for these issues and helps you fix them.
The design system your coding agents check before they ship: tokens plus exact UI fixes.
Your shipped code is the design-system source of truth. Declare the packages you
own, then use Buoy to map adoption, unmanaged UI surface area, and the blast
radius of a component or token change. Figma and other design tools can remain
optional inputs; they are not required for the system map.
buoy system map # Canonical system vs unmanaged surface area
buoy system impact Button # Consumers and migration risk for a change
buoy system impact color-primary --kind token
This is the foundation for cloud adoption trends, deprecation planning, and
AI-assisted iteration reporting: every result is derived from code and can be
attributed to a repository path and owner.
Quick Start
# See your design system immediately (zero config)
npx ahoybuoy show all
# Add project configuration and local integrations when ready
npx ahoybuoy dock
No config needed. Buoy auto-detects your framework and starts working immediately.
What It Catches
Issue
Example
Hardcoded colors
#ff0000 instead of var(--color-primary)
Arbitrary spacing
padding: 17px instead of design scale
Tailwind escape hatches
p-[13px] instead of p-4
Naming inconsistencies
ButtonNew, ButtonV2, ButtonOld
Unused components
Defined but never imported or rendered
Semantic mismatches
Same prop typed string in one, number in another
Repeated patterns
Same Tailwind classes copy-pasted 5+ times
Framework sprawl
React + Vue + jQuery in same codebase
Detached components
Instances without main component
Commands
buoy
├── show # Read design system info (for AI agents)
│ ├── components # Components in codebase
│ ├── tokens # Design tokens found
│ ├── drift # Design system violations
│ ├── health # Health score
│ ├── history # Scan history
│ ├── config # Current .buoy.yaml configuration
│ ├── skills # AI agent skill files
│ ├── agents # Configured AI agents
│ ├── context # Design system context in CLAUDE.md
│ ├── hooks # Configured hooks
│ ├── commands # Installed slash commands
│ ├── graph # Knowledge graph stats
│ ├── plugins # Available scanners
│ └── all # Everything combined
├── drift # Drift detection and fixing
│ ├── scan # Scan codebase for components/tokens
│ ├── check # Pre-commit drift check
│ ├── fix # Suggest/apply fixes
│ └── ignore # Ignore existing drift
│ ├── all # Ignore all current drift (requires --reason)
│ ├── show # View ignored drift signals
│ ├── add # Add new drift to ignore list (requires --reason)
│ └── clear # Remove ignore list
├── rescue # Complete measure → repair → guard → prove journey
│ ├── plan # Build a local baseline and repair plan
│ ├── apply # Apply reviewed safe fixes on a new branch
│ ├── verify # Run detected typecheck/test scripts
│ ├── guard # Record reviewed legacy drift with reasons
│ ├── report # Generate JSON, Markdown, and HTML evidence
│ └── rollback # Restore local pre-Rescue backups
├── dock # Dock tools into your project
│ ├── config # Create .buoy.yaml
│ ├── skills # Create AI agent skills
│ ├── agents # Set up AI agents
│ ├── context # Generate CLAUDE.md context
│ ├── hooks # Set up hooks (--claude for self-validating AI)
│ ├── commands # Install Claude slash commands
│ ├── plugins # Show available scanners
│ ├── tokens # Generate/export design tokens
│ │ ├── compare # Compare token sources
│ │ └── import # Import tokens from Figma/CSS
│ └── graph # Build design system knowledge graph
│ └── learn # Learn patterns from codebase
└── ahoy # Cloud features
├── login # Authenticate
├── logout # Sign out
├── status # Account + bot + sync status
├── github # Set up GitHub PR bot
├── gitlab # Set up GitLab PR bot (soon)
├── billing # Manage subscription
└── plans # Compare pricing
For AI Agents
Coding agents hardcode values because they never read your token file. Give them Buoy as an MCP server:
npx @buoy-design/cli mcp install claude # or cursor, codex, windsurf, all
Claude Code (and any MCP client) gets four tools: list_design_tokens, find_token_for_value
(#1a73e8 → --color-primary), check_ui_against_design_system (line-level, with the token and an exact line edit)
and design_system_context. Claude Code also gets a PostToolUse hook that checks every style
file it edits and hands the fixes back before it moves on. See docs/integrations/mcp.
In Claude Code, the plugin bundles all of it: /plugin marketplace add ahoybuoy/buoy, then /plugin install buoy@buoy.
To review every pull request as well, install the free GitHub App; no Buoy account is needed.
The show command outputs JSON for AI agents to consume:
# Get everything an AI agent needs
buoy show all --json
# Just drift signals
buoy show drift --json
# Components inventory
buoy show components --json
Rescue keeps ambiguous findings review-only, runs detected project checks after
applying high-confidence changes, and retains local backups for rollback. It does
not commit, push, open a pull request, or upload source code. See
docs/rescue.md for the complete workflow.
Configure Your Project
buoy dock
Smart walkthrough that sets up:
.buoy.yaml — Project configuration
AI agent skills — For Claude Code, Copilot, etc.
CLAUDE.md context — Design system documentation
Git hooks — Pre-commit drift checking
Configure severities per drift type
# .buoy.yaml
project:
name: my-app
drift:
severity:
hardcoded-value: critical
naming-inconsistency: warning
# Ignore specific drift (filter by type, file, component, token, value, severity)
ignore:
- type: hardcoded-value
file: "src/legacy/**"
- severity: info
# Promote matching drift to a higher severity
promote:
- type: hardcoded-value
file: "src/components/**"
to: critical
reason: "Design system components must use tokens"
# Enforce — always treat matching drift as critical
enforce:
- type: naming-inconsistency
component: "^Button"
reason: "Button naming is standardized"
health:
# CI gate — exit code 1 if health score falls below threshold
failBelow: 70
Drift Detection
Quick Check
buoy drift check
Fast pre-commit hook friendly. Exits with error code if drift found.
For brownfield projects, ignore existing issues and only flag new ones:
buoy drift ignore all -r "Legacy code before design system" # Ignore all current drift with reason
buoy drift ignore add -r "Third-party components" # Add new drift to ignore list
buoy drift ignore show # View ignored drift with reasons
buoy drift check # Only fails on new drift
A reason is required when ignoring drift to maintain accountability.
Repos scanned by Buoy Cloud get a live score badge for the README:
[](https://buoy.design)
Green at 80+, yellow at 60+, red below. It updates within five minutes of each scan.
PR Comments with Buoy Cloud
# Set up GitHub PR bot
buoy ahoy login
buoy ahoy github
The GitHub bot automatically comments on PRs with drift analysis.
AI Guardrails
Keep AI coding assistants (Copilot, Claude, Cursor) aligned with your design system:
# Set up AI agents with design system context
buoy dock agents
Creates:
AI Skills — Design system knowledge for Claude Code
Claude Hooks — Auto-inject context at session start
CLAUDE.md — Project-specific AI instructions
Self-Validating Agents (Claude Code)
Turn Claude Code into a self-correcting agent. When Claude writes a component, Buoy checks it and feeds corrections back automatically:
buoy mcp install claude # MCP server + line-level hook (recommended)
buoy dock hooks --claude # hook only, component-level
This installs a PostToolUse hook that:
Claude writes/edits a component file
Hook runs buoy drift check on the modified file
If drift detected, feedback returns to Claude
Claude self-corrects without prompting
Example feedback Claude receives:
⚠️ Design drift detected in Button.tsx:
• hardcoded-value: Component "Button" has 3 hardcoded colors: #3b82f6, #ffffff, #1e40af
Run `buoy show drift` for full details.
Works with React, Vue, Svelte, and Angular components. Skips test files and configs.