ds-impact-analysis

ds-impact-analysis is a skill for Claude Code, Codex from atezer/FMCP. It costs 115 tokens per session (2,546 once invoked), scanned A, original, MIT.

A read-only change-impact analyser for a design system. It traces which screens, components, and code files may depend on a Figma token or component, then reports the dependency reach and risk.

In plain words
What is it for?
Use it to check what would be affected by changing a colour, font, spacing value, or reusable interface component.
Why use it?
It helps you see the likely consequences of changing a shared design value or component before making the change.

Skill for Claude CodeCodex

Part of the figma-mcp-bridge plugin — 28 skills, 11 commands, 4 agents, 1 MCP server shipped together

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.

agentmods
npx agentmods add skills/atezer/fmcp/ds-impact-analysis
Any agent
npx skills add atezer/FMCP --skill ds-impact-analysis
Clone the repo
git clone --depth 1 https://github.com/atezer/FMCP

Made for: Claude Code, Codex.

Or install figma-mcp-bridge, the plugin that ships this one along with the rest of its 28 skills, 11 commands, 4 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 ds-impact-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/atezer/fmcp/ds-impact-analysis.svg)](https://agentmods.dev/skills/atezer/fmcp/ds-impact-analysis)
Your own site
<a href="https://agentmods.dev/skills/atezer/fmcp/ds-impact-analysis"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/ds-impact-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 115 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,546 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00115 $0.02546
Opus 5 $0.00057 $0.01273
Sonnet 5 $0.00023 $0.00509
Haiku 4.5 $0.00012 $0.00255

Measured 5d ago against content hash 1d20fdce161c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ds-impact-analysis 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/ds-impact-analysis/SKILL.md · 267 lines

How it starts

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

DS Impact Analysis — Tasarım Sistemi Etki Analizi

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 design system token'ı veya bileşeni değiştirildiğinde etkilenecek tüm ekranları, bileşenleri ve dosyaları analiz eder. DesignOps ekiplerinin değişiklik kararlarını bilinçli vermesini sağlar.

Salt okunur — Figma tuvalinde değişiklik yapmaz.

Prerequisites

  • F-MCP Bridge plugin bağlı olmalı
  • Değiştirilmek istenen token/bileşen bilgisi (isim veya ID)

F-MCP skill koordinasyonu

  • Önce (isteğe bağlı): audit-figma-design-system ile mevcut DS durumunu anla
  • Sonra: Etki analizi onaylandıktan sonra:
    • Token değişikliği → design-token-pipeline (reverse flow ile güncelle)
    • Bileşen değişikliği → apply-figma-design-system veya fix-figma-design-system-finding
    • Kod güncellemesi → implement-design + design-drift-detector

Required Workflow

Step 1: Plugin Bağlantısını Doğrula

figma_get_status()

Step 2: Değişiklik Kapsamını Belirle

Kullanıcıdan değişikliği öğren:

Token değişikliği:

  • Hangi token/variable? (ör. color/primary/500, spacing/md)
  • Yeni değer ne? (ör. #2563EB#3B82F6)
  • Hangi mode'lar etkileniyor? (ör. Light, Dark, her ikisi)

Bileşen değişikliği:

  • Hangi bileşen? (ör. Button, Card, NavBar)
  • Ne değişiyor? (ör. variant ekleme/kaldırma, property değişikliği, boyut)

Step 3: Token Bağımlılık Ağacı

Token değişikliği için:

figma_get_variables(verbosity="full")

figma_execute ile bağımlılık taraması:

const targetVarName = "<TOKEN_NAME>";

const collections = await figma.variables.getLocalVariableCollectionsAsync();
const allVariables = [];
for (const col of collections) {
  for (const varId of col.variableIds) {
    const v = await figma.variables.getVariableByIdAsync(varId);
    allVariables.push(v);
  }
}

const targetVar = allVariables.find(v => v.name === targetVarName);
if (!targetVar) return { error: "Variable bulunamadı: " + targetVarName };

// Alias zincirleri: transitif bağımlılık taraması (A → B → C zinciri)
function findDependents(varId, visited = new Set()) {
  if (visited.has(varId)) return []; // döngü koruması
  visited.add(varId);
  const direct = allVariables.filter(v =>
    Object.values(v.valuesByMode).some(val =>
      val && val.type === "VARIABLE_ALIAS" && val.id === varId
    )
  );
  const transitive = [];
  for (const d of direct) {
    transitive.push(...findDependents(d.id, visited));
  }
  return [...direct, ...transitive];
}

const allDependents = findDependents(targetVar.id);
const uniqueDeps = [...new Map(allDependents.map(d => [d.id, d])).values()];

return {
  target: { id: targetVar.id, name: targetVar.name, type: targetVar.resolvedType },
  directDependents: uniqueDeps.map(d => ({
    id: d.id, name: d.name, type: d.resolvedType
  })),
  dependentCount: uniqueDeps.length
};

Read the full file on GitHub · 267 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 First seen · 267 lines · 115 tokens per session scan A 1d20fdce161c

Subscribe to this mod's changes

ds-impact-analysis is a skill published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 2,546 once invoked, about $0.0006 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.

Related

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…

murphytrueman/design-system-ops · 72 tokens

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…

murphytrueman/design-system-ops · 93 tokens

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…

murphytrueman/design-system-ops · 132 tokens

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…

murphytrueman/design-system-ops · 135 tokens

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…

murphytrueman/design-system-ops · 73 tokens

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…

murphytrueman/design-system-ops · 120 tokens