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.
npx agentmods add skills/atezer/fmcp/design-system-rulesnpx skills add atezer/FMCP --skill design-system-rulesgit clone --depth 1 https://github.com/atezer/FMCPWrote 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.
[](https://agentmods.dev/skills/atezer/fmcp/design-system-rules)<a href="https://agentmods.dev/skills/atezer/fmcp/design-system-rules"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/design-system-rules.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00096 | $0.04176 |
| Opus 5 | $0.00048 | $0.02088 |
| Sonnet 5 | $0.00019 | $0.00835 |
| Haiku 4.5 | $0.00010 | $0.00418 |
Grade A, and why
design-system-rules 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design System Rules Generator (Multi-Platform)
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, iOS, Android ve Web platformlarına özel design system kuralları oluşturur. Her platformun kendi framework'ü, naming convention'ı ve dosya yapısı olduğu için, kurallar platform-spesifik olarak üretilir.
Figma'daki variable ve style verilerini analiz ederek projenin mevcut yapısına uygun kurallar üretir.
REST API veya Figma access token gerekmez.
Prerequisites
- F-MCP Bridge plugin Figma'da çalışıyor ve bağlı olmalı
- Hangi platformlara hizmet verildiği bilinmeli
- Platform proje dizinleri erişilebilir olmalı
F-MCP skill koordinasyonu
- Önce: Figma isimlendirme ve bağlılık için isteğe bağlı audit-figma-design-system veya design-token-pipeline çıktılarıyla hizala.
- Sonra: Üretilen kuralları design-drift-detector ve implement-design doğrulamalarında referans al; tuval ihlali için apply-figma-design-system / fix-figma-design-system-finding.
Required Workflow
Step 1: Plugin Bağlantısını Doğrula
figma_get_status()
Step 2: Figma Design System Verilerini Çek
figma_get_design_system_summary(currentPageOnly=false)
figma_get_token_browser(verbosity="full")
figma_get_variables(verbosity="full")
figma_get_styles(verbosity="full")
Bu verilerden çıkar:
- Token kategorileri ve isimlendirme yapısı
- Mode'lar (Light/Dark, brand varyantları vb.)
- Variable'ların
resolvedType,valuesByMode,scopesbilgileri - Hangi variable'ların alias olduğu (referans zincirleri)
Not: Plugin-only modda enrichment (health score, unused variables, circular references) otomatik olarak hesaplanmaz. Bu analizleri kendin yapmalısın: aynı isimdeki variable'ları, referans edilmeyen variable'ları ve döngüsel alias'ları raw veriden tespit et.
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.
- 4d ago First seen · 408 lines · 96 tokens per session scan A f7bea2e090f6
design-system-rules is a skill published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 4,176 once invoked, about $0.0005 per session on Opus 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.
Other skills, from other repositories
system-pitch
Write a design system investment pitch with a business case and ROI framing. Trigger when someone says: pitch the design system, make the case for the system, sell this to leadership, justify the investment, business case for design systems, why should we invest in a design system, or anything about building an…
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
ai-component-description
Generate AI-optimised text descriptions for components, formatted for Figma's MCP server and LLM consumption. This produces prose descriptions in a six-section format (purpose, props, anti-patterns, composition, accessibility, examples), NOT JSON schemas or structured data files. Trigger when someone says: write…
context-engine-builder
Generate a context engine — seven structured blueprint files (UX, UI, content, accessibility, ethical, technical, business intelligence) that encode everything an AI agent needs to work with a design system. This produces YAML infrastructure in .ai/context-engine/, NOT a health score or quality assessment. Trigger…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
token-compliance
Check a codebase or implementation for token compliance — finding hardcoded values, wrong-tier token references, and inconsistent token application in consuming code. This checks how tokens are used in code, NOT how the tokens themselves are defined or structured. Trigger when someone says: are we using tokens…