Figma Make | Local code editing connects design and Git workflows
Figma has expanded Figma Make with support for working directly on local codebases, giving product teams a more visual way to edit running interfaces. Published on May 28, 2026, the update lets users connect Make to a repository, select elements, adjust properties, annotate UI changes, create branches, save local commits, and prepare pull requests for engineering review.
Figma Make connects visual design work with local production code
Figma Make is moving closer to the codebase, and that is a major shift for web designers and product teams. Instead of only generating prototypes or mockups, Make can now connect to a real local repository and let users edit the running app visually while the agent updates the relevant code behind the interface.
For template creators, front-end teams, and UI designers, this is exciting because it reduces the gap between design decisions and implementation. Layout, spacing, color, typography, and sizing changes can be explored directly in the working interface, while Git history keeps those changes reviewable by the team.
How local code editing works in Figma Make
According to Figma, users can connect a local repository or clone one from GitHub, then open the app inside Make with real data. From there, they can select elements on the live interface and adjust properties such as layout, colors, fonts, and spacing while the agent finds and edits the related code.
Figma also adds annotation-based prompting for changes that go beyond simple visual properties. Users can place annotations directly on the rendered UI, describe what needs to change, and reference multiple elements at once when an interaction, animation, or behavior needs more context.
New Git workflows for designers and product teams
The most important workflow change is version control. Figma Make supports Git operations such as creating branches, reverting commits, and reviewing commit history. Until a pull request is opened, the changes are stored as local commits, which keeps the development process intentional instead of pushing visual experiments directly into production.
This makes the feature especially useful for design-engineering collaboration. Designers and product managers can explore changes visually, while engineers still review the branch, inspect the code, and decide what should be merged through the normal pull request process.
The feature is currently available in closed beta, and Figma's help documentation notes that it requires the Figma Beta desktop app for Mac, access to the beta, a Git repository, and repository access through a version control provider.
Why it matters for modern web production
For animetemplates, the key takeaway is that design-to-code workflows are becoming more visual and more collaborative. A template, landing page, dashboard, or app interface can be adjusted in context, while the code remains connected to branches, commits, and review workflows.
This is powerful, but it also requires discipline. Visual code editing can speed up iteration, but production teams still need code review, accessibility checks, responsive testing, naming consistency, and design system alignment before changes become part of a real project.
Daisuki's Take: What This Means for Web Designers
We see Figma Make's local code workflow as an important step toward making design changes more connected to real production systems. The value is not only editing a running interface visually, but keeping those changes tied to branches, commits, and pull requests so design exploration can stay reviewable.
For web designers and creative teams, this can make template and interface iteration more practical. Layout spacing, typography, component adjustments, and interaction notes can be tested directly against a working codebase, while developers still have a clear Git workflow for reviewing what changed before anything is merged.
The limitation is that visual editing can still create technical debt if it is not reviewed carefully. We need to check code quality, accessibility, responsive behavior, naming consistency, component reuse, and whether the final implementation matches the design system. Faster visual changes are useful, but human review remains essential before production.
Sources and Recommended Links
- Figma Make, now on your local code | Figma Blog (Official)
- Make in your local codebase | Figma Help Center (Official)
- Figma Make | Figma (Official)
