Skip to main content
LintKit ships with 24 rules across six categories. Every rule can be toggled on or off in Settings, and each finding carries a severity level that tells you how urgently it needs attention.
The brokenVariables rule always runs and cannot be toggled off — broken variable references are too dangerous to ignore.

​
Understanding severity levels

Every finding LintKit reports is assigned one of three severity levels. These levels determine sort order, dashboard impact, and handoff readiness. Three findings showing error (red), warning (yellow), and info (blue) severity badges
Start by resolving all error findings first — they represent broken connections and hard violations. Then work through warn findings, which are the most common category. Treat info findings as cleanup opportunities.

​
What “library-only” means

Some rules are marked library-only in the table below. These rules only produce findings when you scan a file that is published as a Figma library. They detect problems that only matter to library maintainers — unused styles, hidden components, missing descriptions, and incomplete variables. If you scan a regular design file, library-only rules silently return zero findings. You do not need to disable them manually. See Library mode for full details on how LintKit adapts when it detects a library file.

​
Fix confidence

Every finding includes a confidence level that tells you how safe the suggested fix is. This determines whether LintKit shows a one-click Apply Fix button or provides manual instructions instead.
Bulk fix (Pro) processes all findings in a category at once. It only applies high-confidence fixes automatically and skips low-confidence findings.

​
Rule categories

Styles

Orphaned fills, text, strokes, effects, grids. Plus duplicate and unused style detection.

Layout and positioning

Spacing scale, corner radii, stroke weight, fractional pixels, auto-layout suggestions, grid alignment, absolute positioning.

Cleanup and structure

Hidden layers, empty frames, single-child groups, default names, forbidden patterns.

Components and libraries

Unapproved libraries, broken instances, deep nesting, hidden components, missing descriptions.

Accessibility

WCAG contrast checking, broken variable references, variable completeness.

​
Full rule table

Rules marked library-only only produce findings when you scan a published library file.

​
Where to start

Different teams have different priorities. Here is a recommended order for enabling rules based on your role.
Start with rules that catch handoff problems:
  1. Orphaned fills, text, strokes — the most common findings. These catch layers disconnected from your design system.
  2. Contrast — catches accessibility violations before code review.
  3. Cleanup — removes hidden layers and empty containers that confuse developers.
  4. Fractional pixels — prevents blurry rendering in production.
  5. Layer naming — stops “Frame 47” and “Rectangle copy 3” from reaching dev handoff.
Once comfortable, enable Spacing scale and Corner radii after configuring your design system values in Settings.
Start with library health rules:
  1. Unused styles — find styles no one is using so you can deprecate them.
  2. Duplicate styles — consolidate near-identical styles cluttering your library.
  3. Variable completeness — catch missing mode values and broken aliases before consumers hit them.
  4. Hidden components — check which components are hidden from publishing.
  5. Missing descriptions — ensure every style and component is documented for consumers.
  6. Nested components — identify performance bottlenecks from deep nesting.
Then enable Unapproved libraries with your approvedLibraryKeys to enforce library governance across your org.
Start with rules that are enabled by default and require no configuration:
  1. Cleanup — instant wins. Remove hidden layers, empty groups, and single-child wrappers.
  2. Orphaned fills and text — connect everything to styles.
  3. Fractional pixels — snap everything to the pixel grid.
  4. Auto layout suggestions — find frames that should use auto layout.
  5. Layer naming — rename “Frame 1” before anyone sees your file.
These rules work out of the box with zero configuration.

​
Findings and fixes

Every finding includes:
  • A severity level — info, warn, or error
  • Affected nodes — click to select them on the canvas
  • A suggested fix — apply it with one click, or bulk-fix all instances (Pro)
Some findings offer multiple fix options. For example, an orphaned fill might suggest linking to an existing style, binding to a variable, or creating a new style.