Figma published 10 skills their community
A few that stuck with me:
- /find-animation-opportunities – scans a design and tells you what should animate, and what definitely shouldn't.
- /ui-state-expander – turns one screen into the full set of states: loading, empty, error, edge cases.
- /component-handoff – turns a component into ready-to-share documentation on the canvas.
- /analyze-components – a component audit: orphans, duplicates, broken naming.
- /superfuture-design-review – a crit in a traffic light system: red blockers, yellow fixes, green "this works".
Top comments (1)
The state expander is the one that changes the economics, and it is easy to under-rate because it reads like a convenience.
A missing empty state costs almost nothing while the work is still text. The same gap found while you are assembling components is a different problem, because now you are inventing a design out of flow, with everything else already decided around it. Expanding states at design time does not really save time. It moves the discovery to the cheapest moment it can happen.
Curious how analyze-components handles the naming half. Orphans and duplicates are structural, so a tool can find those without knowing anything about you. Broken naming is not structural. Broken against what? That rule usually lives outside the file, which tends to be why the naming drifted in the first place.