LEDGERMACHINE

LM-TOKEN-003

Find duplicate design token values

Independent tokens in the same context and category resolve to one value without aliasing each other.

What Ledgermachine reports

Several token names share one value

Decision, not automatic repair

Keep separate semantic names when their roles may diverge; otherwise alias them to one canonical token.

Source example

What this finding can look like

The exact candidate comes from the project’s own tokens and repeated values. This example shows the shape of the issue, not a universal replacement.

Flagged source
:root {
  --text: #1a1a1a;
  --foreground: #1a1a1a;
}
One possible resolution
:root {
  --text: #1a1a1a;
  --foreground: var(--text);
}

Resolution workflow

Fix the source without erasing intent

  1. Inspect

    Review every reported occurrence and the established candidates Ledgermachine found in the same project.

  2. Decide

    Keep separate semantic names when their roles may diverge; otherwise alias them to one canonical token.

  3. Verify

    Make the change in your editor or coding agent, then rescan. Ledgermachine stays read-only and records whether the finding cleared.

Run it on your source

See the evidence behind this rule.

Open a folder locally, inspect the exact occurrences, and decide whether to repair or preserve the difference.

Open Ledgermachine