Open source scanner available now
AI tools generate code that works but doesn't match your design system. subpixel detects drift at every layer — from tokens to product decisions.
npx subpixel init --detect
≡ Products
Catch drift at the code level today. Catch it at the product level next.
Static analysis for design system drift. Catches hardcoded tokens, reinvented components, and accessibility gaps in AI-generated code.
Code drift is a symptom. Product drift is the disease. The Signal Engine connects customer feedback to product decisions.
≡ Getting Started
Point subpixel at your token config and component library. It handles the rest.
Auto-detects your tokens from JSON, CSS custom properties, Tailwind theme, or Figma token export. Ingests your component library from Storybook metadata or TypeScript types.
Run against your full repo or a PR diff. Rule-based checks catch token violations instantly. The AI layer identifies component reinvention with confidence scores.
Interactive fix mode suggests replacements. Add to CI as a GitHub Action to block drift before it merges. Track violations over time as your system evolves.
≡ The Scanner
Every AI tool — Cursor, Copilot, Claude Code — generates UI that compiles but drifts from your system. subpixel catches what linters miss.
Raw hex colors, pixel spacing, and font sizes that should be semantic tokens from your design system.
AI loves to build from scratch. subpixel recognizes when generated DOM matches an existing component in your library.
Hardcoded media queries that don't align with your responsive system. Fragile and inconsistent across surfaces.
Components used with incorrect or deprecated prop combinations that your system discourages.
Missing ARIA patterns, focus management, and keyboard nav that your design system already solves.
Using the right token value but wrong semantic name — like a background color applied to text.
≡ Signal Engine
The Signal Engine ingests what your customers actually say, maps it against what your product actually does, and surfaces what to build next.
Sales and CS call transcripts, objections, churn signals
Internal escalations, customer-facing channels, team signals
Support tickets, resolution patterns, recurring pain points
Product docs, retro notes, internal knowledge bases
Issue backlog, prioritization signals, team velocity context
Issues, PR discussions, contributor feedback, repo activity
≡ FAQ
subpixel is an open-source scanner that detects design system drift in AI-generated code. It catches hardcoded tokens, reinvented components, accessibility gaps, and other patterns that break consistency.
subpixel is tool-agnostic. It scans the output, not the source. Code generated by Cursor, Copilot, Claude Code, or hand-written code — if it drifts from your system, subpixel catches it.
Yes. The scanner CLI is fully open source and free to use. The Pro tier adds CI integration and drift tracking. The Signal Engine is a separate commercial product currently in development.
No. The scanner runs entirely locally. Your code never leaves your machine. The AI component matching uses local models — no code is sent to external APIs.
Linters check syntax and code quality. subpixel checks design system compliance — whether your code uses the right tokens, components, and patterns instead of hardcoded values or reinvented wheels.
The Signal Engine is an upcoming product that detects product-level drift — when your team ships features that don't match what customers actually need. It ingests signals from Gong, Slack, Zendesk, and Notion to surface evidence-backed problem statements.
Open source. Built for teams that ship with AI. Start scanning in three minutes.