design-system-fixer

You can automatically fix design token violations by running a scanner-driven tool that replaces hard-coded colors, spacings, typography, and icon sizes with design-system tokens. It consumes a scanner report to apply deterministic corrections across your UI code.

Yes, you can preview design token fixes by running the tool in dry-run mode. This allows you to review the proposed changes for hard-coded values like colors and spacing across the UI presentation layer before committing them.

Yes, you need a build-capable workstation to run design token linting and fixes. The environment must be able to compile the UI codebase because the tool runs a build after applying changes to verify that no regressions were introduced.

The best way to target a single file for design system token corrections is to use the file targeting flag. This isolates the automated replacement of hard-coded colors, spacings, and typography to one specific path instead of applying changes across the entire presentation layer.

If applying design system token replacements risks breaking the UI build, the tool includes a build verification step that runs immediately after applying changes. This detects regressions early, though you should always use dry-run mode first to review modifications.