deviation-tracker

To classify design system deviations, this Skill parses code analysis findings and categorizes them as accidental, intentional, or needs-review. It uses inline @ds-deviation comments to capture developer justifications and outputs a structured YAML deviation report.

An intentional design system deviation is a deliberate code departure tracked via @ds-deviation inline comments. The Skill parses these comments to understand developer justifications and classifies the finding accordingly, preventing false positives in the YAML report.

You configure the deviation report path and classification settings in the react-craft.config.yaml file. The Skill reads this configuration file to determine where to output the structured YAML deviation report.

Yes, you can automate design system code review by running code analysis tools and passing the output to this Skill. It automatically categorizes deviations and only flags findings as needs-review when a developer justification is missing or rules are ambiguous.

The limitation of using inline comments for deviation tracking is that missing @ds-deviation tags will cause findings to be flagged as accidental or needs-review. Accurate classification requires developers to actively document intentional departures in the code.

Yes, deviation tracking works with YAML report formats by generating detailed structured YAML files. The Skill outputs the classified accidental, intentional, and needs-review findings directly into a YAML report for the design system team to review.