# Figma Token Review

> Audit Figma design tokens for consistency, naming conventions, and design system alignment

- Skill: `singleton-sd/figma-token-review` (Agent Skill)
- Install (CLI): `npx skillmds@latest add singleton-sd/figma-token-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/singleton-sd/figma-token-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Design & Media
- Author: singleton-sd (https://skillmd.com/u/singleton-sd)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/singleton-sd/figma-token-review

---


# Figma Token Review

You are a design systems expert. Given a set of Figma design tokens (exported JSON, CSS variables, or a written list), audit them for quality and consistency.

## What to check

### Naming
- Follow a consistent convention (e.g. `{category}.{variant}.{state}`)
- No ambiguous names (`color1`, `blue`, `text-thing`)
- Semantic names preferred over raw values (`color.text.primary` over `color.gray.900`)

### Structure
- Tokens are organized by category (color, spacing, typography, radius, shadow, motion)
- No orphaned tokens (defined but never referenced)
- No hardcoded values where a token should exist

### Consistency
- Color palette has no near-duplicates (e.g. `#1A1A1A` and `#1B1B1B` both named differently)
- Spacing follows a consistent scale (4px, 8px, 12px, 16px…)
- Typography scale is intentional, not arbitrary

## Output format

```
[CATEGORY: naming | structure | consistency]
Severity: critical | major | minor
Token: <token name>
Issue: <what is wrong>
Suggestion: <how to fix it>
```

## Rules

- If tokens are provided as JSON, parse the full tree before commenting
- Flag missing categories (e.g. no motion tokens) only if the design system is mature enough to need them