rafaelmatosdasilva

Rms Design System Engine — AI skill for Claude Code

AI community

The core of your design system.

How to install Rms Design System Engine

This entry records only its repository, not the path inside it, so there is no exact command to give. Open rafaelmatosdasilva/rms-design-system-engine and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Rms Design System Engine does

The core of your design system. A maintenance engine that keeps designers, developers and AI agents aligned, and Figma and code in parity. It generates the style guide, documentation, contracts and intent layer from code and Figma, then checks every change against the system, including accessibility, telling you what to fix and where.

Alternatives in AI

  • Open Pencil — AI-native design editor 8k ★
  • Cursor Talk To Figma MCP — TalkToFigma: MCP integration between AI Agent (Cursor, Claude Code, Codex) and Figma, allowing Agentic AI to c 7k ★
  • 09 Query Engine — Prompt 09: Get the QueryEngine (Core LLM Loop) Functional 2.3k ★

README

rms-design-system-engine

The engine that maintains your design system.

It keeps designers, developers and the AI tools they use aligned on one design system. From your code and Figma it creates the style guide, the documentation and the contracts they all work from, then checks every change against them.

It keeps your code in parity with your design in Figma. It compares what was built (by a developer or by an AI) with what you designed: the colours, sizes, fonts, spacing, components and their states. When something is different, it tells you what, where, and how to fix it, in plain words. It also checks accessibility.

Have only Figma? It helps Claude build your design system in code from it, one piece at a time: it gives Claude the exact facts from Figma first (every token in every mode, the sizes, the variables, the role of each component) and checks each piece against Figma before Claude says it is done.

Why use it

  • One system for everyone. Designers, developers and AI tools work from the same style guide, documentation and contracts, made from your code and Figma, so the design system stays one system.
  • Catch differences early. See when the code and Figma stop matching, before your users do.
  • Exact fixes, not vague notes. Every difference comes with the file, the line and the right token to use.
  • Safer AI building. When an AI builds screens, every change it makes is checked against your real components and tokens, and for accessibility, and it is told how to fix what does not match.
  • Accessibility included. Text that is hard to read, buttons with no label, things you cannot reach with the keyboard.
  • The same answer every time. The checks are fixed rules, not opinions.
  • You stay in control. It changes Figma only to state what your code already has, such as a component's role, and only after you approve the list. It never changes your code unless you ask. An AI cannot accept a difference or switch a check off without a