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)
bash
npx vibefigma --interactive
Prompts for Figma URL, access token, and output paths.
Direct Command
bash
npx vibefigma "https://www.figma.com/design/FILE_ID?node-id=X-Y" --token FIGMA_TOKEN
With Environment Variable
bash
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:
env
FIGMA_TOKEN=your_token_here
Then run:
bash
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