Audit 500 Components in 10 Minutes

1. 01

   Scan

   Inventory every component across Figma and code

2. 02

   Violations

   Flag token misuse, naming issues, broken patterns

3. 03

   Missing docs

   Components without specs, props tables, or usage notes

4. 04

   Report

   Prioritized list with severity and ownership

5. 05

   Fixes

   Ship patches, update baselines, close the loop

Why This Matters for Your Design System

Most design system teams audit their components once a year. Some never do it at all. Not because they do not care, but because checking 500 components by hand takes an entire day, and nobody has an entire day.

This workflow cuts that to about 10 minutes of machine time. Tidy scans your Figma file and flags naming violations, missing descriptions, and broken token references automatically. Claude then turns that raw report into a prioritized plan and drafts the fixes. You review and approve instead of hunting for problems.

The two halves of the workflow

Tidy is the scanner. Claude is the triager. Tidy is fast and literal: it finds every component that breaks a rule, but it hands you a flat list with no sense of what matters. A 500-component library can return 300 flags, and staring at 300 flags is its own kind of paralysis.

Claude closes that gap. You hand it the raw export and it does the part a human would otherwise do by hand: cluster the issues, rank them by blast radius, and draft the actual fixes. You stay in the approve-or-reject seat the whole time.

The Guide

Step 1: Run the Tidy audit

Open your design system file in Figma and run Plugins → Tidy → Audit. It scans every component in the file and flags three things: naming that breaks your convention, missing descriptions, and broken or raw token references. Let the scan finish before you touch anything.

Step 2: Export the report

Export the results as markdown or CSV so the report lives outside Figma. This matters for two reasons: your team can see it without opening the file, and you can paste it into Claude in the next step. A report trapped inside a plugin panel is a report nobody acts on.

Step 3: Hand the report to Claude and triage

Paste the exported report into Claude with your convention so it can sort signal from noise:

You are a design systems lead triaging a component audit.
Here is the raw Tidy export: [paste report]

Our naming convention is: category/component-name (kebab-case).

Group the issues into: (1) breaking — components other files
depend on, (2) cosmetic — naming and casing, (3) missing docs.
Within each group, rank by how many other components or files
reference the flagged item. Return a markdown table:
Component | Issue type | Severity | Why it matters.

Now you have a plan, not a pile. The components everyone depends on rise to the top, and the cosmetic noise sinks.

Step 4: Let Claude draft the fixes

For the two slowest categories, naming and descriptions, let Claude write the first draft. For descriptions:

For each undocumented component below, write a one-line
description: what it is, when to use it, when not to. Match
this voice: [paste two of your existing good descriptions].
Keep it under 20 words. Do not invent props I did not list.

For renames, ask for a mapping table (old-name → new-name) so you can review the whole rename plan in one pass before applying any of it. The constraint about not inventing props matters: without it, Claude will confidently describe states your component does not have.

Step 5: Apply, publish, and re-audit

Work through the approved fixes in Figma: rename, paste the drafted descriptions, rebind the broken tokens. Publish the library so consumers get the update. Then run Tidy again. The second report should be visibly shorter. That delta, fewer flags than last week, is the number you take to your team, not a slide.

Results

• Before: 4+ hours of manual checking
• After: 10 minutes with Tidy
• Typical findings: 15-30% of components have naming issues, 60%+ missing descriptions

Exercise

Run Tidy on your real library and triage the top issue

30 min

1. Run the audit on your library file

   Open your design system library in Figma. Run Plugins then Tidy then Audit. Let the scan finish. Export the report as markdown or CSV so it lives outside Figma.

   • The report names every component, not just “some components”
   • Each flagged component has at least one reason (naming, missing description, bad token reference)
   • You saved the report to a file you can share with your team

2. Pick the single highest-impact fix and ship it today

   Sort the report by “most consumers affected” if the export supports it, or by the count of flagged instances. Pick the top row. Fix that one component in Figma: rename it, add the description, rebind the token. Publish the library.

   • One real component in your library is fixed, not a demo
   • The next run of the audit shows one fewer flagged component
   • Your team can see the change in the library update notification, not a slide deck