# Figma Use Slides

Helps agents use Figma's use_figma MCP tool in the Slides context.

- Repository: https://github.com/figma/mcp-server-guide (2138 stars)
- Category: Design
- License: see repository
- Last updated: 2026-10-28
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add figma/mcp-server-guide --skill figma-use-slides -g -a claude-code -y`
Codex: `npx skills add figma/mcp-server-guide --skill figma-use-slides -g -a codex -y`
Cursor: `npx skills add figma/mcp-server-guide --skill figma-use-slides -g -a cursor -y`
Gemini CLI: `npx skills add figma/mcp-server-guide --skill figma-use-slides -g -a gemini-cli -y`

## Description

This skill helps agents use Figma's use_figma MCP tool in the Slides context. Can be used alongside figma-use which has foundational context for using the use_figma tool.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# use_figma, Figma Plugin API Skill for Slides

This skill contains Slides-specific context for the `use_figma` MCP tool. The [figma-use](../figma-use/SKILL.md) skill provides foundational context for plugin API execution via MCP as well as the full Figma plugin API for more advanced use-cases that are not described here.

**Always include `figma-use-slides` in the comma-separated `skillNames` parameter when calling `use_figma` for Slides operations. If this skill was loaded via an MCP resource, you MUST prefix the name with `resource:` (e.g. `resource:figma-use-slides`).** This is a logging parameter used to track skill usage, it does not affect execution.

## Choosing How to Build a Slides Deck

If your environment also provides a `generate_deck` tool, choose **one** approach per deck request, do not call both for the same deck.

### When to use which

**`use_figma` + this skill (default):** Handles any Slides task, new decks, edits to existing decks, brand-matched designs, reference-file styling, iterative refinement, speaker notes, and full creative control over layout, color, and typography. Use this for most requests.

**`generate_deck`:** Generates a complete deck in a single call using prebuilt, curated templates. Useful for quick, straightforward decks where the user doesn't need custom design, brand matching, or reference-file styling. It cannot use custom templates, cannot reference other Figma files for design direction, and does not support iterative editing or follow-up modifications through the conversation.

When in doubt, default to `use_figma` + this skill, it covers everything `generate_deck` can do and more.

### Pick one and commit

Once you choose an approach for a deck, complete the entire request with that approach. Do not generate a deck with `generate_deck` and then also create or populate a file with `use_figma`, the user ends up with duplicate, conflicting artifacts and a confusing experience.

## Critical Rules (Slides-specific)

The rest: https://github.com/figma/mcp-server-guide/blob/HEAD/skills-figquery/figma-use-slides/SKILL.md
