From the designer's decisions to the coder's agent

Small teamsProduct team with one designer and three frontend developers

Leela, our designer, settled on 'cards: radius-lg, no shadows, 24px padding' in a review on Monday. By Thursday two developers' agents had built cards with drop shadows, because the Figma comments never reached their prompts.

How do I get our designer's decisions into the developers' AI agent prompts?

Have the designer record each settled choice with ArcRoom's arcroom decide, with the why and a link to the frame. When a developer asks for a new card, recall hands the agent the design decisions that fit, and a later decision replaces the old one, so agents only see what is current. ArcRoom doesn't read Figma: only decisions someone typed in reach the agents.

Also asked as: Our developers' agents keep ignoring what the designer decided. How do I fix that? · How do I make AI agents follow our design system choices? · Can a designer's decisions reach a developer's AI agent?

The work

Leela records each settled choice with arcroom decide, with the why and a link to the frame.

ArcRoom keeps
  • Code map
  • Decision
  • Recall
The next agent gets

Decision (Oct 27, leela): cards use radius-lg, no shadows, 24px padding.

Step by step

  1. Leela records each settled choice with arcroom decide, with the why and a link to the frame.
  2. A rule on the components folder says where cards live.
  3. When a developer asks for a new card, recall hands the agent the design decisions that fit.
  4. A later decision replaces the old one, so agents only see what is current.

What the agent sees

Decision (Oct 27, leela): cards use radius-lg, no shadows, 24px padding.
Why: shadows clashed with the dark theme. Source: Figma 'Cards v3'.
Code map: apps/web/components/card · base Card and variants

Compared with today's tools

Figma Dev Mode + a Notion spec

Developers open the frame in Dev Mode and paste the spec into the agent before building.

Setup
1 hour
Ongoing
paste specs into each prompt, ~5 min per component

ArcRoom

Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.

Setup
2 min per person (npx arcroom init)
Ongoing
None

Figma is the real source for visuals and wins there; ArcRoom puts the decision in front of the agent when nobody remembered to paste it.

Where it stops

ArcRoom doesn't read Figma. Only decisions someone typed in reach the agents.

Try it in your project

Works with the agents your team already uses, and any agent over MCP or the HTTP API.

More in small teams