On client missions, I build and maintain Figma design systems with four Claude skills I wrote myself, designed to chain together as a real pipeline.
fds-charte-graphique lays the brand foundations (colors, typography, logos, spacing, effects, grids, radius, stroke) directly in Figma, together with the matching Root variable collection and a WCAG contrast check shown under every color.
fds-design-system picks up from there: starting from those Root tokens, it builds semantic Alias tokens (light/dark), prioritizes a component list aligned with MUI conventions, then builds those components one at a time, in English, accessible and documented.
fds-new-component works at the unit level: it takes a single existing component in a Figma file already structured with Root/Alias/Components and makes it fully tokenized, themed, and accessible, without touching the rest of the system — useful for completing or fixing one isolated component.
fds-audit acts as a global health check: it evaluates an existing design system's token architecture, naming, completeness and accessibility, gives a per-item verdict (keep, improve, rebuild) plus a prioritized action plan, and can then automatically route the accepted fixes back through the other three skills.
All four skills are generic: they work on any Figma file, not just mine, and are free to use on GitHub for anyone who wants to try them or adapt them.