Why It Matters
Component health is the design equivalent of code quality. Healthy components are properly connected to the design system, use tokens instead of hardcoded values, follow naming conventions, and have complete variant coverage. Tracking component health over time reveals whether your design system is being adopted or eroding.
Examples
1
A file health score of 94% indicates high design system compliance with minor issues to address.
2
Component health metrics: 98% connected instances, 100% token usage, 85% naming convention compliance.
3
A dashboard showing component health trends across all product files over the past 6 months.
How BiblioKit Helps
Track component health with ComponentQA's automated scanning. Get instant visibility into design system compliance across your files.
Related Terms
Design System Audit
A systematic review of design files to assess adherence to design system standards, identify inconsistencies, and find components that have drifted from their source.
Detached Instance
A component instance that has been disconnected from its main component, breaking the link that allows automatic updates when the main component changes.
Token Drift
The gradual divergence between design tokens in Figma and their implementations in code, causing visual inconsistencies across platforms.
Design Governance
The policies, processes, and controls that ensure design system standards are maintained, contributions are reviewed, and quality is preserved at scale.
Explore More Design Terms
Browse our complete glossary of Figma and design systems terminology.