Figma MakeWIP 2026

Building Air for Figma Make

Air for Figma Make integration overview
Role

Solo Designer & Engineer

Team

1 Designer (Me)
AI Tools

Skills

Product Design
Front-end Engineering

Overview

I’m currently building a new integration path between Air and Figma Make by connecting React components through GitHub, NPM, and Figma Code Connect, then using that foundation to create reusable starter templates for teams.

The problem

Where Make falls short

At Carrier, Figma Make has opened up new possibilities for rapid prototyping, but in its current state it lacks the context needed to generate work that aligns with Air. Make prototypes can be slow to build, often rely on code sources that do not reflect our styles or component structure, and have no built-in understanding of our guidance or development standards. Without stronger system integration, teams risk starting from output that looks plausible but drifts from the design system in both structure and quality.

Illustration of Figma Make limitations

Building the bridge

Connecting Air

To solve that, I’m currently creating a new integration path between Air and Figma Make. Because Figma Code Connect does not currently support Bitbucket, where our parent React repository lives, I’m rebuilding and publishing our React components through GitHub, setting up NPM, and connecting components individually through Figma Code Connect.

Integration flow connecting Air to Figma Make via GitHub and Code Connect

Grounded in real components

This work is creating a way for Make to reference Air’s actual coded components instead of disconnected stand-ins, while staying aligned with our public Storybook and broader front-end system.

Repository import from GitHub into Figma

Stronger start

Starter templates for scale

With that foundation taking shape, I’m building reusable Make templates that give designers, PMs, and engineers a faster way to start from the right structure. Instead of recreating the same wrappers each time, teams can begin with starter templates built from Air’s actual components, including shared elements like navbars and app bars. These templates are designed to strengthen all three pillars of Air by bringing in our theme styles and tokens for visual parity, mirroring the proper component structure through coded React components, and supporting guidance.md files that help embed best practices directly into the workflow.

Mobile starter template built from Air components

Embedded onboarding

To make the templates more usable out of the box, I’m including built-in starter guidance such as setup instructions, prompt recipe links, and contribution resources. This gives teams not just a starting layout, but also clearer direction for how to work within Make in a way that aligns with Air.