From Rules to Runtime: Building an AI-Powered UX Writing Checker in Figma
Our Voice & Tone guidelines lived in a document nobody had time to check copy against — so I built a Figma plugin that does it automatically, reading intent with Claude instead of just matching keywords.
The problem
By the time this started, our design system spanned a large, constantly growing set of Figma files across two enterprise security products, touched by 10+ product owners and engineers, each reading UI copy a little differently.
Our Voice & Tone guidelines were solid on paper, but they lived in a document: nobody had time to check every button, toast and error message against them by hand, so inconsistency only surfaced after it had already shipped.
My approach
There wasn't an existing tool for this — enforcing a specific internal writing standard, semantically, inside a design file, isn't a problem a spell-checker solves.
So I split Voice & Tone into two layers: Claude API for the judgment a linter can't make — does this line blame the user? — and structured JSON for feedback a designer can act on inside Figma, not in a report nobody opens.
Architecture
The plugin reads text nodes straight off the Figma canvas, sends them through a small proxy for the actual model call, and writes structured feedback back into its own panel — three moving pieces, one continuous loop.
The rules system
A growing set of rules came out of turning Voice & Tone from prose into something a plugin could actually test. A few examples:
"Don't blame the user."
"Be specific about errors."
"No punctuation on buttons."
"Keep alert tone calm."
Plugin in action
Run against representative frames built in the product's own design system. Click any screen to expand it.
Outcomes
Works on any Figma file, any frame — not just the ones I made.
Voice & Tone documentation itself got formalized as a byproduct of writing the rules.
Production-ready security: API key in Vercel environment variables, plugin token auth, private GitHub repo.
What I learned
Where AI actually helps, and where it doesn't. Semantic judgment — tone, blame, clarity — needs a model; deterministic checks — casing, punctuation — don't. Treating them differently kept the plugin fast and cheap to run.
A CORS-safe proxy architecture, built from the start. A Figma plugin can't call an external API directly, so the Vercel proxy became the real security boundary — not an afterthought bolted on later.
Turning documentation into executable logic. The hard part was never the API call — it was making "don't blame the user" into something a machine could actually test.