dscheck.config.json

Zero-config works when your repo has an @theme CSS entry or a tokens.css/:root block. The config file makes it explicit — a JSON Schema is published for editor validation ("$schema": "https://oddurs.github.io/dscheck/config.schema.json"), and unknown keys fail fast with a did-you-mean rather than being silently ignored:

{
  // Token sources, relative globs. Merged into one allowed set.
  "tokens": ["app/tokens.css", "app/global.css"],

  // Files exempt from linting entirely (content pages, generated code).
  "ignore": ["app/blog/**", "src/generated/**"],

  // Custom-property names never reported as unknown —
  // for variables injected at runtime (syntax highlighters, next/font).
  "allow": ["--shiki-*", "--font-geist-*", "--header-height"],

  // Matching tolerances (ΔEOK): exact = autofixable, close = confident suggestion.
  "tolerance": { "colorExact": 0.005, "colorClose": 0.03 },

  // CLI severity overrides (plugins use their host's severity config instead).
  "rules": { "no-raw-length": "off" }
}

Discovery walks up from each linted file to the nearest config; nearest wins (monorepos). @import "tailwindcss" in a token source pulls in Tailwind’s full default theme, with your declarations taking precedence; --tw-* internals are always allowed.