← Cycles
design · c15archivedstarted Mar 11Auto draft — not yet reviewed

Figma-to-Vue Workflow

Why we did this

We had Figma designs and a tool that can read them, but no tested way to turn a Figma component into a working part of our shared library.

What happened

It worked: the policy card came out of Figma as a real shared part, with four sizes and two states. The output needed tidying, and the Figma-to-code link was left for later.

Early → finalThe policy card was read out of Figma and rebuilt as a shared part in four sizes, green when a rule is met and red when it is not.
At a glance
3
changes
0
conversations
2
decisions
0
outside helpers

What changed

The two changes that matter most, in plain words. Open any one to see it.

  1. 1

    The policy card was read out of Figma and rebuilt as a shared part in four sizes, green when a rule is met and red when it is not.

    The policy card, from Figma to code · came from Mark Parsonopen →

  2. 2

    Layout, sizes and colours came across cleanly; exported images and tags from the drawing had to be replaced by hand.

    What survives the trip from Figma · came from Mark Parson

Also in this cycle
  • The link that would tie the Figma drawing to the code was never registered. In words

How we got here

Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.

Someone said

From the record: no recorded conversation behind this one.

We decided

c15-D1 Product-specific parts get their own folder: the card lives under security, not with the general-purpose parts. — Mark Parson

c15-D2 Stat columns use the library's number and sparkline parts instead of the images Figma exports. — Mark Parson

So now

The policy card was read out of Figma and rebuilt as a shared part in four sizes, green when a rule is met and red when it is not.

Someone said

From the record: no recorded conversation behind this one.

We decided

c15-D2 Stat columns use the library's number and sparkline parts instead of the images Figma exports. — Mark Parson

So now

Layout, sizes and colours came across cleanly; exported images and tags from the drawing had to be replaced by hand.

Thanks to

People outside Qpoint first. Every thank-you points at something they said or made.

MP
Mark Parson
Qpoint team

Ran the first Figma-to-code test

Tested the Figma reading tool on the real PolicyListingItem frame and turned its output into the shared policy card, with a security group of its own.

All images

Every picture from this cycle. Click any one to step through them all.

The pairs

The policy card, from Figma to codeEarly → final
→

Everything captured · 2

The full record 0 decisions · 9 key-change entries · 370 words · 1 captures

The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.

Open the record for c15 →

Qpoint Brand Style Guide