figma-create-design-system-rules SKILL.md skillB
figma-create-design-system-rules from openai/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add openai/skills/figma-create-design-system-rules@git:20260324.0e7823cPins git:20260324.0e7823c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- openai/skills
- Path
skills/.curated/figma-create-design-system-rules/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260324.0e7823c, committed Mar 24, 2026
- First version recorded
- Dec 19, 2025
- Size
- 18,221 bytes
- Repository stars
- 28,831
- License
- none declared
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Create Design System Rules ## Overview This skill helps you generate custom design system rules tailored to your project's specific needs. These rules guide AI coding agents to produce consistent, high-quality code when implementing Figma designs, ensuring that your team's conventions, component patterns, and architectural decisions are followed automatically. ### Supported Rule Files | Agent | Rule File | |-------|-----------| | Claude Code | `CLAUDE.md` | | Codex CLI | `AGENTS.md` | | Cursor | `.cursor/rules/figma-design-system.mdc` | ## What Are Design System Rules? Design system rules are project-level instructions that encode the "unwritten knowledge" of your codebase - the kind of expertise that experienced developers know and would pass on to new team members: - Which layout primitives and components to use - Where component files should be located - How components should be named and structured - What should never be hardcoded - How to handle design tokens and styling - Project-specific architectural patterns Once defined, these rules dramatically reduce repetitive prompting and ensure consistent output across all Figma implementation tasks. ## Prerequisites …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_cqnf7mikymdzhr6c/1f4d7e16ba5325a80da32e2e6bde0ea850ba9287f35f4675d51d55d2f0dc6e2a.json
Then /plugin install figma-create-design-system-rules@markdownregistry-cqnf7mikymdzhr6c in Claude Code. It installs git:20260324.0e7823c, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add openai/skills/figma-create-design-system-rules@sha256:1f4d7e16ba5325a8The line at the top of this page pins the label git:20260324.0e7823c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_cqnf7mikymdzhr6c)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in openai/skills/figma-create-design-system-rules since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of figma-create-design-system-rules from somewhere else? Ask it: where did my figma-create-design-system-rules come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between Dec 19, 2025 and Mar 24, 2026, about one every 32 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260324.0e7823c latest | 2026-03-24 | 0e7823c | 18,221 B | B | view · diff |
| git:20251219.136d58a | 2025-12-19 | 136d58a | 17,511 B | B | view · diff |
| git:20251219.3b1b766 | 2025-12-19 | 3b1b766 | 16,944 B | B | view · diff |
| git:20251219.f4d6fda | 2025-12-19 | f4d6fda | 16,880 B | B | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/figma-create-design-system-rules/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (18221 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
openai/skills · 28,831 stars · license none declared · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cqnf7mikymdzhr6c GET https://markdownregistry.com/api/v1/resolve?ref=openai/skills/figma-create-design-system-rules GET https://markdownregistry.com/api/v1/blob/1f4d7e16ba5325a80da32e2e6bde0ea850ba9287f35f4675d51d55d2f0dc6e2a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.