style-audit

style-audit is a skill for Claude Code from alvinindra/figma-mcp-rust. It costs 57 tokens per session (511 once invoked), scanned A, original, MIT.

A Figma design audit that finds colors, fonts, and effects entered directly on objects instead of linked to named styles or variables. It can match raw values to existing styles and recommend linking them.

In plain words
What is it for?
Use it to check design-system adoption, find unlinked styles, and clean up hardcoded values in a Figma design.
Why use it?
It reveals where a design has detached or hardcoded styling that may drift from the design system.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the figma-mcp-rust plugin — 13 skills, 1 MCP server shipped together

Good fit Use it to check design-system adoption, find unlinked styles, and clean up hardcoded values in a Figma design.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alvinindra/figma-mcp-rust/style-audit
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 alvinindra/figma-mcp-rust --skill style-audit
Clone the repo
git clone --depth 1 https://github.com/alvinindra/figma-mcp-rust

Made for: Claude Code.

Or install figma-mcp-rust, the plugin that ships this one along with the rest of its 13 skills, 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 style-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/alvinindra/figma-mcp-rust/style-audit/github.svg)](https://agentmods.dev/skills/alvinindra/figma-mcp-rust/style-audit)
Your own site
<a href="https://agentmods.dev/skills/alvinindra/figma-mcp-rust/style-audit"><img src="https://agentmods.dev/badge/skills/alvinindra/figma-mcp-rust/style-audit/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 style-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/alvinindra/figma-mcp-rust/style-audit"><img src="https://agentmods.dev/badge/skills/alvinindra/figma-mcp-rust/style-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 511 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00057 $0.00511
Opus 5 $0.00028 $0.00255
Sonnet 5 $0.00011 $0.00102
Haiku 4.5 $0.00006 $0.00051

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

Security

Grade A, and why

style-audit 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 10d 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/style-audit/SKILL.md · 43 lines

What it actually says

Style Audit Strategy

Find all nodes that use raw (unlinked) fill colors, text styles, or effect styles instead of the design system's named styles or variables. Report findings and optionally fix them.

Steps

  1. Collect the design system

    • Call get_styles() to list all local paint, text, effect, and grid styles (note their names and IDs).
    • Call get_variable_defs() to list all local COLOR variables (note their names and IDs).
  2. Scan the design

    • Call get_design_context() with detail="compact" to get the full node tree.
    • For each node that has a fills, strokes, or textStyle property:
      • If the node's style field shows a named style (e.g. "fillStyle": "Brand/Primary"), it is already linked; skip it.
      • If the node shows a raw fill color (e.g. "fills": [{"type":"SOLID","color":...}]) without a style name, flag it.
      • If a TEXT node shows raw fontFamily/fontSize without a textStyle name, flag it.
  3. Match raw values to existing styles

    • For each flagged node, check whether the raw hex color matches any existing paint style color.
    • If a match is found, recommend apply_style_to_node() to link the node to that style.
    • If no match is found, note the raw value as a design system gap (a new style may be needed).
  4. Report findings Present a table:

    Node ID Node Name Issue Raw Value Matching Style
  5. Fix (optional, ask user first) For each node with a matching style, call: apply_style_to_node(nodeId, styleId, target) Batch nodes by styleId to minimize round trips.

Rules

  • Never change a node's visual appearance; only link it to a style that already matches.
  • Skip INSTANCE nodes whose overrides intentionally diverge from the main component.
  • Process in chunks of 20 nodes at a time when scanning large trees.
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. 10d ago First seen · 43 lines · 57 tokens per session scan A e98b63f1afe0

Subscribe to this mod's changes

style-audit is a skill published in the GitHub repository alvinindra/figma-mcp-rust (38 stars, last pushed 5d ago), licensed MIT. It adds 57 tokens to every session and 511 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

clean-interface-design

Design clean, calm, uncluttered interfaces that don't read as templated AI output. Use when building or restyling any UI (web, iOS, Android, macOS) and it needs visual hierarchy, restraint, spacing discipline, one clear primary action, and a cohesive look. Covers accent color, whitespace, corner radius, type scale…

HalidSaglam/saglitzdesign-mcp · 95 tokens

landing-page-conversion

Build or improve landing pages and marketing sites that convert, not just look good. Use when writing a hero, structuring a page, choosing a CTA, adding social proof, or diagnosing why a page isn't converting. Covers positioning, copy-first workflow, the above-the-fold contract, page narrative, CTAs, trust, and…

HalidSaglam/saglitzdesign-mcp · 86 tokens

ship-quality-gate

Run the deterministic auditors over a real project before it ships — design drift, security headers, generated-default tells, SEO/GEO signals, delivery signals, Apple and Android project configuration — and read the results correctly, disclosure list included. Use when someone asks "audit this", "is this ready to…

HalidSaglam/saglitzdesign-mcp · 86 tokens

apple-platform-design

Design iOS, iPadOS, and macOS apps that feel native, in the Liquid Glass era. Use when building or reviewing Apple-platform UI — navigation, controls, sheets, materials, typography, haptics — or deciding what must change when porting from web/Android. Covers Apple's HIG, the Liquid Glass design language (iOS 26 /…

HalidSaglam/saglitzdesign-mcp · 95 tokens

design-system-audit

Find out whether a codebase actually has a design system or is re-deciding the basics on every screen — count the distinct colors, sizes, radii, shadows and spacings, collapse the near-duplicates, and migrate onto tokens. Use when inheriting a codebase, before a redesign, when a UI "feels inconsistent but I can't say…

HalidSaglam/saglitzdesign-mcp · 93 tokens

motion-and-animation

Add motion and animation that feels great, not like slop. Use when animating any UI — transitions, hovers, presses, sheets, drawers, modals, page transitions, gestures — or when an animation feels "off". Covers the easing rules agents get wrong (ease-out for enter, ease-in for exit), springs, interruptibility…

HalidSaglam/saglitzdesign-mcp · 104 tokens