Drift Types Detected
Buoy categorizes drift by severity to help you prioritize fixes
Deprecated Patterns
Components marked @deprecated still in use
Orphaned Components
Components in code but not in design
How Drift Detection Works
Scan
Buoy parses your codebase to build a map of all components, props, and style values.
Analyze
Compares against your design system config to identify patterns that don't match.
Report
Outputs drift signals with severity, location, and suggested fixes.
Step 1: Find Drift
Every issue includes the exact file, line, and what to change.
Step 2: Auto-Fix
One command applies all safe fixes. No manual editing required.
What You Get
Clarity, not just data. Every scan ends with concrete next steps.
Auto-Fixes Applied
Hardcoded colors → tokens. Deprecated components → current ones. Done automatically.
buoy fix --auto Manual Review Queue
Complex issues get a clear explanation and exactly what needs to change.
buoy fix --interactive Coverage Score
Before: 52%. After: 68%. Show leadership exactly how much you improved.
buoy status Visible Outcomes
👩💻 For Developers
- ✓ No guessing — exact file, line, and fix
- ✓ Auto-fix handles the tedious work
- ✓ PR checks catch issues before review
- ✓ Less time debating, more time building
📊 For Leaders
- ✓ Real adoption numbers, not estimates
- ✓ Track improvement week over week
- ✓ Prove design system ROI with data
- ✓ Identify which teams need help
Why Design Drift Matters
Without Drift Detection
- ✗ Inconsistent UI across the app
- ✗ Design system becomes optional
- ✗ Harder to maintain and update
- ✗ No way to measure adoption
With Buoy
- ✓ Consistent, cohesive UI
- ✓ Design system enforcement
- ✓ Easy global updates via tokens
- ✓ Real adoption metrics