⏺ Design system linter for catching design drift. Catches hardcoded colors, spacing violations, and design token drift in your PRs before they merge.

Design system GitHub comment Bot that uses Buoy.

Catches hardcoded colors, token violations, and design drift in your PRs before they merge.

How it works

Buoy runs an open-source scanner in the cloud on every PR. No config needed. Posts a review with every issue with exact file, line, and fix suggestion. One-click committable suggestions let you apply fixes right from the GitHub UI.

What Buoy catches

• Hardcoded colors (#3b82f6 → var(--color-primary))
• Magic numbers (padding: 15px → spacing.4)
• Arbitrary Values (p-[20px] → p-5)
• Inline styles that should use tokens or classes
• Naming inconsistencies and deprecated patterns
• Hardcoded typography, motion, border-width, opacity, radius, shadow, and z-index

Why teams use Buoy

• Catches when Copilot/Cursor generate off-system values
• No manual code review needed for design system compliance
• Track health scores and drift trends over time on the dashboard
• Zero config, unless you want to. Works with React, Vue, Svelte, Angular, and Tailwind
• Builder mode coaches teams toward their first tokens. Established mode enforces them.
• AI-powered summaries explain what drifted and why it matters

Setup

1. Install Buoy on your repository
2. Open a PR with UI changes
3. Buoy scans and comments with any drift detected

Bonus: Reply or ask @ahoybuoy about your design system right in GitHub.

Reply @ahoybuoy to ask questions about your design system.

No API keys needed. No configuration files. Works out of the box.

Pricing

Free for life for the first 100 installs (full features, including AI). Then $25/dev/month for teams who join after.

The open-source CLI is always free for local scanning.

Requirements

• Read access to code, write access to checks, and pull requests