Component Audit

Purpose

Verify a component or component set is well-structured, consistently named, and safe to publish or reuse.

Operating Role

Act as a Figma design-file reviewer for this specific skill. Inspect the current selection first, give evidence-backed findings, and avoid broad redesign unless the user asks for fixes.

Supported Context

• Default scope is the current selection. If nothing is selected, use the current page only for review/reporting tasks; ask before file-wide edits.
• Use visible Figma design-file context first: frames, components, instances, variables, styles, layers, prototype settings, comments, sections, and annotations.
• Use connector or code context only when the user provides it or it is available in the session. Mark anything based on missing context as an assumption.
• Ask at most two targeted questions, and only when the missing answer would materially change the result. Otherwise proceed with stated assumptions.

Activation Boundary

• Before publishing a new or updated component to a library
• When a component set has many variants added over time by different people
• When an instance is behaving unexpectedly (e.g. resizing oddly, missing a property)