← CORE HOLDINGS / POSITION
FIGMA-PLUGIN ACTIVE
Figma Annotate
A structured review-trail plugin that turns scattered design feedback into addressable, statused, traceable records — so critique stops dying in chat threads.
annotationcollaborationreview-ops
TYPE
figma plugin
ROLE
Design + Build
STACK
TS · React · Figma API
SINCE
2025.04
OPEN PRODUCT ↗READ THE CASE STUDIES (2) →
Figma Annotate — full product UI
[ WHAT IT IS ]
Feedback as data, not disappearing messages.

Every comment becomes a first-class object with an owner, a status, and a link back to the exact frame. Reviewers resolve threads in place; designers export a clean decision trail when the file ships.

[ HOW IT WORKS ]
01
Drop a pin

Click anywhere on a frame to anchor a comment to real coordinates. The pin binds to the node, not the pixel, so it survives the next layout pass.

Pin placement
Pin detail
02
Assign & status

Every thread gets an owner and a state — open, in progress, resolved, or won’t fix. The state machine is deliberately tiny so nobody has to learn it.

Status panel
03
Export the trail

Ship with a Markdown or CSV log of every decision and who made it — the artifact that turned out to be why people actually installed the plugin.

Export dialog
Exported markdown
Trail overview
[ LANDING PAGE ]

A single-page pitch for the plugin: the problem in one line, a live annotated frame you can poke at, and the install button. Written to be read in under thirty seconds.

VISIT LANDING PAGE ↗
Landing hero
Pricing panel
Under the hood
AFrame-anchored pinsComments survive layout changes by binding to node IDs, not pixels.
BStatus modelA tiny state machine keeps every thread accountable through to resolution.
CDecision exportOne click produces a portable log for handoff, retros, or audit.
RELATED CASE STUDIES (2)
Turning the weekly report into something a system does
Methodology for moving a recurring manual chore into an automated pipeline — without losing the judgment that made it worth reading.
READ →
Why review feedback keeps dying in group chats
A recurring annoyance became a data model, then a shipped plugin — the full trail from problem discovery to the decision that shaped it.
READ →
✎ RELATED WRITING
Versioning a design system beyond the Figma library2026.067 MINWhere AI-assisted design review stops being useful2026.056 MIN