design-systems plugins

by Thiago Xikota

Agent skills for real Figma files: Plugin API gotchas, checks before and after every write, comments to verified fixes, handoff gate.

by Matt Corbett

Design-systems engineering team — agents (design-systems-architect, design-tokens-and-component-engineer) answering 'what is the shared system every product surface builds from, and how is it versioned and adopted?': design-token architecture (primitive → semantic → component tiers, theming/dark-mode/multi-brand), component-library API design (composition vs configuration, controlled/uncontrolled, a11y baked in), Storybook/docs, Figma→code token pipeline (Style Dictionary), and versioning/adoption (semver, changesets, codemod-backed breaking changes, deprecation, governance, adoption metrics). skills, a knowledge bank (a Mermaid decision tree + a dated 2026 tooling reference). Distinct from frontend-engineering (builds apps that CONSUME the system), accessibility-engineering (WCAG compliance), and web-design (site visual design) — this team owns the SYSTEM those build from. Tooling specifics volatile: retrieval-dated + verify-at-use. Needs ravenclaude-core.

by Sergey Chudarin

Five skills for agents that design in Figma, one per stage of the work: plan flows, audit a design system, design screens, write to the Plugin API without silent failures, repair detached variable bindings.

by farbodjavan

Evidence-based, multidisciplinary UX/UI analysis and implementation-ready redesign workflows with privacy-gated public evolution.

by Michael Meaney

Multimodal presentation engineering from quick reference reconstruction to governed editable PowerPoint decks.

by Proto Labs

Proto on your laptop: set up your account, import your product's design system, build prototypes, and serve them at public URLs, driven by your coding agent.