agentleFS
renfei-designrenfei-design/Figma-AI-Bridge/.github/skills/figma-slides/SKILL.md

figma-slides

Skill16 starsChanged 9 months agoMITView on GitHub

Create presentation slides in Figma. Use when asked to create slides, a deck, a presentation, or a pitch in Figma. Builds 1920×1080 slide frames with title, body, key points, and visual references using standard slide layout patterns.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. southleft/figma-console-mcp-skills★ 83same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    MANDATORY: Every deck must be organized into logical sections.

    line 13
  2. Very specific:

    Discover the template autonomously: Use get_selection, or scan with get_document_info and get_node_info to find an INSTANCE named "Slide …

    line 38
  3. Very specific:

    Use get_canvas_bounds to avoid overlap

    line 228

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Figma Slides

Build presentation slides in Figma. One command per slide via create_slide, or batch multiple slides. Combine with online-research skill for data-driven decks.

MANDATORY: Every deck must be organized into logical sections. Each section = one row on the canvas, starting with a cover slide cloned from an existing template. The agent must autonomously decide how to divide content into sections — do NOT ask the user for section structure.

Prerequisites

  • figma-ai-bridge plugin running in Figma and connected
  • The create_slide command registered in code.js
  • Helper: scripts/figma_cmd.mjs <channel> create_slide '<paramsJSON>'

Slide Types

Type 1: title — Section Cover / Title Slide

Clone an existing slide template via templateNodeId to get the decorative background, then update text.

{
  "type": "title",
  "templateNodeId": "<node-id>",
  "header": "Project Name",
  "title": "Presentation Title",
  "x": 0, "y": 0
}
  • Always use templateNodeId — cover slides must clone a template for visual style
  • Discover the template autonomously: Use get_selection, or scan with get_document_info and get_node_info to find an INSTANCE named "Slide templates". Only ask the user if no template exists.

Type 2: content — Title + Body + Key Points (Two-Column)

Left column has body text, right column has bold heading + description pairs.

{
  "type": "content",
  "title": "Key Findings",
  "body": "Our research across three verticals revealed...",
  "points": [
    {"heading": "Finding One", "description": "Details about the first finding..."},
    {"heading": "Finding Two", "description": "Details about the second finding..."}
  ],
  "x": 0, "y": 0
}

Type 3: visual — Title + Body + Cloned Visual

Left side has title and body. Right side clones an existing Figma node (UI mockup, screenshot, diagram).

{
  "type": "visual",
  "title": "Feature Preview",
  "body": "This shows the new user onboarding flow...",
  "imageNodeId": "<node-id>",
  "x": 0, "y": 0
}

Type 4: statement — Big Quote / Key Message

Single impactful statement, large text.

{
  "type": "statement",
  "title": "Key Insight",
  "statement": "Users complete tasks 3x faster with the new workflow.",
  "x": 0, "y": 0
}

Type 5: columns — Side-by-Side Equal Columns

Two parallel text blocks for contrasting or complementary concepts.

{
  "type": "columns",
  "title": "Trade-offs",
  "columns": [
    {"text": "Approach A:\n• Fast to implement\n• Lower cost\n• Less flexible"},
    {"text": "Approach B:\n• Slower rollout\n• Higher investment\n• More extensible"}
  ],
  "x": 0, "y": 0
}

Type 6: comparison — Table / Comparison Grid

{
  "type": "comparison",
  "title": "Feature Comparison",
  "headers": ["Dimension", "Option A", "Option B"],
  "rows": [
    ["Performance", "Fast", "Moderate"],
    ["Cost", "$$$", "$$"],
    ["Scalability", "✅ High", "⚠️ Medium"]
  ],
  "x": 0, "y": 0
}

Type 7: numbered — Numbered Decision / Action List

{
  "type": "numbered",
  "title": "Decisions Needed",
  "items": [
    {"text": "Approve the new architecture", "detail": "Sets technical direction for Q3"},
    {"text": "Hire two more engineers", "detail": "Needed to meet the timeline"}
  ],
  "x": 0, "y": 0
}

Workflow

1. Plan the Deck

Each slide = one idea:

  • Title for opener and section breaks
  • Content for arguments with supporting points
  • Visual for UI mockups, screenshots, diagrams
  • Statement for key takeaways and quotes
  • Columns for side-by-side contrasts
  • Comparison for structured data / feature matrices
  • Numbered for ordered decisions or action items

2. Plan Sections (MANDATORY — autonomous)

Group slides into 3–5 sections by theme. Each section = one row on the canvas, starting with a cloned cover slide.

Example structure:

Row 1 — Opening:     [Cover] [Content] [Content] [Statement]
Row 2 — Analysis:    [Cover] [Comparison] [Content] [Content]
Row 3 — Strategy:    [Cover] [Content] [Statement] [Comparison]
Row 4 — Next Steps:  [Cover] [Columns] [Numbered] [Statement]

Grid formula:

  • x = (slideIndex % 5) × 2020
  • y = rowIndex × 1338

3. Build Slides

For multiple slides, use batch mode which auto-avoids overlapping existing content:

FIGMA_TIMEOUT_MS=300000 node scripts/figma_cmd.mjs <ch> batch_slides /tmp/slides.json

For a single slide:

FIGMA_TIMEOUT_MS=60000 node scripts/figma_cmd.mjs <ch> create_slide '<JSON>'

Typography

ElementFontWeightSizeColor
Header (deck title)InterSemibold 60024#1f1f1f
Slide titleInterBold 70068#242424
Body textInterRegular 40028#525252
Key point headingInterSemibold 60028#242424
Key point descriptionInterRegular 40028#525252
Statement textInterBold 70048#242424
Table headerInterSemibold 60020#242424
Table bodyInterRegular 40020#525252
Numbered itemInterBold 70040#242424

Layout

ElementValue
Slide size1920 × 1080
Corner radius48 (content), 32 (title)
Fill#ffffff
Content margin75px
Column gap150
Line height (body 28px)42px
Line height (title 68px)92px

Content Guidelines

  • One idea per slide
  • Short, declarative titles — state the conclusion, not the topic
  • 3–5 sentences max per column
  • 2–4 key points per content slide
  • Visual slides clone existing Figma nodes via imageNodeId

Deck Structure Patterns

Leadership Presentation (12–16 slides, 4 sections)

  • Section 1: Opening — problem + framing
  • Section 2: Analysis — options + evidence
  • Section 3: Strategy — opportunity + recommendation
  • Section 4: Ask — decisions + closing

Feature Overview (8–10 slides, 3 sections)

  • Section 1: Overview — what and why
  • Section 2: Deep Dives — feature mockups
  • Section 3: Summary — matrix + next steps

Research Findings (10–12 slides, 3 sections)

  • Section 1: Context — summary + key distinction
  • Section 2: Findings — data + analysis
  • Section 3: Recommendations — actions + takeaway

Notes

  • Cover slides MUST use templateNodeId — discover template autonomously
  • Section planning is autonomous — never ask the user how to group slides
  • Use get_canvas_bounds to avoid overlap
  • Cloned visuals retain their original styling

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.