Figma Enhance — Component Properties & Audit for Your File

After a frame has components and variables, the last gaps are easy to miss. A button whose label is baked into each variant cannot take text from outside. Two components named Card / Large and Card / Small are really one component with a size. A text style may exist but not be applied. This skill scans for those gaps, shows them in a ranked table, and fixes only the ones you pick.

What it does

• Finds standalone components that share a name prefix and structure and could become one variant set
• Finds components with no Text, Boolean, or Instance Swap properties, and adds them so the text and nested parts can be set on each instance
• Finds colors, font sizes, and spacing that are not bound to variables, and Text Styles whose font size is not bound to a variable
• Finds invisible (0 percent) or duplicated fills and strokes, and text that matches an existing Text Style but does not use it
• Ranks the findings, asks which to implement, and asks before adding anything to a library collection
• Re-checks instance text, images, and sizes after every change and reports counts, not just "done"

How it works

1. Give it a Figma page, frame, or section URL
2. It scans the components across the whole page, and the frame you gave it for bindings and fills
3. It shows a ranked table of proposals
4. You choose all, some by number, or report only
5. It implements the chosen items, verifies the instances, and gives a final report

Includes field notes for the Figma Plugin API

The skill ships with a reference of 21 known pitfalls in writing to Figma through use_figma. It also carries the fixes learned from merging variants: sizes that collapse after variants are combined, instance text that resets, and images that fall back to the master's photo. The skill opens only the entry that matches a symptom.

What it is not

It does not build a first structure. If the file has no variables and no components yet, it tells you to run a tidy-up, tokenize, or componentize step first. On a file that has just been through those steps, expect a short report: in our example run, the only gap left was component properties.

Requirements

Runs inside an agent connected to the official Figma MCP server, the same connection used for implementing Figma designs as code. Needs edit access to the Figma file, because it changes components in place. Duplicate the file first if you want a way back. No local file access and no arbitrary network calls.

Try it free first

Try it Free on Agensi runs on Agensi's servers, which have no connection to your Figma file. Use the example session above to see the flow and the kind of report you get; the installed skill works on your real file through your own Figma MCP connection.

Works well with

Run it last, after a tidy-up, tokenize, and componentize step, as a polish pass.

More from KMRVID

The full Claude Code skill bundle for Figma, Tailwind and Astro workflows is available on Gumroad: https://gaspanik.gumroad.com/l/kmrvid-claudeskills