chudarin-figma-skills

Five skills for designers: the agent works in Figma from your product's own components and variables.

claude plugin marketplace add schudarin/chudarin-figma-skills
claude plugin install chudarin@chudarin

Why

The agent works inside your design system: your components, your variables, the decisions already in the product.
A similar-looking frame never passes as a component: an instance, a design system update or a new component, nothing else.
The agent doesn't learn the Figma API all over again: the limits, the approaches that work and the checks are in the rules.

Reads the file and reports what the design system holds: components, tokens, patterns, debt. Changes nothing by default.

Maps the flow: every screen and state, entry and exit points, a page structure for the file, before anything is drawn.

Builds new screens and edits approved ones: where the style comes from, a brief per screen, checks after, one element at a time.

Finds detached, orphaned and hardcoded values, shows you a report, and rebinds only after you approve it.

Recorded Plugin API failures and the way around each one. Loads by itself, before the agent writes into your file.

Install the plugin in Claude Code with the two commands above, then restart the agent.
Connect the agent to Figma: type /mcp, pick figma, and log in through the browser.
Start the agent in your project folder and send a link to the frame along with the task.

Check your Figma seat first: Dev and Full allow substantially more tool calls than View and Collab. Limits in the Figma docs

Tell me what worked, where you had to step in, and when the result diverged from what you expected. If something broke, send the session.

claude plugin marketplace add schudarin/chudarin-figma-skills
claude plugin install chudarin@chudarin