Skill

figma

Every Figma endpoint, plus codegen-ready frame extracts, comments audit, orphans finder, tokens diff, and webhook...

Verified: 2026-05-13 (printing-press-ingest-2026-05-13+enrich-capability-skill)

When to use figma

Choose if

You're driving Figma from an agent loop and need the editorial superset (codegen-ready frame extracts, orphans finder, tokens diff, comments audit, webhook replay) plus full REST coverage. Alternative is the raw Figma API, which gives you no compaction, no diffing, and 10MB JSON dumps that blow up agent context.

Avoid if

Your Figma plan tier can't absorb the strict tier-1 rate limits and multi-day 403 lockouts that the README warns about. Also avoid if you need activity-log access without Enterprise+OAuth, or for use cases where image URL expiry (14-30 days) would break downstream workflows.

Risk Flags

  • HIGH rate_limit Tier-1 endpoints (files/images/nodes) enforce strict per-plan-tier limits; the README notes 403 lockouts can last multi-day on /v1/files calls. Agents must monitor X-Figma-Plan-Tier headers and back off aggressively.
  • MEDIUM auth PAT vs OAuth routing is split — some endpoints are OAuth-only and will reject a personal access token. Activity logs require Enterprise tier + OAuth. Misconfigured auth surfaces as endpoint- specific failures.
  • MEDIUM data_quality Image URLs expire (14 days for fill URLs, 30 days for rendered nodes). Failed renders silently return null in the image map. Large file JSON responses (10MB baseline) require compaction or the agent's context window overflows.
  • LOW scope Maximum 10 dev resources per node. Frame-extract output can exceed agent context unless `--depth` is reduced.

Cost

Type: Unknown

Install

Default

npx -y @mvanhorn/printing-press install figma

Setup docs →

Estimated time to first success: ~10 min

Dependencies

Minimum runtime: Node.js (npx) or pre-built Go binary

Distribution

Repository
https://github.com/mvanhorn/printing-press-library
License
MIT