
vibefigma-figma-to-react
Convert Figma designs to production-ready React components with Tailwind CSS using VibeFigma
- Installs
- 139
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/reason-machines/design-skills --skill vibefigma-figma-to-react- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads vibefigma-figma-to-react automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
VibeFigma - Figma to React Converter
Skill by ara.so — Design Skills collection.
VibeFigma is an open-source tool that transforms Figma designs into production-ready React components with Tailwind CSS. It uses the official Figma API to extract designs and generate clean, maintainable TypeScript/React code.
Installation
VibeFigma can be used without installation via npx, or installed globally/locally:
# Run directly (recommended)
npx vibefigma
# Install globally
npm install -g vibefigma
# Install as dev dependency
npm install --save-dev vibefigma
Prerequisites
You need a Figma Personal Access Token:
- Go to https://www.figma.com/settings
- Scroll to Personal Access Tokens
- Click Generate new token
- Copy the token and store it securely
Set the token as an environment variable:
export FIGMA_TOKEN=your_figma_access_token
Or create a .env file:
FIGMA_TOKEN=your_figma_access_token
CLI Usage
Interactive Mode (Easiest)
npx vibefigma --interactive
The CLI will prompt you for:
- Figma URL
- Access token (if not in env)
- Output paths
Direct Command
# Basic usage
npx vibefigma "https://www.figma.com/design/FILE_ID/FILE_NAME?node-id=NODE_ID"
# With explicit token
npx vibefigma "https://www.figma.com/design/FILE_ID/FILE_NAME?node-id=NODE_ID" --token YOUR_TOKEN
# Custom output paths
npx vibefigma "https://www.figma.com/design/FILE_ID/FILE_NAME?node-id=NODE_ID" \
--component ./src/components/Hero.tsx \
--assets ./public/images
# Force overwrite without confirmation
npx vibefigma "https://www.figma.com/design/FILE_ID/FILE_NAME?node-id=NODE_ID" --force
Common Options
# Disable Tailwind CSS (generate regular CSS)
npx vibefigma [url] --no-tailwind
# Optimize generated code
npx vibefigma [url] --optimize
# Use AI code cleaner (requires GOOGLE_GENERATIVE_AI_API_KEY)
npx vibefigma [url] --clean
# Disable responsive design
npx vibefigma [url] --no-responsive
# Don't include font imports
npx vibefigma [url] --no-fonts
# Disable absolute positioning
npx vibefigma [url] --no-absolute
Full CLI Options
Options:
-V, --version Output version
-t, --token <token> Figma access token (overrides FIGMA_TOKEN)
-u, --url <url> Figma file/node URL
-c, --component <path> Component output path (default: ./src/components/[ComponentName].tsx)
-a, --assets <dir> Assets directory (default: ./public)
--no-tailwind Disable Tailwind CSS
--optimize Optimize components
--clean Use AI code cleaner
--no-classes Don't generate CSS classes
--no-absolute Don't use absolute positioning
--no-responsive Disable responsive design
--no-fonts Don't include fonts
--interactive Force interactive mode
-f, --force Overwrite existing files without confirmation
-h, --help Display help
Real-World Examples
Example 1: Convert Login Form
# Figma URL for a login form component
npx vibefigma \
"https://www.figma.com/design/4i8Tp5btFPRqtkYXplnfT6/50-Web-Sign-up-log-in-designs--Community-?node-id=26-2944" \
--component ./src/components/LoginForm.tsx \
--assets ./public/login-assets \
--force
Generated output (example):
// src/components/LoginForm.tsx
import React from 'react';
export const LoginForm: React.FC = () => {
return (
<div className="flex flex-col items-center justify-center min-h-screen bg-gray-50">
<div className="w-full max-w-md p-8 space-y-6 bg-white rounded-lg shadow-md">
<h2 className="text-2xl font-bold text-center text-gray-900">
Sign In
</h2>
<form className="space-y-4">
<div>
<label htmlFor="email" className="block text-sm font-medium text-gray-700">
Email
</label>
<input
id="email"
type="email"
className="w-full px-3 py-2 mt-1 border border-gray-300 rounded-md focus:outline-none focus:ring-2 focus:ring-blue-500"
placeholder="you@example.com"
/>
</div>
<div>
<label htmlFor="password" className="block text-sm font-medium text-gray-700">
Password
</label>
<input
id="password"
type="password"
className="w-full px-3 py-2 mt-1 border border-gray-300 rounded-md focus:outline-none focus:ring-2 focus:ring-blue-500"
/>
</div>
<button
type="submit"
className="w-full px-4 py-2 text-white bg-blue-600 rounded-md hover:bg-blue-700 focus:outline-none focus:ring-2 focus:ring-blue-500"
>
Sign In
</button>
</form>
</div>
</div>
);
};
Example 2: Generate Multiple Components
# Create a components directory structure
mkdir -p src/components/hero
mkdir -p public/hero-assets
# Convert hero section
npx vibefigma \
"https://www.figma.com/design/YOUR_FILE_ID?node-id=HERO_NODE_ID" \
--component ./src/components/hero/Hero.tsx \
--assets ./public/hero-assets \
--optimize
Example 3: Without Tailwind (Regular CSS)
npx vibefigma \
"https://www.figma.com/design/YOUR_FILE_ID?node-id=NODE_ID" \
--no-tailwind \
--component ./src/components/CustomCard.tsx
This generates a component with inline styles or CSS modules instead of Tailwind classes.
API Server Usage
VibeFigma includes a REST API for programmatic conversions.
Starting the Server
# Install dependencies
bun install
# Development mode
bun run dev
# Production mode
bun run start
Configuration
Create .env file:
GOOGLE_GENERATIVE_AI_API_KEY=your_google_ai_key_here
PORT=3000
HOST=0.0.0.0
CORS_ORIGIN=*
FIGMA_TOKEN=your_figma_token_here
API Endpoint
// POST /v1/api/vibe-figma
interface ConversionRequest {
figmaUrl: string;
token?: string; // Optional if FIGMA_TOKEN env var is set
options?: {
useTailwind?: boolean;
optimize?: boolean;
clean?: boolean;
responsive?: boolean;
includeFonts?: boolean;
};
}
interface ConversionResponse {
component: string; // Generated React component code
assets: Array<{
name: string;
url: string;
data?: string; // Base64 for embedded assets
}>;
}
Example API Call
const response = await fetch('http://localhost:3000/v1/api/vibe-figma', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
},
body: JSON.stringify({
figmaUrl: 'https://www.figma.com/design/FILE_ID?node-id=NODE_ID',
token: process.env.FIGMA_TOKEN,
options: {
useTailwind: true,
optimize: true,
responsive: true,
},
}),
});
const { component, assets } = await response.json();
// Write component to file
await fs.writeFile('./src/components/Generated.tsx', component);
// Download assets
for (const asset of assets) {
const assetData = await fetch(asset.url);
await fs.writeFile(`./public/${asset.name}`, await assetData.arrayBuffer());
}
Common Patterns
Pattern 1: Batch Conversion Script
import { execSync } from 'child_process';
import path from 'path';
interface FigmaComponent {
name: string;
url: string;
outputPath: string;
}
const components: FigmaComponent[] = [
{
name: 'Header',
url: 'https://www.figma.com/design/FILE_ID?node-id=HEADER_NODE',
outputPath: './src/components/Header.tsx',
},
{
name: 'Footer',
url: 'https://www.figma.com/design/FILE_ID?node-id=FOOTER_NODE',
outputPath: './src/components/Footer.tsx',
},
];
for (const comp of components) {
console.log(`Converting ${comp.name}...`);
execSync(
`npx vibefigma "${comp.url}" --component ${comp.outputPath} --force`,
{ stdio: 'inherit' }
);
}
Pattern 2: CI/CD Integration
# .github/workflows/figma-sync.yml
name: Sync Figma Designs
on:
workflow_dispatch:
schedule:
- cron: '0 0 * * 1' # Weekly on Mondays
jobs:
sync:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Setup Node.js
uses: actions/setup-node@v3
with:
node-version: '18'
- name: Convert Figma to React
env:
FIGMA_TOKEN: ${{ secrets.FIGMA_TOKEN }}
run: |
npx vibefigma "${{ vars.FIGMA_URL }}" \
--component ./src/components/DesignSystem.tsx \
--force
- name: Create Pull Request
uses: peter-evans/create-pull-request@v5
with:
title: 'chore: sync Figma designs'
branch: figma-sync
Pattern 3: Custom Post-Processing
import { execSync } from 'child_process';
import fs from 'fs/promises';
async function convertAndCustomize(figmaUrl: string, outputPath: string) {
// Generate component
execSync(
`npx vibefigma "${figmaUrl}" --component ${outputPath} --force`,
{ stdio: 'inherit' }
);
// Read generated file
let content = await fs.readFile(outputPath, 'utf-8');
// Add custom imports
content = `import { motion } from 'framer-motion';\n${content}`;
// Replace div with motion.div for animations
content = content.replace(
/<div className="/g,
'<motion.div initial={{ opacity: 0 }} animate={{ opacity: 1 }} className="'
);
content = content.replace(/<\/div>/g, '</motion.div>');
// Write back
await fs.writeFile(outputPath, content);
console.log(`✅ Generated and customized: ${outputPath}`);
}
// Usage
await convertAndCustomize(
'https://www.figma.com/design/FILE_ID?node-id=NODE_ID',
'./src/components/AnimatedHero.tsx'
);
Troubleshooting
Issue: "Invalid Figma token"
Solution: Verify your token is correct and not expired:
# Test token manually
curl -H "X-Figma-Token: YOUR_TOKEN" \
https://api.figma.com/v1/me
Issue: "Node not found"
Solution: Ensure your Figma URL includes the correct node-id parameter:
# Correct format
https://www.figma.com/design/FILE_ID/FILE_NAME?node-id=123-456
# You can copy this from Figma:
# Right-click frame → Copy/Paste → Copy link
Issue: Generated code has inline styles instead of Tailwind
Solution: Ensure Tailwind is not disabled:
# Remove --no-tailwind flag
npx vibefigma [url] --component ./output.tsx
# Explicitly enable optimization
npx vibefigma [url] --component ./output.tsx --optimize
Issue: Assets not downloading
Solution: Check asset directory permissions and path:
# Create directory first
mkdir -p ./public/assets
# Specify absolute path
npx vibefigma [url] --assets $(pwd)/public/assets
Issue: Component has positioning issues
Solution: Try disabling absolute positioning:
npx vibefigma [url] --no-absolute --responsive
Issue: Fonts not loading
Solution: Ensure font imports are enabled and Tailwind config includes fonts:
// tailwind.config.js
module.exports = {
theme: {
extend: {
fontFamily: {
sans: ['Inter', 'system-ui', 'sans-serif'],
},
},
},
};
Integration with Development Workflow
Next.js Integration
# Generate component in Next.js app directory
npx vibefigma [url] \
--component ./app/components/FigmaComponent.tsx \
--assets ./public/figma-assets
Vite/React Integration
# Generate for Vite project
npx vibefigma [url] \
--component ./src/components/FigmaComponent.tsx \
--assets ./public/assets
Storybook Integration
// Generate component
// Then create story file
import type { Meta, StoryObj } from '@storybook/react';
import { FigmaComponent } from './FigmaComponent';
const meta: Meta<typeof FigmaComponent> = {
title: 'Design System/FigmaComponent',
component: FigmaComponent,
};
export default meta;
type Story = StoryObj<typeof FigmaComponent>;
export const Default: Story = {};
Best Practices
- Version Control: Always commit generated components to track design changes over time
- Naming Conventions: Use descriptive component names that match Figma frame names
- Asset Management: Organize assets in subdirectories per component
- Review Generated Code: Always review and test generated components before production use
- Incremental Updates: Use
--forceflag carefully; review diffs when regenerating existing components - Environment Variables: Never commit tokens; always use environment variables
- AI Optimization: Use
--cleanflag only when GOOGLE_GENERATIVE_AI_API_KEY is available for better code quality
Resources
- GitHub: https://github.com/vibeflowing-inc/vibe_figma
- NPM: https://www.npmjs.com/package/vibefigma
- Homepage: https://vibeflow.ai/
- Discord: https://discord.com/invite/Ctm2A2uEaq
- License: AGPL-3.0
FAQ
What does the vibefigma-figma-to-react skill do?
Convert Figma designs to production-ready React components with Tailwind CSS using VibeFigma
How do I install vibefigma-figma-to-react?
Run npx skills add https://github.com/reason-machines/design-skills --skill vibefigma-figma-to-react in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/vibefigma-figma-to-react/ (personal) or .claude/skills/vibefigma-figma-to-react/ (project).
Which AI agents can use vibefigma-figma-to-react?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is vibefigma-figma-to-react safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains vibefigma-figma-to-react?
It is published by reason-machines in reason-machines/design-skills. It has 139 recorded installs.
More from reason-machines/design-skills
awesome-claude-design
reason-machines/design-skills
Open the skill to read its SKILL.md instructions.
open-design-ai-prototyping
reason-machines/design-skills
Open the skill to read its SKILL.md instructions.
design-md-format
reason-machines/design-skills
Open the skill to read its SKILL.md instructions.
open-codesign-ai-design
reason-machines/design-skills
Open the skill to read its SKILL.md instructions.
design-md-chrome-extractor
reason-machines/design-skills
Open the skill to read its SKILL.md instructions.
claude-design-system-hooks
reason-machines/design-skills
Open the skill to read its SKILL.md instructions.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.