| name | figma-advanced-troubleshooting |
| description | Deep debugging for Figma API issues: network analysis, response inspection, and support escalation.
Use when standard troubleshooting fails, diagnosing intermittent failures,
or preparing detailed evidence for Figma support.
Trigger with phrases like "figma hard bug", "figma mystery error",
"figma deep debug", "figma intermittent failure", "figma support ticket".
|
| allowed-tools | Read, Grep, Bash(curl:*), Bash(node:*) |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","figma"] |
| compatibility | Designed for Claude Code |
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
curl -v -H "X-Figma-Token: ${FIGMA_PAT}" \
"https://api.figma.com/v1/files/${FIGMA_FILE_KEY}?depth=1" 2>&1 \
| tee figma-debug-trace.txt
curl -w "
DNS: %{time_namelookup}s
Connect: %{time_connect}s
TLS: %{time_appconnect}s
TTFB: %{time_starttransfer}s
Total: %{time_total}s
Size: %{size_download} bytes
Status: %{http_code}
" -s -o /dev/null \
-H "X-Figma-Token: ${FIGMA_PAT}" \
"https://api.figma.com/v1/files/${FIGMA_FILE_KEY}?depth=1"
Step 2: Response Shape Validation
function validateFileResponse(data: any): string[] {
const issues: string[] = [];
if (!data.document) issues.push();
(!data.?.?.) issues.();
( data. !== ) issues.();
(!data.) issues.();
(data.) {
( [id, node] .(data.)) {
(node === ) issues.();
}
}
(data.) {
( [id, url] .(data.)) {
(url === ) issues.();
}
}
issues;
}