figma-use

Enforce mandatory Figma Plugin API execution rules for use_figma tool calls.

Updated May 13, 2026
One-click install
npx skills add https://github.com/DevPelumi/sleeqma --skill figma-use-devpelumi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-use
Source: https://github.com/DevPelumi/sleeqma/tree/main/backend/figma-plugin-bundle/skills/figma-use
Command: npx skills add https://github.com/DevPelumi/sleeqma --skill figma-use-devpelumi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the common, hard-to-debug failures that occur when calling the use_figma tool without loading its mandatory prerequisite context, ensuring reliable and predictable Figma file operations.

Core Features & Use Cases

  • Mandatory Execution Guardrails: Enforces critical best practices including returning all created/mutated node IDs, preloading fonts before text edits, using async page switching, and avoiding unsupported APIs to prevent silent failures.
  • Comprehensive Reference Library: Includes full API references, ready-to-use code patterns, common pitfalls guides, design system documentation for components/variables/styles, and step-by-step error recovery workflows.
  • Use Case: When building a Figma design system button component with color tokens and variants, this Skill ensures correct variable scoping, component property wiring, and incremental validation to avoid broken designs or missing assets.

Quick Start

Invoke the figma-use skill before any use_figma tool call to access Figma Plugin API guidelines, reference materials, and error recovery workflows for your design task.

Frequently Asked Questions about figma-use

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Figma plugin API script fail silently during node creation?

Figma plugin API scripts fail silently when mandatory execution rules are ignored, such as missing font preloading or unsupported API calls. Enforcing atomic script execution and incremental workflow validation prevents these hard-to-debug errors.

How do I build Figma component variants with correct variable token scoping?

Building Figma component variants with variable tokens requires correct variable scoping and component property wiring. Applying incremental validation during design system alignment ensures assets are correctly configured and avoids broken designs.

What is the best way to recover from errors during Figma design system mutations?

Error recovery for Figma design system mutations involves following step-by-step workflows that validate operations incrementally. Returning all created or mutated node IDs allows you to track changes and safely recover from failures.

Do I need to preload fonts before executing text edits in the Figma plugin API?

Yes, you must preload fonts before executing text edits in the Figma plugin API. Mandatory execution guardrails enforce font preloading alongside async page switching to prevent silent failures during file operations.

Can I use async page switching for Figma node creation workflows?

Yes, async page switching is a mandatory execution rule for Figma node creation workflows. Using async switching and returning all mutated node IDs ensures atomic script execution and reliable design system alignment.