The Flaude plugin

Figma only lets a plugin edit a file. Install this one and it becomes the hands Claude uses on your canvas: rebuilding a screen when needed, and carrying out every change Claude makes once the MCP is connected.

The Flaude MCP chat asking Claude to add a code-verification screen that matches the app design, with the plugin studying the design system

What the plugin does

  1. Plugins

    Development

    FlaudeConnected
    01Install once

    The bridge between Claude and your Figma file

    Figma only lets plugins touch a document, so this is what makes the connection possible: Claude sends an instruction, the plugin carries it out inside Figma. You install it once. It is not listed on the Figma Community, so setup is a quick manifest import, not a search and click.

    • Frame / Landing
    • Nav bar
    • Hero
    • Headline
    • Button / primary
    • Feature grid

    Editable Figma layers

    02The fallback

    Rebuilds a screen when the fast path is not available

    Most screens paste straight onto the canvas with a plain ⌘V, no plugin needed. For the rare screen without stored Figma-native bytes, Copy hands the plugin a small payload instead, and it reconstructs the layer tree in place: frames, text, components, exactly as designed.

  2. Claude designing a new screen inside a Figma file through the Flaude plugin
    03With the MCP

    What every Claude command actually runs through

    Once the MCP is connected, ask Claude to restyle a screen, rename layers, or build something new. The plugin is what turns that request into a real, saved change in your Figma file.