pix
by skobakv1.0.0
Build frontend on autopilot. Pixel-perfect Figma-to-code with autonomous refinement.
Keywords
figmafrontenduidesign-to-codepixel-perfectmcpchrometailwindreactautonomous
Documentation
# Pix Build frontend on autopilot. Pixel-perfect Figma-to-code with autonomous refinement. ## Install ```bash claude plugin install github:skobak/pix ``` Or manually: ```bash git clone https://github.com/skobak/pix.git ~/.claude/plugins/pix ``` ## Usage Start Claude Code with Chrome integration: ```bash claude --dangerously-skip-permissions --chrome ``` Then run: ``` /pix ``` ## How it works 1. **Run `/pix`** — checks your Figma MCP and Chrome extension setup, guides you if anything is missing 2. **Auto-launch** — starts your dev server, opens localhost in Chrome, asks you to paste the Figma link (Figma MCP handles screenshots directly) 3. **Sit back** — watch it extract tokens, implement the component, screenshot both views, compare pixel-by-pixel, and auto-fix until perfect ## What it handles - Detects your stack (Vite, Next, etc.) - Finds your design system (Tailwind, styled-components, Chakra, etc.) - Identifies your icon library - Syncs Figma tokens to your config - Uses Code Connect to reuse existing components - Recursive refinement until pixel-perfect ## Figma MCP Tools Used | Tool | Purpose | |------|---------| | `whoami` | Verify authentication | | `get_metadata` | Component structure | | `get_design_context` | Full design spec | | `get_variable_defs` | Design tokens | | `get_code_connect_map` | Existing component mappings | | `get_screenshot` | Figma reference image | ## Requirements - **Claude Code** v2.0.73+ with `--chrome` flag - **Claude in Chrome** extension v1.0.36+ ([install](https://claude.com/chrome)) - **Figma MCP** configured ([setup guide](https://help.figma.com/hc/en-us/articles/32132100833559)) - **Paid Claude plan** (Pro, Team, or Enterprise) ## License MIT