Features

Three things Bedrock Flows does: shows complex flows clearly, lets your team and agents work on them together, and keeps everything true to your design system.

01

Visualizing complex wireflows

Turn a tangle of screens, states and edge cases into one graph the whole team can read at a glance.

See the logic, not a slide deck

A wireflow is a series of screens drawn as an interconnected graph — follow the arrows and you understand the interaction model. Faster to read than a video, and asynchronously understandable by the whole team.

edge case

Edge cases & page states, laid out

List every edge case and page state explicitly — "code expired", "email already registered", the multi-participant variant of a step — so everyone sees exactly which variations exist.

One flow, three views

Every flow is a Wireflow, a logical Mermaid diagram, and a written spec — and any screen can Copy to Figma, at the screen or whole-flow level. Figma never disappears.

Decide responsiveness on the flow level

Each flow declares the viewport range it’s designed for — a native-phone band, a responsive-web span, or desktop-only — so you click through every screen at the size it’s actually meant for, and the review chrome keeps everyone honest about the range.

02

Collaborate with your team and agents

The classic product trifecta — PM, designer, developer — works around one living artefact, with Bedrock Flows and its agents in the middle.

Bedrock Flowscomments → agentsProduct manager / CEOWrites specs · sets directionDesigner / design eng.Designs the best UXDeveloperShips it: dev · deploy · security

As roles converge, it helps the whole trio — or any two of the three — stay in sync.

Comment at every level

Threaded comments on the whole wireflow, an individual screen, or a design-system component itself — with resolve and re-open, just like Figma.

Hand a comment to an agent

Any comment is actionable by an AI agent. Proposed changes land in an agent design queue where you approve or reopen with a reply — with an email on each new design.

A real deliverable

The PM gets a living repository of specs; the designer bridges Figma to interactive prototypes; the developer gets a clear, validated view of what to build.

03

Design systems & guardrails

Agentic design tends to drift. Guardrails keep prototypes true to your design system — and keep you in control of how it evolves.

F-001 · Step 4 · Confirm phone
⊹ DS X-rayDS 7Mixed 0Turn on ⊹ X-ray to inspect the components.

X-ray any screen to reveal the design-system component behind every element — and jump straight to its Storybook.

Command-menu to the system

A ⌘K palette jumps from any element to its component in a generated Storybook — with a Figma source link and code you can copy.

Portable, framework-free systems

Author components as plain CSS + Nunjucks macros + JSON variants — no framework or build tooling to learn, and the whole system travels with your project.

Versioning & archiving

Run multiple design systems, version your wireflows (a v2 supersedes its predecessor), and archive what is no longer active — with the history kept.