check-design-system

To check design-system violations before merging, run checks on recently changed or specified UI files to surface token usage, component-class adherence, typography consistency, and color violations. The audit returns structured findings with line references and suggested fixes.

Yes, you can audit color and typography consistency by specifying target UI files. The check reports color violations, typography consistency issues, and dark mode patterns, returning structured findings with exact line references and suggested fixes.

Yes, the design-system lint check ensures compatibility with common UI frameworks. It enforces adherence to design tokens and component class conventions while validating accessibility where applicable across the audited files.

Design token usage validation audits UI files to ensure component styling adheres to defined design tokens. It catches violations by comparing recent changes against token conventions, reporting mismatches with line references and suggested fixes.

To report dark mode pattern violations, apply the check to files in your repository scope defined by user input or recent changes. It identifies dark mode pattern inconsistencies and returns structured findings with line references and suggested fixes.