figma-known-pitfalls
Avoid the most common Figma API integration mistakes and anti-patterns. Use when reviewing Figma code, onboarding new developers, or auditing an existing Figma integration. Trigger with phrases like "figma mistakes", "figma anti-patterns", "figma pitfalls", "figma code review", "figma what not to do". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill figma-known-pitfalls --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Figma Known Pitfalls ## Overview The ten most common mistakes when integrating with the Figma REST API and Plugin API, with correct alternatives for each. ## Prerequisites - Working Figma integration to audit - Access to codebase ## Instructions ### Pitfall 1: Fetching Full File Trees **Problem:** `GET /v1/files/:key` without `depth` returns the entire document tree. Large files can be 10-100 MB
What does the figma-known-pitfalls skill do?
Avoid the most common Figma API integration mistakes and anti-patterns. Use when reviewing Figma code, onboarding new developers, or auditing an existing Figma integration. Trigger with phrases like "figma mistakes", "figma anti-patterns", "figma pitfalls", "figma code review", "figma what not to do". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill figma-known-pitfalls --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
