Install
$ agentstack add skill-ikusmart-claude-figma-skills-figma-plugin-build ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
Build & Validate Figma Plugin
Self-Documentation
When invoked WITHOUT clear context (no plugin project in current directory):
- Display the Quick Help block below
- Search for the nearest manifest.json to identify the project
When invoked WITH a clear project context — skip help and proceed to Step 1.
Quick Help
What I do: Run the full build pipeline for a Figma plugin — TypeScript checking, esbuild bundling, and manifest validation. Reports errors and warnings.
What gets checked:
- TypeScript types (zero errors required)
- esbuild bundling (dist/code.js + dist/ui.html)
- manifest.json validity (required fields, file references)
Example prompts:
Build the pluginCheck for errors in the pluginValidate the Figma plugin
Prerequisites: A Figma plugin project with manifest.json. Create one with /figma-new.
Expected output:
=== Build Report ===
TypeScript: OK
Build: OK
Output: dist/code.js (12 KB), dist/ui.html (3 KB)
Manifest: OK
====================
Step 1: Locate Project
Find the nearest manifest.json with a "main" field (Figma plugin manifest). If not found in the current directory, check parent directories up to 3 levels.
Step 2: TypeScript Check
pnpm typecheck
If pnpm is not available, use npx tsc --noEmit.
Report any TypeScript errors. If there are errors, stop and report them.
Step 3: Build
pnpm build
If pnpm is not available, use node esbuild.config.js.
Step 4: Validate Build Output
Check that the expected output files exist:
dist/code.js— main plugin bundle (required)dist/ui.html— UI bundle (only if manifest has"ui"field)
Step 5: Validate Manifest
Read manifest.json and verify:
nameis not emptyidis not the placeholder"000000000000000000"(warn if it is)apiis"1.0.0"mainpoints to an existing fileuipoints to an existing file (if present)editorTypeis a non-empty arraydocumentAccessis"dynamic-page"
Step 6: Report
Output a summary:
=== Build Report ===
TypeScript: OK / X errors
Build: OK / FAILED
Output: dist/code.js (X KB), dist/ui.html (X KB)
Manifest: OK / X warnings
====================
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ikusmart
- Source: ikusmart/claude.figma.skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.