Evil Martians’ eight-part framework for keeping AI-built interfaces consistent. Component contracts say when to use and not use each component, an inventory lets agents shortlist components before reading any code, and a design linter fails the build on a raw hex color. The agent skill is published too, split into craft and use workflows.

Anton Lovchikov, Head of Design at Evil Martians, makes the case that ​“a designer’s main job isn’t drawing screens. It’s pulling rules out of chaos and making sure they’re followed.” His proof is a 700-line localization refactor, after which Claude rewrote half the strings. The fix was a three-layer system of product principles, copy rules traced back to them, and skills built on those rules. Now when he dislikes a string, he asks Claude which rule produced it and fixes the rule.

Brett McMillin, Designer Advocate at Figma, runs a skill that pulls user personas from a Notion page and critiques selected frames as one persona, in his demo a fintech app for teens. The findings land as annotations on the canvas covering comprehension, findability, visual hierarchy and trust, and the skill is told never to touch the design. ​“Nothing will take the place of actual user testing and talking to our customers.”

Jakub Antalik packaged all seven Libraries.dev effects into an agent skill. The most useful command is libraries review. It scans your project and returns a per-file list of spots where an effect fits (waiting states, chat inputs, mic buttons, bot avatars) without editing anything. Then libraries apply installs the package and wires it to real app state.

Kailash rounds up ten design skills from the ui​-skills​.com directory, including Anthropic’s frontend-design, Emil Kowalski’s apple-design and emil-design-eng, Meng To’s beautiful-shadows, Addy Osmani’s accessibility, and Paul Bakaus’s adapt. Jakub Krehel’s better-interface makes the list too, after showing up in Miggi’s agent skills roundup in Issue #259.

Karl Koch, Design Engineer at DuckDuckGo, published 11 custom skills to the Figma Community, ported from his open-source dxe set. Run /dxe orchestrator and you get his whole design engineering review in order: intent (write-first-design, subtractive-design), platform (semantic-html-first, modern-css-html), feel (fluid-design, interface-affordances, product-delight), bridge (design-engineering), then shipping (ai-output-judgement, prototype-to-production).

The skills demo is the one to watch. Rodrigo calls a slash command for a skill his teammate Tammy wrote in plain English, carrying her own design-review conventions, and the agent returns the critique as annotations right on the canvas. Team practice becomes a callable command.

“MCP gives your AI reach. Skills give it a recipe.” Murphy Trueman compresses two acronyms into one sentence you can actually hold onto. MCP is access: Claude reading your real Figma file, walking every fill on a button set and finding the fourteen layers still on raw hex, all of them on hover and disabled states. A skill is the playbook it follows once it’s in there. Their rule for writing one is the third time you catch yourself explaining the same preference, write it down.

The post above shows the skills, this one shows the plumbing. Miggi builds 3 skills: a type scale generator that also writes the variables, an image audit that drops a DPI card beside every image, and Shader Starter, which pairs neatly with the shaders update below.

Miggi rounds up ten community skills for the Figma agent, though the real news is in the first line: you can now author skills inside Figma. Ask the agent to draft one using a design frame as reference, preview it, then keep iterating in chat or open the markdown editor for manual changes. Emil Kowalski’s /find-animation-opportunities, which scans a file for places that don’t animate but should, and Jakub Krehel’s /better-interface which catches the details your interface is missing, are the ones I’d install first.