Figma Automation via Rube MCP

Overview

This public intake copy packages

plugins/antigravity-awesome-skills/skills/figma-automation

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Figma Automation via Rube MCP Automate Figma operations through Composio's Figma toolkit via Rube MCP.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Prerequisites, Common Patterns, Known Pitfalls, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• This skill is applicable to execute the workflow or actions described in the overview.
• Use when the request clearly matches the imported source intent: Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.
• Use when copied upstream references, examples, or scripts materially improve the answer.
• Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds
2. Call RUBEMANAGECONNECTIONS with toolkit figma
3. If connection is not ACTIVE, follow the returned auth link to complete Figma auth
4. Confirm connection status shows ACTIVE before running any workflows
5. FIGMADISCOVERFIGMA_RESOURCES - Extract IDs from Figma URLs [Prerequisite]
6. FIGMAGETFILE_JSON - Get file data (simplified by default) [Required]
7. FIGMAGETFILE_NODES - Get specific node data [Optional]

Imported Workflow Notes

Imported: Setup

Get Rube MCP: Add

https://rube.app/mcp

1. Verify Rube MCP is available by confirming

   RUBE_SEARCH_TOOLS

   responds
2. Call

   RUBE_MANAGE_CONNECTIONS

   with toolkit

   figma

3. If connection is not ACTIVE, follow the returned auth link to complete Figma auth
4. Confirm connection status shows ACTIVE before running any workflows

Imported: Core Workflows

1. Get File Data and Components

When to use: User wants to inspect Figma design files or extract component information

Tool sequence:

1. FIGMA_DISCOVER_FIGMA_RESOURCES

   - Extract IDs from Figma URLs [Prerequisite]

2. FIGMA_GET_FILE_JSON

   - Get file data (simplified by default) [Required]

3. FIGMA_GET_FILE_NODES

   - Get specific node data [Optional]

4. FIGMA_GET_FILE_COMPONENTS

   - List published components [Optional]

5. FIGMA_GET_FILE_COMPONENT_SETS

   - List component sets [Optional]

Key parameters:

• file_key

  : File key from URL (e.g., 'abc123XYZ' from figma.com/design/abc123XYZ/...)

• ids

  : Comma-separated node IDs (NOT an array)

• depth

  : Tree traversal depth (2 for pages and top-level children)

• simplify

  : True for AI-friendly format (70%+ size reduction)

Pitfalls:

• Only supports Design files; FigJam boards and Slides return 400 errors

• ids

  must be a comma-separated string, not an array
• Node IDs may be dash-formatted (1-541) in URLs but need colon format (1:541) for API
• Broad ids/depth can trigger oversized payloads (413); narrow scope or reduce depth
• Response data may be in

  data_preview

  instead of

  data

2. Export and Render Images

When to use: User wants to export design assets as images

Tool sequence:

1. FIGMA_GET_FILE_JSON

   - Find node IDs to export [Prerequisite]

2. FIGMA_RENDER_IMAGES_OF_FILE_NODES

   - Render nodes as images [Required]

3. FIGMA_DOWNLOAD_FIGMA_IMAGES

   - Download rendered images [Optional]

4. FIGMA_GET_IMAGE_FILLS

   - Get image fill URLs [Optional]

Key parameters:

• file_key

  : File key

• ids

  : Comma-separated node IDs to render

• format

  : 'png', 'svg', 'jpg', or 'pdf'

• scale

  : Scale factor (0.01-4.0) for PNG/JPG

• images

  : Array of {node_id, file_name, format} for downloads

Pitfalls:

• Images return as node_id-to-URL map; some IDs may be null (failed renders)
• URLs are temporary (valid ~30 days)
• Images capped at 32 megapixels; larger requests auto-scaled down

3. Extract Design Tokens

When to use: User wants to extract design tokens for development

Tool sequence:

1. FIGMA_EXTRACT_DESIGN_TOKENS

   - Extract colors, typography, spacing [Required]

2. FIGMA_DESIGN_TOKENS_TO_TAILWIND

   - Convert to Tailwind config [Optional]

Key parameters:

• file_key

  : File key

• include_local_styles

  : Include local styles (default true)

• include_variables

  : Include Figma variables

• tokens

  : Full tokens object from extraction (for Tailwind conversion)

Pitfalls:

• Tailwind conversion requires the full tokens object including total_tokens and sources
• Do not strip fields from the extraction response before passing to conversion

4. Manage Comments and Versions

When to use: User wants to view or add comments, or inspect version history

Tool sequence:

1. FIGMA_GET_COMMENTS_IN_A_FILE

   - List all file comments [Optional]

2. FIGMA_ADD_A_COMMENT_TO_A_FILE

   - Add a comment [Optional]

3. FIGMA_GET_REACTIONS_FOR_A_COMMENT

   - Get comment reactions [Optional]

4. FIGMA_GET_VERSIONS_OF_A_FILE

   - Get version history [Optional]

Key parameters:

• file_key

  : File key

• as_md

  : Return comments in Markdown format

• message

  : Comment text

• comment_id

  : Comment ID for reactions

Pitfalls:

• Comments can be positioned on specific nodes using client_meta
• Reply comments cannot be nested (only one level of replies)

5. Browse Projects and Teams

When to use: User wants to list team projects or files

Tool sequence:

1. FIGMA_GET_PROJECTS_IN_A_TEAM

   - List team projects [Optional]

2. FIGMA_GET_FILES_IN_A_PROJECT

   - List project files [Optional]

3. FIGMA_GET_TEAM_STYLES

   - List team published styles [Optional]

Key parameters:

• team_id

  : Team ID from URL (figma.com/files/team/TEAM_ID/...)

• project_id

  : Project ID

Pitfalls:

• Team ID cannot be obtained programmatically; extract from Figma URL
• Only published styles/components are returned by team endpoints

Imported: Prerequisites

• Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
• Active Figma connection via

  RUBE_MANAGE_CONNECTIONS

  with toolkit

  figma

• Always call

  RUBE_SEARCH_TOOLS

  first to get current tool schemas

Examples

Example 1: Ask for the upstream workflow directly

Use @figma-automation-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @figma-automation-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @figma-automation-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @figma-automation-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills/skills/figma-automation

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @error-debugging-multi-agent-review-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @error-detective-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @error-diagnostics-error-analysis-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @error-diagnostics-error-trace-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: Quick Reference

Imported: Common Patterns

URL Parsing

Extract IDs from Figma URLs:

1. Call FIGMA_DISCOVER_FIGMA_RESOURCES with figma_url
2. Extract file_key, node_id, team_id from response
3. Convert dash-format node IDs (1-541) to colon format (1:541)

Node Traversal

1. Call FIGMA_GET_FILE_JSON with depth=2 for overview
2. Identify target nodes from the response
3. Call again with specific ids and higher depth for details

Imported: Known Pitfalls

File Type Support:

• GET_FILE_JSON only supports Design files (figma.com/design/ or figma.com/file/)
• FigJam boards (figma.com/board/) and Slides (figma.com/slides/) are NOT supported

Node ID Formats:

• URLs use dash format:

  node-id=1-541

• API uses colon format:

  1:541

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.