figma-load-scale
Load test Figma API integrations and plan for scale. Use when benchmarking API throughput, testing rate limit behavior, or planning capacity for high-volume Figma integrations. Trigger with phrases like "figma load test", "figma scale", "figma benchmark", "figma capacity", "figma throughput". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill figma-load-scale --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 Load & Scale ## Overview Test and plan for the throughput limits of your Figma API integration. Figma's rate limits use a leaky bucket algorithm -- this skill helps you find the bucket size for your plan tier and design your integration to stay within it. ## Prerequisites - k6 load testing tool (`brew install k6` or `apt install k6`) - Figma test PAT (do not load test with production token
What does the figma-load-scale skill do?
Load test Figma API integrations and plan for scale. Use when benchmarking API throughput, testing rate limit behavior, or planning capacity for high-volume Figma integrations. Trigger with phrases like "figma load test", "figma scale", "figma benchmark", "figma capacity", "figma throughput". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill figma-load-scale --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.
