LEDGERMACHINE

LM-BREAKPOINT-001

Find duplicate responsive breakpoints

Two media-query widths sit close enough that they may describe the same transition.

What Ledgermachine reports

Two responsive thresholds are very close

Decision, not automatic repair

Merge them when the layout change is shared; keep both when distinct breakpoints prevent a real failure.

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
@media (min-width: 767px) { … }
@media (min-width: 768px) { … }
One possible resolution
@media (min-width: 48rem) {
  /* Keep related layout changes together. */
}

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

    Merge them when the layout change is shared; keep both when distinct breakpoints prevent a real failure.

  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