agentleFS
SFKislevSFKislev/Flue/skills/figma/SKILL.md

Figma

Skill102 starsChanged 6 months agoMITView on GitHub

Control Figma from the shell via Flue - a plugin bridge to the Figma Plugin API without an MCP server.

  • Installs packages

52 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use analytics-metrics, aws-account-management and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • hoodiniSkill

    analytics-metrics

    Build data visualization and analytics dashboards. Use when creating charts, KPI displays, metrics dashboards, or data visualization components. Triggers on analytics, dashboard, charts, metrics, KPI, data visualization, Recharts.

    Also in 3 projects that use this

  • hoodiniSkill

    aws-account-management

    Manage AWS accounts, organizations, IAM, and billing. Use when setting up AWS Organizations, managing IAM policies, controlling costs, or implementing multi-account strategies. Triggers on AWS Organizations, AWS IAM, AWS billing, Cost Explorer, SCPs, multi-account, AWS SSO, Identity Center.

    Also in 3 projects that use this

  • LangChainSkill

    slideshow

    Author a HyperFrames slideshow — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching, hotspot navigation, and built-in presenter mode with speaker notes; also converts an existing page into a deck. Output is a navigable deck, not a rendered MP4. If the user didn't explicitly ask for a slideshow, confirm before authoring. Unclear → /hyperframes.

    Also in 8 projects that use this

  • jaron-goh-centrSkill

    talking-head-recut

    Package an existing talking-head / interview / podcast video with timed, designed GRAPHIC OVERLAY cards — kinetic titles, lower-thirds, data callouts, quotes, side panels, picture-in-picture — synced to the transcript, on a 16:9 / 9:16 / 4:5 canvas of your choice; the clip plays untouched underneath. Trigger on "graphic overlays", "on-screen graphics", "package / dress up my video". Not plain subtitles (/embedded-captions). Unclear → /hyperframes.

    Also in 6 projects that use this

  • LangChainSkill

    faceless-explainer

    Turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video: there is no site or footage to capture, so the visuals are invented per scene (typography, abstract graphics, diagrams, data-viz). Use for topic explainers, concept breakdowns, how-tos, listicles. Not a video built from a website (/product-launch-video — promo or tour). Unclear → /hyperframes.

    Also in 6 projects that use this

  • ElyzeSolutionsSkill

    captions-overlay

    Overlay doctrine for the embedded-captions workflow — the caption MODEL (drop / rail / embed) and the rule that captions are an OVERLAY composited on top of the film, never a reserved bottom band you shift content up to avoid. Load when adding captions/subtitles to a talking-head or launch video, when deciding whether a phrase should be dropped, ride the verbatim rail, or be promoted to a scarce embedded climax, when laying out a composition that will carry captions (do NOT reserve a keep-out band), or when centering a composition on the true frame center under captions. Quotes the rail+embed model from embedded-captions and constraint #13 (captions overlay, keep-out band retired) from the product-launch-video scene agent. Applies ON TOP of embedded-captions.

    Also in 3 projects that use this

  • +4 more from hoodini

The file

Files
SKILL.md

This skill lets a coding agent operate Figma (desktop app) through Flue, a local shell-to-application bridge. The agent runs figma_bridge.py commands (compact build, tree, set, shot, sheet, or raw JS with eval) and gets structured JSON back. A small development plugin, Flue Bridge, runs in the open file and carries the jobs into the Plugin API.

agent shell -> figma_bridge.py -> local daemon <- polled by the Flue Bridge plugin -> Figma Plugin API

When to use

The human requests work performed inside Figma - inspect the open file, build or restyle frames and components, apply effects, import images, review a design visually. A CLI agent cannot act inside Figma without a bridge like Flue.

How to proceed

  1. Read FLUE.md in this directory first. It explains how Flue works, the bridge contract and safety expectations.
  2. If Flue is installed: also read adapters/figma_adapter/APP.md (commands, spec format, connection recovery) and, for visual design work, adapters/figma_adapter/docs/design-recipes.md.
  3. If Flue is not installed: tell the human. The install command is pip install flue && flue setup. Do not install without explicit approval in the current session.
  4. First run: the human imports the plugin once (Figma desktop > Plugins > Development > Import plugin from manifest...) and opens it in the file. Then figma_bridge.py pair approves it; no code to type.

Other apps

Flue also supports Photoshop, Illustrator, Premiere, After Effects, InDesign, Audition, Blender, Houdini, 3ds Max, Unity, and Microsoft Office through the same contract. One install covers all adapters.

Safety

Flue acts inside the human's live design file. Treat the human as the driver; prefer small, inspectable steps; every call is one undo step; do not save, publish or delete unless explicitly asked. Flue is MIT-licensed and reviewable on GitHub / PyPI before use.

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.