figma-environment-setup

Configures the local working folder and connects Claude to Figma for design-system workflows.

77|11|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/jrpease/throughline --skill figma-environment-setup-jrpease
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-environment-setup
Source: https://github.com/jrpease/throughline/tree/main/skills/figma-environment-setup
Command: npx skills add https://github.com/jrpease/throughline --skill figma-environment-setup-jrpease

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up a design system requires a working folder, a manifest file to track progress, and a live connection between Claude and Figma — steps that are confusing for users who have never created an API token or used developer tools. This Skill walks through the entire environment setup as the required first step before any other design-system skill can run. ## Core Features & Use Cases - Workspace Intake and Scanning: Locates or creates the project directory, scans for existing signals (monorepo, Storybook, token pipelines), and writes a design-system.json manifest recording the workspace origin and detected layers. - Figma Connection Setup: Guides the user through creating a Figma access token, choosing between the Figma Console MCP or the official plugin, pairing via the desktop bridge plugin, and capturing the file key — with strict secret-handling rules so tokens never pass through chat. - Liveness and Write Verification: Proves the connection works with a read probe and a throwaway write/delete test, then routes brownfield projects to an audit and greenfield projects to token building. - Use Case: A designer says "let's set up my design system" — the Skill finds their project folder, creates the manifest, connects Claude to their Figma file, verifies the connection, and hands off to token building. ## Quick Start Ask Claude to set up your design system environment and connect it to your Figma file.

Frequently Asked Questions about figma-environment-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect Claude to Figma for design system work?

Run this setup skill first: it walks you through creating a Figma personal access token, choosing the Figma Console MCP or official plugin, pairing via the desktop bridge plugin, and verifying the connection with a liveness check.

What is the Figma Console MCP versus the official Figma plugin?

The Figma Console MCP is the recommended option — it creates variables in bulk efficiently and reads variables on any plan including free. The official plugin is a simpler fallback with lighter setup but slower bulk operations and restricted variable reads on non-Enterprise plans.

Does the Figma connection work in the browser version of Figma?

No. The Figma desktop app must be installed, open, and signed in with the target file loaded. The browser version causes connection and token errors, so the skill requires the desktop app every time.

Why does the Figma MCP server fail to start with an npm error?

Errors mentioning npx, EACCES, or ~/.npm usually mean the npm cache has files owned by root from a past sudo install. The user should run sudo chown -R $(whoami) ~/.npm in their own terminal, then retry the liveness check.

Is it safe to share my Figma access token with Claude?

No — and this skill enforces that. The token must never pass through chat; the user places it themselves into the FIGMA_ACCESS_TOKEN environment variable in the plugin's MCP configuration, and Claude never sees or stores the value.

When should I run the design system audit instead of building tokens?

If the workspace scan detects an existing repo or monorepo, the skill routes you to the design-system-audit first to measure existing colors and Figma content. Greenfield projects skip the audit and proceed directly to token building.