Run a detector scan | Impeccable

Check your UI from the terminal.
Scan for known design problems without starting an AI conversation. The detector checks code and rendered pages for issues such as low contrast, overflowing text, common AI design patterns, and drift from your design system.
From your project folder:
Give it one file for a focused check, or a URL to inspect a rendered page:
Source scans inspect UI code and styles. URL scans open the page in a browser, where checks can use the rendered layout. Choose the target that matches what you want to inspect.
Each finding names the rule, identifies the relevant code or element, and explains what to reconsider. Here is a real finding from a small CSS example:
Line 3 · background-clip: text + gradient
The detector recommends a solid text color. Decide whether the gradient serves a purpose in this design.
Fix a real problem, or record a narrow exception for an intentional choice. A clean scan means these checks found no reportable problem; critique can assess the wider design.
Use JSON when a script or CI job needs the results:
Primary findings determine the finding count and exit code. Advisories are additional observations; they do not make a scan fail. Treat code 1 as a scan failure, even if other targets produced findings.
JSON goes to standard output. Human-readable findings go to standard error:
--quiet reduces text output to the final count. --no-advisory hides advisories for one scan.
When a local DESIGN.md exists, the detector uses it to check documented fonts, colors, corner radii, and type sizes. The .impeccable/design.json companion file adds structured token and type-scale data.
Keep the record current with document:
For one scan without design-system checks:
Ignores apply to both manual scans and design hooks. Record the specific value when possible:
That keeps the rule active for other fonts. Configuration & ignores covers file scopes, private exceptions, and removing an ignore later.
Folders are searched for supported UI and style files. HTML scans include linked local CSS. JSX, TSX, Vue, Svelte, Astro, and stylesheet files receive source checks.
Declare extra template extensions, such as Blade or ERB, under detector.extensions. See server-side templates.
The detector checks web interfaces. For native iOS or Android work, use audit for a review suited to the platform.
URL scans use a 1280 × 800 viewport by default. Choose a narrower size to check a mobile layout:
Limit checks to a design domain, or combine domains with commas:
With piped text and no target, the detector reads standard input:
Manual scans read .impeccable/config.json and .impeccable/config.local.json. Turning hooks off does not disable manual scans.
--no-inline-ignores bypasses in-file ignore comments but keeps config ignores. --no-config bypasses both, along with project configuration and local design-system context.
To attach an exception to a file that leaves the repository, use an inline ignore comment.