Create and update generative Figma plugins

Load this skill before every create_generative_plugin or update_generative_plugin call. In user-facing language, call the result a “plugin.” The “generative” qualifier only distinguishes this account-library tool from other plugin systems.

Preflight

Before authoring, confirm the request fits this surface:

• Plugins run in the Figma Design editor.
• Every plugin must provide functional UI for its core workflow. A plugin with no configurable inputs still needs a clear primary action and useful status or validation feedback.
• Never embed API keys, OAuth tokens, signed URLs, or other secrets. Plugin source is readable by people who can access it. For authenticated integrations, stop and offer a static dataset, a public no-auth endpoint, or a different architecture.

Create workflow

1. Resolve the requested workflow and its useful controls. Ask a concise question only if required inputs or behavior are genuinely ambiguous.
2. Resolve planKey. Reuse one supplied by the user; otherwise call whoami. Use the sole eligible plan automatically, or ask the user to choose when several materially different plans are available.
3. Call create_generative_plugin once with a concise name, description, and planKey. This creates a runnable square-drawing scaffold, not the requested final plugin.
4. Call get_generative_plugin with the returned id, then read every source URI. This establishes the scaffold's manifest, UI message contract, and current TypeScript entrypoint.
5. Replace the scaffold with complete authored files for the requested behavior and UI.
6. Call update_generative_plugin with the returned id, a files array containing complete replacements for code.ts and, when the UI changes, ui.html, plus a specific commitMessage. Use metadata when changing the name or description.

Never stop after create_generative_plugin: the starter must be replaced with the requested experience.