Agent skill · data analytics · jeremylongshore
figma-advanced-troubleshooting
Deep debugging for Figma API issues: network analysis, response inspection,
Why this skill is useful
Provides specific debugging techniques and scripts for handling complex Figma API issues that the AI wouldn't generate on its own.
What it needs
Requires curl installed locally. Requires figma account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Figma Advanced Troubleshooting Overview Deep debugging techniques for complex Figma REST API issues that resist standard error handling: intermittent failures, unexpected response shapes, rate limit edge cases, and large file timeouts. Prerequisites Access to application logs curl with verbose mode for network inspection Figma API credentials for testing Instructions Step 1: Verbose Request Inspection Step 2: Response Shape Validation Step 3: Rate Limit Edge Cases Step 4: Large File Debugging Step 5: Support Escalation Template curl -v -H "X-Figma-Token: [REDACTED]" \ "https://api.figma.com/v1/files/FILEKEY?depth=1" HTTP/2 [status] x-figma-rate-limit-type: [value] retry-after: [value] Output Verbose request/response traces captured Response shape issues identified Rate limit behavior measured Large file handled with page-level chunking Support ticket prepared with diagnostic data Error Handling Issue Diagnostic Solution ------- ----------- ---------- Intermittent 500s Track frequency and timing Log every request; report pattern to Figma Slow responses curl timing breakdown Check if DNS/TLS is the bottleneck Null image renders Validate node visibility Check node opacity and visibility in Figma Memory crash Large file JSON Use depth=1 + per-page /nodes calls Examples A sync that "randomly fails" — verbose inspection (Step 1) shows it's not random: The failures cluster at the top of each hour — a cron thundering herd, not flakiness. Fix per Step 3 (jitter + honor Retry-After). A "works for small files, breaks for the design system" report is usually payload size — Step 4: Escalation packet for Figma support: references/support-escalation-template.md. Resources Figma Developer Forum Figma Support Figma Status Page Next Steps For load testing, see figma-load-scale.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/figma-advanced-troubleshooting