analyzing-design-system

analyzing-design-system is a skill for Claude Code, Codex from iclinic/afyapowers-plugin-dev. It costs 0 tokens per session (7,189 once invoked), scanned A, original, no licence file.

A Figma-to-code review that traces each interface component in a design back to its original component and its declaration in the codebase. It then produces a verdict for each layout node and asks the user to confirm the verdicts.

In plain words
What is it for?
Use it to inspect Figma layouts, identify the source components in code, verify each node against the codebase, and confirm the findings.
Why use it?
It helps detect when a design uses the wrong component or when the link between the design and the real code is unclear.

Skill for Claude CodeCodex

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/iclinic/afyapowers-plugin-dev/analyzing-design-system
Any agent
npx skills add iclinic/afyapowers-plugin-dev --skill analyzing-design-system
Clone the repo
git clone --depth 1 https://github.com/iclinic/afyapowers-plugin-dev

Made for: Claude Code, Codex.

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 analyzing-design-system

README.md
[![agentmods](https://agentmods.dev/badge/skills/iclinic/afyapowers-plugin-dev/analyzing-design-system.svg)](https://agentmods.dev/skills/iclinic/afyapowers-plugin-dev/analyzing-design-system)
Your own site
<a href="https://agentmods.dev/skills/iclinic/afyapowers-plugin-dev/analyzing-design-system"><img src="https://agentmods.dev/badge/skills/iclinic/afyapowers-plugin-dev/analyzing-design-system.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,189 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00000 $0.07189
Opus 5 $0.00000 $0.03594
Sonnet 5 $0.00000 $0.01438
Haiku 4.5 $0.00000 $0.00719

Measured yesterday against content hash f071c1f5cf28, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

analyzing-design-system 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 yesterday.

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.

src/skills/analyzing-design-system/SKILL.md · 312 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday Changed · +64 lines f071c1f5cf28
  2. 5d ago First seen · 248 lines · 0 tokens per session scan A 170ec51caccf

Subscribe to this mod's changes

analyzing-design-system is a skill published in the GitHub repository iclinic/afyapowers-plugin-dev (10 stars, last pushed 2d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 7,189 tokens. 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens