Think inside your AI world.
How do I connect Figma to Claude?
Figma over MCP gives Claude the design surface — files, frames, structure — which turns design review from screenshots into reads.
Direct answer: connect Figma's MCP surface in Claude — Settings → Connectors, authorise ('claude mcp add' in Claude Code). Claude then reads design files and their structure: what screens exist, how the flow hangs together, what the components actually are. Design conversations stop needing exported PNGs as their evidence.
Design files as readable structure
Which screens changed this week, what the onboarding flow contains now, whether the new screen uses the sanctioned components — read from the file rather than eyeballed from exports. Structure beats screenshots for every question except pure aesthetics.
Principles are decisions about pixels
Worked case: your team ratified a design principle — one primary action per screen, no exceptions without a written case, settled after a testing round where a two-button screen split users evenly and converted neither half. Figma renders both buttons beautifully; the principle and its testing story are design law, held by the team.
Screens, read under the law
Through Unl the file read arrives measured: the checkout redesign carries two primary actions — against your principle, the one the split-conversion test wrote. Critique starts from settled law rather than fresh taste. New joiners inherit the principle with its evidence on day one.
Figma to Claude reads the design as structure; Figma through Unl reads it against the design principles you ratified — the two-button screen gets caught by the rule that already fought this fight.
Reads through Unl arrive with measured context — in the presence of the decisions you’ve already settled. The reach lane is live: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.
Read further
Questions people ask
What can Claude read from Figma?
Design files and their structure — screens, frames, flows, components — enough to answer what-exists and what-changed questions and to review against standards.
Does 'figma mcp' work with other clients?
Yes; the surface is standard MCP and connects from ChatGPT or any capable client through its own connector flow.
What design rules belong in Unl rather than a design-system doc?
The judged ones: principles with testing evidence, exception processes, what 'shippable' means. The design-system doc defines the parts; Unl holds the decisions about their use — and serves them during the review, not after it.
What if a screen genuinely needs to break the design principle?
Break it and say why. The principle carries the argument that produced it, so you can see whether this exception is a new case or one that already lost that argument once — which is the difference between an informed exception and the same mistake arriving a second time.
What this is
Think inside your AI world — you stay in command
Save the thoughts, decisions and targets worth keeping, each with its reasoning, carried into every AI session the moment they matter. A new unit of exchange between you and your AI: the Settled Why with standing that travels. Unprompted.
Your whole AI world. What you decided at the epicentre. It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector — quick to connect, in a couple of steps.
MCP native·Human settled·Model agnostic·Your data
Measured Context
Connect Unl to bring the right information into the moment.
Your sources, read against the criteria you set.
The full product, open. Free at launch.