figma-analyzerlisted
Install: claude install-skill YevheniiaQA/qa-agent-toolkit
# Figma Analyzer
A design is a specification that nobody writes down in words. Screenshots are not
enough — the layer structure carries states, variants, and constraints that
determine whether two test cases exist or one.
## Disabled integrations
Follow `qa-conventions` → *Disabled integrations* for Figma (`figma`): read `INTEGRATIONS`, skip a
system that is not listed, report it as `➖ <system> disabled for this project`, never route
around a `qa-guard` block.
**Local alternative:** work from exported frames or screenshots the engineer supplies and say which states they cover. Without either, mark every design-dependent check as blocked on the design rather than inferring the UI from the requirements.
## What to extract
For every screen in scope:
1. **Interactive elements** — buttons, inputs, selects, toggles, links. Record the
visible label, the element type, and any variant names (`primary/disabled`,
`input/error`).
2. **States and variants.** This is the highest-value output. A component set with
`default / hover / focus / disabled / error / loading` implies six checks.
A missing state implies an open question.
3. **Exact texts.** Labels, placeholders, helper text, error messages, empty-state
copy, button captions. Scenario assertions quote these verbatim, so copy them
character for character including punctuation.
4. **Constraints** — max lengths visible in the design, character counters,
responsive breakpoints, truncation behaviour.
5. **Navig