rms-design-system-engine

agent
Security Audit
Fail
Health Warn
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 7 GitHub stars
Code Fail
  • process.env — Environment variable access in .githooks/private-check.mjs
  • exec() — Shell command execution in .githooks/private-terms.mjs
  • process.env — Environment variable access in .githooks/private-terms.mjs
Permissions Pass
  • Permissions — No dangerous permissions requested

No AI report is available for this listing yet.

SUMMARY

One engine and shared knowledge layer in place of the separate tools and AI skills teams use to check Figma, validate code and write documentation. Connects Figma, code, documentation and decisions: checks library rules, parity and accessibility, writes contracts and usage guidelines, and publishes a living style guide.

README.md

One engine. A clear picture of your design system.

Trust OpenSSF Best Practices: Silver No dependencies Local-first
Use
Claude Code Terminal

The style guide the engine builds, its Status page: parity with Figma, code, documentation and accessibility, scored for every component

Design system knowledge is scattered across tools and workflows that rarely talk to each other. RMS Design System Engine connects Figma, your code and your documentation, checks them against your own rules and brings everything together into one shared knowledge layer. It shows teams their system’s health, what needs attention and exactly what to do next, helping humans and AI agents maintain the system with confidence.


Features

See what is ready at work in the live style guide, which the engine automatically builds.

Audit

Stable
Check your Figma library rules

The patterns, architecture and rules your Figma library is built on, each break listed, with a score for how well you follow them.

Reads Figma
Runs Figma MCP figma-cli Figma Console MCP

Stable
Lint your codebase rules

The patterns, architecture and rules your codebase is built on, each break listed, with a score for how well you follow them.

Reads Vue.js React shadcn/ui CSS Sass
Runs ESLint Stylelint TypeScript

Stable
Measure Figma-code parity

Every difference between Figma and the code in colours, sizes, states and spacing, in every mode, with the fix for each.

Reads Figma Code Connect Vue.js React shadcn/ui CSS Sass Storybook
Runs Chrome Firefox Git

Stable
Test accessibility

Contrast, keyboard focus, touch targets and zoom on every component and state, each failure tied to its WCAG criterion.

Reads Figma Vue.js React CSS Sass Storybook
Runs axe-core Chrome Firefox Screen readers
Follows WCAG 2.2 A / AA WAI-ARIA APG
Documentation

Stable
Write component specs

One contract per component, its props, states, tokens and decisions, that developers and AI agents build from without guessing.

Reads Figma Code Connect Vue.js Storybook
Writes W3C DTCG DSDS llms.txt
Publishes GitHub GitLab

Stable
Maintain usage guidelines

The intent layer, why each component exists and when to use it, kept current where your docs live, with drafts for the gaps.

Reads Figma Vue.js Markdown Storybook
Writes Markdown
Publishes GitHub GitLab
Collaboration

Stable
Publish a living style guide

The team's control center, each component's parity, accessibility, docs and decisions in one place, with who acts on what.

Reads Figma Vue.js Markdown
Runs Chrome Git
Writes HTML CSS JavaScript
Publishes GitHub GitLab

Beta
Try components in a playground

A component's props changed live, in every state and theme, as the code draws it, for design review and visual and functional QA.

Reads Figma Vue.js React Storybook
Runs Vite Nuxt
Creation

Soon
Design themes over your system

A new theme over your system's tokens, its colours, type, corners and spacing, set live in light and dark and kept readable.

Soon
Turn Figma into code

A Figma-only system turned into code, piece by piece, from Figma's exact names and values, with each piece checked once built.

Soon
Turn code into Figma

Anything that exists only in your code, drawn in Figma with its props as properties and its tokens as variables, for review.

Soon
Build from your documentation

Your variables, text styles and components with their variants, built in Figma and in code from your docs, the same every time.

Soon
Generate in Figma from a prompt

Anything your system holds, a component, pattern, template or foundation, described by you and drawn in Figma from its rules.

Soon
Generate in code from a prompt

Anything your system holds, a component, pattern, template or foundation, described by you and written in code from its rules.

Soon
Prototype with your real components

Prototypes built by AI from your real components, each edit checked as it is made, so nothing invented gets past the checks.


Get started

You need Claude Code, Node.js 22+ and Git. Google Chrome and TypeScript 5 are recommended; the installer tells you if they are missing.

  1. Ask Claude Code to install the engine:

    curl -fsSL https://raw.githubusercontent.com/rafaelmatosdasilva/rms-design-system-engine/main/install.sh | bash
    
  2. Restart Claude Code.

  3. Set up your project:

    /rms-design-system-engine set up this project
    

Then ask in plain words, such as /rms-design-system-engine check the button. See every command.


Who it's for

  • Design-led teams working in Figma who want to review their library, document their design system and verify accessibility.
  • Design and engineering teams who need to maintain parity between Figma and code, verify implementations against design intent and catch inconsistencies as designs and code evolve.
  • Code-first teams who want to improve the reliability, accessibility and maintainability of their codebase, document components, track design system health and ensure AI-generated code follows their implementation rules.

Security and enterprise

  • Runs on your machines. No server, no account and no telemetry. It talks only to the services you already use, listed host by host for your firewall.
  • Your data stays yours. Tokens stay in each person's own .env, and code people wrote is never changed: findings come back as patches.
  • Nothing extra to trust. No npm dependencies. Every release is signed and comes with a software bill of materials.
  • Compliance answered. GDPR, SOC 2, ISO 27001, HIPAA and the AI model's terms, each in one line.

For IT and security teams · Security and data · Assurance case · Report a vulnerability


Explore

Built by Rafael Matos da Silva. Released under the MIT License.

Reviews (0)

No results found