Design system governance loop
Define tokens, distribute them to design and code, evaluate pull requests, recommend semantic fixes, resolve findings, and measure compliance over time.
Step 1
Define
Manage canonical tokens and semantic mappings in the token editor. Set the rules your product expects in code.
Step 2
Distribute
Push definitions to Figma, generate CSS and Tailwind artifacts, and expose live values to agents through MCP and skills.
Step 3
Evaluate
Inspect pull requests for raw values and other design-system violations before merge.
Step 4
Recommend
Suggest semantically appropriate token replacements with enough context for developers to trust the fix.
Step 5
Resolve
Apply fixes from audits or PR suggestions, dismiss noise, and record justified exceptions where your policy allows.
Step 6
Measure
Review findings and trends in project insights. See what keeps recurring and which mappings need attention.
Common questions
- What is design system compliance in Vois?
- Vois connects your token definitions and semantic mappings to GitHub pull requests. It flags raw values in diffs and suggests the semantic token that matches your system, so humans and AI-generated code stay aligned with design intent.
- How do GitHub pull request checks work?
- Install the Vois GitHub app on selected repositories. On each pull request, Vois scans changed files for hardcoded colors, spacing, typography, and related violations, then comments with suggested token replacements from your semantic map.
- Does Vois work with AI coding assistants?
- Yes. Vois exposes live tokens and rules through an MCP server so tools like Cursor and Claude can read your system. PR checks catch drift regardless of how the code was written.
Make compliance measurable
Connect tokens to pull requests, recommend semantic fixes, and give agents the same rules your reviewers use.