agentmods.dev

generate-figma-screen

generate-figma-screen is a skill for Claude Code from atezer/FMCP. It costs 118 tokens per session (15,752 once invoked), scanned A, original, MIT.

A tool for creating a complete Figma screen from code or a written description. It uses the project's published design-system components and shared values, such as colours, spacing, and text styles.

In plain words
What is it for?
Use it to turn a coded page or interface brief into a Figma screen, such as a landing page or application view. It is intended for generating the screen itself, not for connecting screens into a clickable prototype.
Why use it?
It avoids rebuilding screens with arbitrary values that do not match the existing design system. This makes the generated Figma screen more consistent with the product's established components and styles.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; names the AskUserQuestion tool.

Part of the figma-mcp-bridge plugin — 29 skills, 10 commands, 3 agents, 1 MCP server shipped together

not rated 10repo changed 5d ago A scan 118 tokens original MIT

Good fit Use it to turn a coded page or interface brief into a Figma screen, such as a landing page or application view. It is intended for generating the screen itself, not for connecting screens into a clickable prototype.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/atezer/fmcp/generate-figma-screen
View source ↗ atezer/FMCP npmjs.com
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add atezer/FMCP --skill generate-figma-screen
Clone the repo
git clone --depth 1 https://github.com/atezer/FMCP

Made for: Claude Code.

Or install figma-mcp-bridge, the plugin that ships this one along with the rest of its 29 skills, 10 commands, 3 agents, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for generate-figma-screen

README.md
[![agentmods](https://agentmods.dev/badge/skills/atezer/fmcp/generate-figma-screen/github.svg)](https://agentmods.dev/skills/atezer/fmcp/generate-figma-screen)
Your own site
<a href="https://agentmods.dev/skills/atezer/fmcp/generate-figma-screen"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/generate-figma-screen/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for generate-figma-screen

Your own site · 80×15
<a href="https://agentmods.dev/skills/atezer/fmcp/generate-figma-screen"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/generate-figma-screen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 118 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 15,752 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00118 $0.15752
Opus 5.5 $0.00047 $0.06301
Sonnet 5.5 $0.00024 $0.03150
Haiku 4.5 $0.00012 $0.01575

Measured 5d ago against content hash ba8c7b693043, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

generate-figma-screen scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/generate-figma-screen/SKILL.md · 1,151 lines

How it starts

The opening of the file, as written. The whole thing — 1,151 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate Figma Screen — Kod/Açıklamadan Figma Ekranı

Kullanım (v3.1+): fmcp-screen-orchestrator altında, Fast Path match FALSE olduğunda ana üretim motoru. Doğrudan entry point DEĞİL. Kullanıcı "ekran üret" dediğinde önce orchestrator yüklenir; orchestrator Fast Path match yapamadıysa buraya düşer.

Design Token Kuralı: Bu skill'deki kod örneklerinde geçen font adları, renk kodları, piksel boyutları yalnızca FORMAT gösterimidir. Çalışma anında tüm design token değerleri (font, renk, boyut, spacing, radius, gölge) kayıtlı kütüphaneden (figma_get_variables, figma_get_styles) veya kullanıcıdan okunmalıdır. Hardcoded token değeri kullanma. Detay: project-context.md → "Design Token Kuralı".

Overview

Bu skill, bir kod tabanından veya metin açıklamasından Figma'da tam sayfa/ekran oluşturur. Temel ilke: hardcode hex renk ve piksel değerleri yerine yayınlanmış design system bileşenlerini (component instance), değişkenlerini (variable) ve stillerini (text/effect style) kullanmak.

Topluluk figma-generate-design skill'inden uyarlanmış, F-MCP Bridge araçlarına göre yeniden yazılmıştır.

Zorunlu: Her figma_execute çağrısından önce figma-canvas-ops kılavuzundaki kuralları uygula.

Skill Boundaries

  • Bu skill: Figma'da ekran oluşturma/güncelleme (DS bileşen instance'ları ile)
  • Figma'dan kod üretmek istiyorsan → implement-design
  • Yeniden kullanılabilir bileşen/variant oluşturmak istiyorsan → generate-figma-library
  • Code Connect eşlemesi istiyorsan → code-design-mapper

Prerequisites

  • F-MCP Bridge plugin bağlı olmalı
  • Hedef Figma dosyasında yayınlanmış DS bileşenleri (veya team library erişimi) olmalı
  • Kaynak: kod dosyaları veya ekran açıklaması

F-MCP skill koordinasyonu

  • Önce (isteğe bağlı): audit-figma-design-system ile mevcut ekranın DS uyumunu kontrol et
  • Birlikte: figma-canvas-ops (her figma_execute öncesi zorunlu)
  • Sonra: figma-a11y-audit ile erişilebilirlik kontrolü; design-drift-detector ile kod parity'si

Read the full file on GitHub · 1,151 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago Changed ba8c7b693043
  2. 1mo ago First seen · 1,151 lines · 118 tokens per session scan A 39bc366bb7af

Subscribe to this mod's changes

generate-figma-screen is a skill published in the GitHub repository atezer/FMCP (10 stars, last pushed 5d ago), licensed MIT. It adds 118 tokens to every session and 15,752 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Design and UXaiclaudecursordesign-systemdesign-tokensfigma
Related

Other skills, from other repositories

theme-audit

Audit theme parity: tokens missing or unchanged per theme, component tokens bypassing semantics, contrast within each theme, resolver contexts, theme-switch regressions. Triggers: dark mode audit, theme coverage, brand variant parity. For general token structure use token-audit.

murphytrueman/design-system-ops · 57 tokens

token-audit

Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).

murphytrueman/design-system-ops · 72 tokens

accessibility-per-component

Audit one design system component's accessibility against WCAG 2.2 AA: keyboard, screen reader, contrast, focus, ARIA, target size. Trigger: a11y audit, is this accessible, WCAG check, screen reader support, keyboard navigation check. Not for page- or product-wide audits.

murphytrueman/design-system-ops · 68 tokens

ai-component-description

Write a six-section prose description (purpose, props, anti-patterns, composition, accessibility, examples) for a Figma component's description field so LLMs read it via MCP. Triggers: describe this component for AI, Figma MCP description. JSON metadata files: use metadata-schema-generator.

murphytrueman/design-system-ops · 65 tokens

codebase-index

Generate machine-readable index files in .ai/index/ (component inventory, uses/usedBy graph, stats) for AI agents. Triggers: index my codebase, build a relationship graph, what depends on what. Not an assessment; for library health use component-audit.

murphytrueman/design-system-ops · 60 tokens

component-decision-tree

Write "choosing between" pages (docs/choosing/) that route an intent to the right component via narrowing questions; YAML trees on request. Triggers: which component should I use, choose between X and Y, dialog vs drawer, selection guide. One chosen component: usage-guidelines.

murphytrueman/design-system-ops · 65 tokens