vibefigma
Convert Figma designs to production-ready React components with Tailwind CSS. Use when user provides a Figma URL, asks to convert Figma designs to React/code, wants to extract components from Figma, or mentions "vibefigma". Requires a Figma access token (via --token flag, FIGMA_TOKEN env var, or .env file).
How do I install this agent skill?
npx skills add https://github.com/vibeflowing-inc/vibe_figma --skill vibefigmaIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill allows users to convert Figma designs into React components using the vibefigma CLI tool. It follows standard development practices for handling access tokens and executing commands via npx, posing no significant security risk when used as intended.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
- Runlayerwarn
1/2 files flagged
What does this agent skill do?
VibeFigma - Figma to React Converter
Convert Figma designs into React components with Tailwind CSS using the vibefigma CLI.
Usage
Interactive Mode (Recommended for first-time users)
npx vibefigma --interactive
Prompts for Figma URL, access token, and output paths.
Direct Command
npx vibefigma "https://www.figma.com/design/FILE_ID?node-id=X-Y" --token FIGMA_TOKEN
With Environment Variable
export FIGMA_TOKEN=your_token
npx vibefigma "https://www.figma.com/design/FILE_ID?node-id=X-Y"
Using .env File
The user can add their Figma access token to a .env file in their project root:
FIGMA_TOKEN=your_token_here
Then run:
npx vibefigma "https://www.figma.com/design/FILE_ID?node-id=X-Y"
Note: If the token is not configured, vibefigma will throw an error. Only then inform the user about the token requirement.
Common Options
| Option | Description |
|---|---|
-t, --token <token> | Figma access token |
-c, --component <path> | Output path (default: ./src/components/[Name].tsx) |
-a, --assets <dir> | Assets directory (default: ./public) |
-f, --force | Overwrite existing files without confirmation |
--no-tailwind | Generate regular CSS instead |
Getting a Figma Access Token
- Go to Figma Account Settings
- Scroll to Personal Access Tokens
- Click Generate new token → name it → copy immediately
- Store it securely in a
.envfile or pass via--tokenflag
Workflow
- Get Figma URL with specific node selected (frame/component to convert)
- Check if output file already exists at the target path (default:
./src/components/[Name].tsxor user-specified path) - If file exists, ask the user for confirmation before overwriting, then use the
--forceflag - Run:
npx vibefigma "<URL>" -c <output-path>(add--forceif overwriting confirmed)- User configures token in .env or via --token flag
- If vibefigma throws a token error, inform the user about the token requirement
- Review generated component
- If code needs cleanup, see
references/responsive-cleanup.mdfor making code responsive and production-ready
Output
VibeFigma generates:
- React component (
.tsx) with Tailwind CSS classes - Assets (images/icons) in the assets directory
Notes
- Always select a specific node/frame in Figma URL for best results
- Generated code may need manual cleanup for production use
- See
references/responsive-cleanup.mdfor responsive design patterns
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/vibeflowing-inc/vibe_figma/vibefigma">View vibefigma on skillZs</a>