Expanding Your Figma Audit: Six Checks, One Command

The previous guide covered the basics: connect Antigravity (or Cursor) to Figma via Dev Mode MCP, set up spacing and variable audit rules, run /audit-figma and get a structured violation report in under a minute. Practical setup, beginner level, copy-paste configuration.

This one extends it.

Four additional audit rules bring the total to six checks, all triggered by the same single command. The new rules cover accessibility (WCAG AA contrast ratios, text size minimums, touch target dimensions), typography consistency (font family compliance, line height, text alignment), component integrity (detached instances and manual property overrides), and layer hygiene (unnamed layers, hidden elements, empty groups).

These are the categories that design leads and reviewers typically catch by eye during critique. The difference is that checking them manually across 40 frames takes time most teams don't have before handoff. Written as rules, they run programmatically.

A few design decisions worth calling out. The accessibility rule is explicit about what it can and cannot check. Color contrast works reliably for solid fills and approximates for gradients. Focus states can't be read if they aren't present on the page, so the rule adds a reminder block to verify them in the component library.

The component integrity rule explicitly distinguishes variant selection from manual override and skips anything it cannot confirm. When in doubt, it doesn't flag it. Fewer false positives, more trustworthy output.

Same principle as before: the AI reads and reports. You validate and act.