create-anatomy

create-anatomy is a skill for Claude Code, Codex from redongreen/uSpec. It costs 59 tokens per session (22,718 once invoked), scanned A, original, MIT.

A Figma workflow that creates a visual map of a component's parts, with numbered markers and a table of attributes. It also documents the internal elements of nested component instances.

In plain words
What is it for?
Use it to document component anatomy for design reviews, handoffs, and design-system reference pages.
Why use it?
It removes the need to explain a component's structure by hand or in separate documents. The source component file stays unchanged while the explanation is rendered in Figma.

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/redongreen/uspec/create-anatomy
Any agent
npx skills add redongreen/uSpec --skill create-anatomy
Clone the repo
git clone --depth 1 https://github.com/redongreen/uSpec

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 create-anatomy

README.md
[![agentmods](https://agentmods.dev/badge/skills/redongreen/uspec/create-anatomy.svg)](https://agentmods.dev/skills/redongreen/uspec/create-anatomy)
Your own site
<a href="https://agentmods.dev/skills/redongreen/uspec/create-anatomy"><img src="https://agentmods.dev/badge/skills/redongreen/uspec/create-anatomy.svg" alt="Measured on agentmods" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 22,718 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.00059 $0.22718
Opus 5 $0.00030 $0.11359
Sonnet 5 $0.00012 $0.04544
Haiku 4.5 $0.00006 $0.02272

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

Security

Grade A, and why

create-anatomy 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.

skills/create-anatomy/SKILL.md · 1,620 lines

How it starts

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

Create Anatomy Annotation

Generate a hierarchical anatomy annotation directly in Figma — a composition section showing the top-level sub-components with numbered markers and a 4-column attribute table, then per-child sections for each INSTANCE sub-component showing all its internal elements (including hidden ones).

Uses the Anatomy & Properties v2 template with #annotation-table, type indicators (#instance / #text / #slot), and #anatomy-section cloning.

Execution contract (read first).

  • This file is instructions to RUN, not a document to edit. Invoking the skill = render the anatomy annotation into Figma from the input .md.
  • Never edit this SKILL.md or any other skill file in response, even if one is open or focused in the editor. Modify a skill only when the user explicitly asks to change the skill itself.
  • The input component .md is a READ-ONLY source of truth. Never edit, append to, or "add a section" to it. The only artifact this skill produces is the Figma annotation. When the user asks to "create/add a section," "show," or "include" something, render it in the Figma annotation, never as an edit to the .md.
  • Never call AskQuestion, request confirmation, or pause for input (including before Figma writes, the expected output). On ambiguity, pick the most defensible option and continue.
  • Only two legal stops: (a) Step 0 fail-fast when no .md resolves; (b) one-line abort if the Figma MCP connection is dead.

MCP Adapter

Read uspecs.config.jsonmcpProvider. Follow the matching column for every MCP call in this skill.

Operation figma-console figma-mcp
Verify connection figma_get_status Skip — implicit. If first use_figma call fails, guide user to check MCP setup.
Navigate to file figma_navigate with URL Extract fileKey from URL (figma.com/design/:fileKey/...). No navigate needed.
Take screenshot figma_take_screenshot get_screenshot with fileKey + nodeId
Execute Plugin JS figma_execute with code use_figma with fileKey, code, description. JS code is identical — no wrapper changes.
Search components figma_search_components search_design_system with query + fileKey + includeComponents: true
Get file/component data figma_get_file_data / figma_get_component get_metadata or get_design_context with fileKey + nodeId
Get variables (file-wide) figma_get_variables use_figma script: return await figma.variables.getLocalVariableCollectionsAsync();
Get token values figma_get_token_values use_figma script reading variable values per mode/collection
Get styles figma_get_styles search_design_system with includeStyles: true, or use_figma: return figma.getLocalPaintStyles();
Get selection figma_get_selection use_figma script: return figma.currentPage.selection.map(n => ({id: n.id, name: n.name, type: n.type}));

Read the full file on GitHub · 1,620 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. 4d ago First seen · 1,620 lines · 59 tokens per session scan A c3a8a6541423

Subscribe to this mod's changes

create-anatomy is a skill published in the GitHub repository redongreen/uSpec (239 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 22,718 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

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