figma-environment-setup

figma-environment-setup is a skill for Claude Code from jrpease/throughline. It costs 0 tokens per session (5,333 once invoked), scanned B, original, MIT.

A setup workflow for connecting a local project to Figma, a collaborative design tool. It finds or creates the project folder, writes its design-system.json settings file, and checks the connection.

In plain words
What is it for?
Use it to set up the working folder, create the design-system.json manifest, connect an agent to Figma, and verify that the connection works.
Why use it?
It prepares the required foundation for other Figma-related coding workflows and explains unfamiliar setup concepts along the way.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the throughline plugin — 12 skills, 5 commands, 4 agents, 1 MCP server shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/jrpease/throughline/figma-environment-setup
Any agent
npx skills add jrpease/throughline --skill figma-environment-setup
Clone the repo
git clone --depth 1 https://github.com/jrpease/throughline

Made for: Claude Code.

Or install throughline, the plugin that ships this one along with the rest of its 12 skills, 5 commands, 4 agents, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for figma-environment-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/jrpease/throughline/figma-environment-setup.svg)](https://agentmods.dev/skills/jrpease/throughline/figma-environment-setup)
Your own site
<a href="https://agentmods.dev/skills/jrpease/throughline/figma-environment-setup"><img src="https://agentmods.dev/badge/skills/jrpease/throughline/figma-environment-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,333 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.05333
Opus 5 $0.00000 $0.02667
Sonnet 5 $0.00000 $0.01067
Haiku 4.5 $0.00000 $0.00533

Measured 6d ago against content hash 7d070c7cddec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade B, and why

figma-environment-setup scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo chown -R $(whoami) ~/.npm
adapters/generic/skills/figma-environment-setup/SKILL.md · 457 lines

How it starts

The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Figma environment setup

This skill does three foundational jobs, in order:

  1. Discover where you're working — find or create the project directory, scan what's already there, and set expectations.
  2. Create the local working folder and write the design-system.json manifest into it (if not already present from step 1).
  3. Connect the agent to Figma so later skills can read and write the file, then verify the connection works.

It is the required first step. Every other Figma skill does a cheap liveness check and, if it fails, points the user back here.

Who you're talking to

Assume the user is design-fluent but may have never set up a developer tool, created an API token, or used a terminal before. Explain every concept the first time it appears, in one plain sentence. Never assume they know what a "token", "MCP server", "config file", or "package manager" is. Be warm and concrete. When you ask them to do something outside the chat (in Figma, on a website), give the exact click path, not a vague instruction.

Read .throughline/references/manifest-schema.md before writing the manifest so you use the correct field names and defaults.

Step 0 — Intake (Locate → Scan → Brief)

This step runs before everything else. Establish where you're working, read what's already there, and set the user's expectations before taking any action. It has three phases in sequence.

Phase 1: Locate

Open by surfacing the user's current working directory and presenting three explicit options — no assumptions made about where they want to work or whether they have started anything already:

"Before we get started, I want to make sure we're working in the right place. You're currently in: [current working directory path]

Where should we set up?

  • Here — this directory is where the design system should live
  • Somewhere else — I have a project at a different path
  • A new folder — create a fresh folder somewhere"

"Here": Proceed to the existing manifest check below.

Read the full file on GitHub · 457 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 457 lines · 0 tokens per session scan B 7d070c7cddec

Subscribe to this mod's changes

figma-environment-setup is a skill published in the GitHub repository jrpease/throughline (76 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,333 tokens. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens