What it does
Turns a Figma file and a requirement into the brief a designer can start from, and the one engineering can build against. It reads the frames, the components used, and the comments already on the file, then writes what the screen has to do, which states must exist, and where the design and the requirement disagree. The states are the point. Most handoffs specify the happy path and discover the rest in code review: what this looks like empty, loading, at the longest realistic content, with a failed request, with no permission, on a narrow viewport. The brief lists each one and says explicitly which are already designed and which are not — an unlisted missing state becomes a developer's improvised guess. It also names the drift. A frame using a one-off colour or a detached component instead of the system's is worth catching before it ships, not during a design-system audit six months later. It never edits the Figma file. It reads, and it writes one Confluence page for review.
Example prompts
- Read this Figma file and write the brief for the checkout flow.
- Which states are missing from these frames — empty, error, long content?
- Does the design actually cover what ABC-412 asks for?
Before you connect
The credentials this agent will ask you for — the full setup is on the Setup tab.
Needs 2 credentials (2 required) to connect. See setup
