Skip to content
Skills Library
Design & UX · Review & audit

figma-diff

/figma-diff

Diff Figma designs to identify what changed and generate code update checklists. Use when syncing code with updated designs or reviewing what changed between iterations. Requires Figma MCP.

Repository
ai-helpers ↗
Licence
MIT
Last repository change
11.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
16
Scripts
4
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 4 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/compare-tokens.js, scripts/compare-tokens.sh, scripts/extract-figma-file-key.sh, scripts/figma-sync.sh

What it does and when to use it

Diff Figma designs to identify what changed and generate code update checklists. Use when syncing code with updated designs or reviewing what changed between iterations. Requires Figma MCP.

Original author description

Diff Figma designs to identify what changed and generate code update checklists. Use when syncing code with updated designs or reviewing what changed between iterations. Requires Figma MCP.

How it works

  1. What This Skill Does
  2. Output Files
  3. What to Analyze
  4. Status Determination
  5. Report Format
  6. Key Guidelines
  7. Examples
  8. Additional Resources
Original SKILL.md headings · 119 lines, 509 words
SKILL.md preview
---
name: figma-diff
description: Diff Figma designs to identify what changed and generate code update checklists. Use when syncing code with updated designs or reviewing what changed between iterations. Requires Figma MCP.
version: 3.1.0
---

# Figma Design Change Tracker

Track Figma design updates and generate code checklists for PatternFly.

## What This Skill Does

1. Fetches recent changes from Figma version history
2. Analyzes design updates to components
3. Compares design specs with code implementation
4. Generates three types of reports (see below)
5. Creates actionable checklists for developers

## Output Files

**FIGMA_CHANGELOG.md** - Internal design team changelog with all updates
**RELEASE_NOTES.md** - Consumer-facing release notes
**figma-updates-[date].md** - Detailed checklist with token changes

See [report-templates.md](report-templates.md) for full template examples.

## What to Analyze

For each component update, focus on:

- **Colors** - Background, border, text, hover/focus states
- **Typography** - Font size, weight, line height
- **Spacing** - Padding, gaps, margins
- **Layout** - Dimensions, alignment, structure
- **Variants** - States (hover, focus, disabled) and sizes
- **Changes** - Elements added or removed

## Status Determination

Assign each update one of three statuses:

**✅ Design-only** - Figma documenting what's already in code
**⚠️ Code update needed** - Design is ahead of code
**🔍 Needs verification** - Unclear if code matches design

### How to Determine Status

1. Check if there's a related GitHub issue
   - Issue closed/merged → Likely ✅ Design-only
   - Issue open → Likely ⚠️ Code update needed
   - No issue → Check token comparison

2. Compare design tokens with code
   - Values match → ✅ Design-only
   - Values differ → ⚠️ Code update needed
   - Can't compare → 🔍 Needs verification

3. Check recent git commits (last 2 weeks)
   - Recent work on component → Possibly ✅ Design-only
   - No recent work → Possibly ⚠️ Code update needed

> See [references/troubleshooting.md](references/troubleshooting.md) for detailed decision tree and automation commands.

## Report Format

### For Each Component Update

Include:
- **Date** - When the design was updated
- **Designer** - Who made the change
- **Page/Context** - Where in Figma (e.g., "Chatbot: Filters")
- **Status** - ✅ / ⚠️ / 🔍
- **Links** - Figma, PatternFly.org, GitHub issues

### For Code Updates (⚠️ status only)

Create token comparison tables:

| ✓ | Token | Current | New | Where Used |
|---|-------|---------|-----|------------|
| [ ] | `--pf-c-button--BackgroundColor` | `#0066CC` | `#004080` | Button background |

List files that need updating:
- `Button.scss` - Update color tokens
- `Button.md` - Update documentation
- `Button.test.tsx` - Update snapshots

## Key Guidelines

**Be Specific** - Use exact token names and values
**Link Everything** - Figma, PatternFly.org, GitHub
**Prioritize** - High (breaking, a11y), Medium (updates), Low (docs)
**Note Context** - Always include the Figma page/section

## Examples

**Code Update Needed:**
```
### Button - 2026-03-16
**Status**: ⚠️ Code update needed
**By**: Sarah Designer | **Page**: Component Library

Primary button color updated for better accessibility (WCAG AA).

Token: `--pf-c-button--m-primary--BackgroundColor`
Change: `#0066CC` → `#004080`
```

**Design-Only:**
```
### Card - 2026-03-10
**Status**: ✅ Design-only
**Related**: Issue #915 (closed)

Figma updated to match PatternFly 6.0.0. No code changes needed.
```

## Additional Resources

- [Report Templates](report-templates.md) - Full template examples
- [Troubleshooting](references/troubleshooting.md) - Common issues
- [Validation Checklists](references/validation-checklists.md) - Quality checks
- [Token Mappings](examples/token-mappings.json) - Figma ↔ Code mapping
Files in this package (16)
  • README.md 7 KB
  • SKILL.md 4 KB
  • report-templates.md 4 KB
  • examples/.figma-sync-cache.json 4 KB
  • examples/sample-output.md 7 KB
  • examples/token-mappings.json 4 KB
  • references/figma-api-guide.md 5 KB
  • references/template-changelog.md 1 KB
  • references/template-detailed-report.md 1 KB
  • references/template-release-notes.md 1 KB
  • references/troubleshooting.md 9 KB
  • references/validation-checklists.md 7 KB
  • scripts/compare-tokens.js 7 KB
  • scripts/compare-tokens.sh 3 KB
  • scripts/extract-figma-file-key.sh 1 KB
  • scripts/figma-sync.sh 9 KB

Versions

The database has no other skills named figma-diff.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 193cc22f3094 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100using-figma
    Use when implementing UI from Figma designs, comparing implementations against Figma, performing design gap analysis, or planning Figma-based frontend work. Triggers on Figma URLs, node IDs, design-to-code tasks, requests to match a design, or Figma MCP setup and…
  • 100figma-copy-sync
    Use when synchronizing text copy between Figma designs and implemented code. Triggers on requests to update copy from Figma, sync text with designs, check copy matches design, or align UI text with Figma. Requires a working Figma MCP server and browser MCP (chrome-devtools or playwright).
  • 91figma-mcp
    Use when reading a Figma file into code, or when the Figma MCP is missing.
  • 100figma-component-sync
    Check a React component against its Figma design source and identify differences. Use when reviewing component implementations, syncing designs, auditing visual accuracy, or updating components to match new Figma designs.
  • 100figma-component-sync
    Check a React component against its Figma design source and identify differences. Use when reviewing component implementations, syncing designs, auditing visual accuracy, or updating components to match new Figma designs.
  • 90figma-sync
    Keep a Figma copy of a mobile or web app (screens, responsive views, design system, brand deck) updated with its code - set up a sync record and diff, redraw what changed after a release or a merged change, and run a weekly drift check that asks before it changes anything. Works…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.