LEDGERMACHINE

LM-EFFECT-003

Find unnecessary !important rules in CSS

A declaration forces precedence with !important.

What Ledgermachine reports

Styles rely on !important

Decision, not automatic repair

Confirm whether layers, specificity, or source order can express the intent. Utility and accessibility overrides can be legitimate.

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
.button { color: red !important; }
One possible resolution
@layer components {
  .button.is-danger { color: var(--status-error); }
}

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

    Confirm whether layers, specificity, or source order can express the intent. Utility and accessibility overrides can be legitimate.

  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