AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Figma Plugin Create

skill-ikusmart-claude-figma-skills-figma-plugin-create · by ikusmart

Create a new Figma plugin project from template with proper structure, types, and build config. Generates manifest.json, package.json, tsconfig.json, esbuild config, and source templates. Use when: creating a new Figma plugin, running /figma-new command, scaffolding plugin project, or when user says create figma plugin or new plugin.

No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-ikusmart-claude-figma-skills-figma-plugin-create

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-ikusmart-claude-figma-skills-figma-plugin-create)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Figma Plugin Create? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Create Figma Plugin Project

Self-Documentation

When invoked WITHOUT clear input:

  1. Display the Quick Help block below
  2. Ask the user for the plugin name and details

When invoked WITH a plugin name or clear intent — skip help and proceed to Step 1.

Quick Help

What I do: Scaffold a complete Figma plugin project with TypeScript, esbuild, and Figma API types. Ready to build and test in minutes.

What gets created:

{plugin-name}/
├── src/
│   ├── main.ts          # Plugin sandbox (Figma API access, no DOM)
│   └── ui.ts            # UI iframe (DOM access, no Figma API)
├── dist/                # Build output (gitignored)
├── manifest.json        # Figma plugin config
├── package.json         # Dependencies and scripts
├── tsconfig.json        # TypeScript config
├── ui.html              # UI shell template
├── esbuild.config.js    # Build configuration
└── .gitignore

Example prompts:

  • Create a new Figma plugin called "Color Palette Generator"
  • New Figma plugin for FigJam
  • Scaffold a Figma Dev Mode plugin

Prerequisites: Node.js 22+, pnpm. Run /figma-setup if not installed.


Step 1: Gather Project Info

Ask the user these questions (one at a time):

  1. Plugin name — human-readable name for the plugin (e.g., "Color Palette Generator")
  2. Plugin ID — (optional) Figma-assigned ID. If not provided, leave as placeholder "000000000000000000"
  3. Editor type — which Figma editors to support:
  • figma (default)
  • figjam
  • dev (Dev Mode)
  • Multiple selections allowed
  1. Include UI? — whether the plugin needs a user interface (iframe)
  • Yes (default) — generates ui.html + ui.ts
  • No — plugin runs without UI

Step 2: Create Project Structure

Use the plugin name in kebab-case as the directory name. Create the project at {current_working_directory}/{plugin-name}/.

Read each template from assets/templates/ and customize with the user's input:

{plugin-name}/
├── src/
│   ├── main.ts          # Plugin sandbox code
│   └── ui.ts            # UI iframe code (if UI enabled)
├── dist/                # Build output (gitignored)
├── manifest.json        # Figma plugin manifest
├── package.json         # Dependencies and scripts
├── tsconfig.json        # TypeScript configuration
├── ui.html              # UI shell template (if UI enabled)
├── esbuild.config.js    # Build configuration
├── .gitignore
└── README.md

Step 3: Customize Templates

manifest.json

  • Replace {{PLUGIN_NAME}} with the plugin name
  • Replace {{PLUGIN_ID}} with the ID (or placeholder)
  • Replace {{EDITOR_TYPE}} with the editor type JSON array (e.g., ["figma"] or ["figma", "figjam"])
  • If no UI: remove the "ui" field

package.json

  • Replace {{PLUGIN_NAME_KEBAB}} with kebab-case name
  • Replace {{PLUGIN_NAME}} with display name

main.ts

  • If UI enabled: include figma.showUI(__html__) and message handler
  • If no UI: include a simple plugin that runs and closes

esbuild.config.js

  • If UI enabled: include both main and ui entry points
  • If no UI: include only main entry point

Step 4: Install Dependencies

cd {plugin-name}
pnpm install

If pnpm is not available, fall back to npm install.

Step 5: Build and Verify

pnpm build

Verify that:

  • dist/code.js exists
  • dist/ui.html exists (if UI enabled)
  • No TypeScript errors
  • No build errors

Step 6: Report Success

Tell the user:

  • Project created at {path}
  • To test: Open Figma → Plugins → Development → Import plugin from manifest → select {path}/manifest.json
  • To develop: pnpm watch for auto-rebuild on save
  • To build: pnpm build for production build
  • Run /figma-build to validate the plugin
  • Run /figma-mastery to learn about the Plugin API architecture

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.