TechPrufer
Sign inGet started

Blogs›Figma›Figma File Organization and Permissions Model

Figma File Organization and Permissions Model

Figma File Organization and Permissions Model

2
posts
2026

Figma has introduced nested folders to improve file organization for growing teams. This required a significant overhaul of the underlying content and permissions model, impacting the file browser, admin controls, sharing, permissions, and core infrastructure. The development process shifted towards a 'lead with code' approach, with engineers making design calls and designers pushing code, fostering closer collaboration and faster iteration through early PRs and live demos. This evolution also introduced Code Connect, which enriches Figma's MCP server response by connecting Figma components to real components in the codebase, providing agents with production-relevant code snippets. This reduces token usage, improves code quality, and decreases task duration for design-to-code tasks performed by coding agents.

2026

Better code, fewer tokens: The benefits of Code Connect in MCP

8/5/2026

This post details the evaluation of Code Connect's impact on coding agents' performance when using Figma's MCP server. It quantifies the benefits of Code Connect in terms of reduced median task duration (-19.6%), increased code quality (+1 on a 1-4 Likert scale), and reduced median token usage (-29.5%). It explains how Code Connect provides context by substituting generated React with production-accurate code snippets, enabling agents to use existing codebase components instead of reinventing them. The post also outlines the methodology used for measuring these impacts, including the eval harness, scoring rubric, and the design systems tested.

Code, craft, and the making of nested folders

8/3/2026

This post details the engineering effort behind implementing nested folders in Figma. It highlights a shift in development methodology from traditional product development to a 'lead with code' approach, emphasizing early PRs for rapid prototyping and validation. The post also discusses the blurring of roles between engineering, design, and product management, with engineers taking on design decisions and designers contributing to code. This collaborative approach, facilitated by tools like CoderBox and a strong design system, allowed for faster iteration and a deeper understanding of technical constraints and implementation complexities.