Figma design system rules
Writes project rules for turning Figma designs into code into CLAUDE.md, AGENTS.md or a Cursor rules file, based on Figma's rule template and an analysis of the codebase. Use when setting up an agent for regular Figma-to-code work in a repo.
figma-create-design-system-rules- Author
- OpenAI
- Source
- openai/skills/skills/.curated/figma-create-design-system-rules @ 49f948f
- License
- Figma Developer Terms
About this skill
What it does
The skill writes a rules file that tells a coding agent how this repository turns Figma designs into code, so the conventions hold in every session. It starts with the Figma MCP tool create_design_system_rules, passing the project's languages and framework, and follows the template it returns. Then it reads the codebase: component folders, styling approach, token files, naming and props, state, routing, import aliases.
The rules have fixed parts: where components live and how they are named, styling and token rules ("never hardcode colours, use tokens from …"), the Figma flow (design context, screenshot, assets, translation, visual check), asset handling, and project conventions for tests, accessibility and performance. Critical lines get an IMPORTANT: prefix. The file goes where the agent reads it: CLAUDE.md or .claude/rules/figma-design-system.md for Claude Code, a section appended to AGENTS.md for Codex (32 KiB combined limit), .cursor/rules/figma-design-system.mdc with description, globs and alwaysApply frontmatter for Cursor. The agent then tries the rules on a simple component and refines them.
Helpers: references/rule-template.md, a skeleton of the sections, and scripts/check_agents_md.sh, which only reports whether AGENTS.md exists at the repo root.
When to use it, and when not
Use it once per project before regular Figma-to-code work, when onboarding an agent to a repo with established patterns, or after conventions change.
If Figma work is rare, loading Implement a Figma design in code when needed may be enough; a root rules file costs context in every session.
How to run it
We do not copy this skill: its files fall under Figma's Developer Terms, not an open licence. Install it from the author's repository with the button to the source; in Codex the route is $skill-installer figma-create-design-system-rules, for another agent copy the folder into its skills directory. OpenAI has marked openai/skills deprecated; openai/plugins no longer has this skill. It needs the Figma MCP server.
- Claude Code:
/figma-create-design-system-rules, or ask for the skill by name. - Codex:
$figma-create-design-system-rules. - Cursor: type
/in the Agent chat and pickfigma-create-design-system-rules.
Example: /figma-create-design-system-rules React with CSS Modules, tokens in src/styles/tokens.css. Write the rules into CLAUDE.md.
How it differs from similar skills
AGENTS.md and CLAUDE.md writer writes a general instruction file under 60 lines and makes CLAUDE.md a symlink to AGENTS.md; a Figma section can push that file past its budget, so with both, prefer the separate .claude/rules/ or .cursor/rules/ file. Writing for agents teaches how to word instructions, with no Figma template. Figma MCP design context carries the same flow inside a skill instead of a project file.
Install
This skill is not copied to the catalog: its licence does not allow it. Install it from the author's repository.
Connect through AnyModel API
This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.
AnyModel