For an identity security vendor, the interface carries as much weight as the cryptography behind it. 1Password ships across mobile autofill, desktop apps, and a browser extension that now fields credential requests from AI agents, and each of those surfaces has to read as unmistakably 1Password. Matt Davey, the company's Chief Experience Officer, reduces the goal to two words: "trust and certainty." Any prompt a user encounters must make the consequence of acting on it obvious.

Reaching that bar requires testing ideas that look and behave like the shipping product, which is why the product design team adopted Figma Make inside its prototype codebase. Davey oversees a design organization of roughly 40 people, split around the audiences 1Password serves—security and IT admins, consumers, and developers.

Turning design guidance into machine-readable guardrails

Consistency across those audiences falls to a centralized design systems team. As recently as about eight months before the account, its output was documentation and guidelines that designers read and discussed together. As AI tools take on more UI generation, the team now treats that guidance as something the tools themselves consume, so Figma Make and other agents follow the same rules a designer would.

"Trust is at the foundation of everything we do," says Ryan Williamson-Cardneau, Senior Manager of Design Systems & Design Language. "As UI gets generated on the fly, the guardrails we put in place and the best practices we've codified through years become critically important."

Nearly two decades of design guidance—content design, design principles, components, and the reasoning behind typography decisions and setup flows—became context the tooling can draw on in the moment. Williamson-Cardneau frames the audience as twofold: a human in the loop asking a question, and an agent handed a task that must determine how to complete it and where the guardrails lie.

A front-end-only playground instead of production

Prototyping in production environments was never realistic; the setup and maintenance burden is too heavy. "They're just too cumbersome for a designer to pick up," Williamson-Cardneau says. The design systems team instead assembled an internal prototype playground: a front-end-only repository with code templates for 1Password products, generated from the team's Figma files and product references.

The lightweight setup made the playground a natural entry point for Figma Make. Designers open it in Figma Make and begin work with the repository's skills and rules already in place. Some still go straight to an IDE, but others prefer the familiarity of Figma. "You can click into it, type the new text, and the change is there and queued," Williamson-Cardneau says. "People are finding their own new unique ways to work with the tools at hand."

Code Connect ties the playground's components to their published counterparts in the Figma library. Changing a primary button to a secondary one is a dropdown selection rather than an HTML edit or an agent prompt.

What the workflow looks like in practice

Williamson-Cardneau recently updated the template for a generally available product by feeding revised Figma screens into the existing coded template, then correcting individual elements—including a stubborn padding value swapped for the proper design system variable. Rather than making 30 small edits by hand, Figma Make handled roughly 80% of them correctly, leaving only a final pass. "I know it's using the foundations from our design system," he says.

"Figma Make cut my editing time down from 'there are 30 things I need to make quick edits on' to 'it got 80% of those right.'" — Ryan Williamson-Cardneau, 1Password

Designers can also encode multiple directions as toggles within a single prototype, switching between concepts in one place. Davey singles out what he calls visual branching: duplicating a prototype, making small changes, and comparing versions side by side on the canvas—"Doing that in any other medium is really painful," he says. With chat connected to 1Password's MCP, Figma Make also serves as a design partner. "I find myself having a back and forth about things like, 'Do you think that this works with this?'" Davey says. "It's a sparring partner."

The team is additionally exploring code layers, which place coded prototypes directly on the canvas and let designers produce full user flows rather than isolated working prototypes. "Designers want to see and talk through a bird's-eye view of the UX instead of recording a voiceover," Williamson-Cardneau says, citing the agent's ability to track clicks through a code layer and generate an artboard as useful.

Earlier alignment—and more realistic testing

Every designer at 1Password has been onboarded to the playground, and engineers and PMs now build prototypes there as well. But for Williamson-Cardneau the main benefit is communication rather than speed. The original problem was getting alignment on ideas early—reaching a shared good idea quickly and at sufficient fidelity to understand the value being put in customers' hands. Davey points to the canvas as the center of gravity: "The real superpower of Figma has always been the canvas," he says, likening it to printing out a website's pages and pinning them to a whiteboard.

Working in code has made early concepts cheaper to communicate. "We're able to show micro-interactions in a way we couldn't previously," Williamson-Cardneau says. The realism extends to user testing, where coded prototypes have largely replaced wired-up Figma ones, so participants no longer hit a prototype's edges and get steered back to the "happy path." For a security product this changes the findings. "User testing someone with an empty test vault containing no real credentials is a completely different scenario from giving that user a realistic, populated experience," Davey says.

Participation has spread beyond the design org: engineers who first picked up the playground at hackathons now bring their own prototypes to the table, and PMs recently used one to pitch a roadmap item. "That feels like a pretty strong win," Williamson-Cardneau says, "and very much outside the norm of who you expect to use a design tool right out of the gate."

He argues that the approach moves designers closer to what actually ships while making the shift less intimidating. "Seeing the familiarity of Figma in this new territory helps designers trust that they can wade into this with the rest of us," he says.