Parlance Design-to-code contract platform

Parlance is a live platform that keeps design and code in sync. It treats a design system as a contract — colours, spacing, components, terminology, and accessibility rules — and continuously audits everywhere a product lives: design files, code, the live product, and native apps. One engine, packaged as the @parlancelabs/sdk, drives a fast, keyboard-navigable web app built on the Lexicon OKLCH token system, and a family of extensions that put the audit wherever the team already works: Figma, Chrome, Firefox, Safari, VS Code, Xcode, iOS, and AI agents over MCP.

Design systems drift the moment they leave the source of truth. A token gets hard-coded, a contrast ratio slips below 4.5:1, a label says "Click here", a radius is 6px where the token says 10px, and nobody notices until it ships. The problem was not building a system; it was enforcing one, everywhere, without slowing teams down.

• Tokens get hard-coded the moment design leaves Figma
• Accessibility regressions, contrast, targets, labels, ship unnoticed
• Design, code, live product and native apps drift apart
• Standards (WCAG 2.2, ARIA, Section 508, EN 301 549) are checked by hand, late
• Designers and engineers work in different tools with different truths
• One product, but findings look different on every surface

Parlance began as a systems problem, not a screen problem: design systems drift the moment they leave the source of truth. Discovery mapped where drift actually happens, which accessibility standards have to be enforced rather than hoped for, and how one audit could read identically across eight wildly different hosts.

Everything started from the token layer — Lexicon, built in OKLCH so colour stays perceptually even, with light and dark as equal modes and a functional system where severity and status get their own accessible treatments. From there the same language extended outward: the web platform for the full audit and system definition, then the surfaces where work actually happens — a Figma plugin, browser extensions, a VS Code extension, an Xcode extension, and a native iOS auditor — all consuming one shared SDK so the audit engine is written once and reused everywhere.

The challenge was coherence across radically different hosts. A 240px web sidebar, a 360px Figma panel, a browser popup, a VS Code tree view and an iOS screen have nothing in common structurally, but the product had to feel like one thing — and the audit data had to be instantly recognisable on all of them. Underneath, one engine had to be robust enough to ship as a paid product: six fix phases, four security waves and three audit rounds went into making the same contract hold on every surface without drifting.

• One language across web, plugin, extensions and native — wildly different hosts
• Keeping severity and status legible at every size and in every theme
• Designing dense, data-heavy audit views that still scan quickly
• Light and dark as equals on every surface, never an afterthought
• Making the same finding feel native in Figma, Chrome, VS Code, Xcode and iOS
• Hardening one engine into a paid product — security, correctness, and accessibility held under load

Parlance is one contract enforced across eight surfaces beyond its web platform, live and paid at parlancelabs.net. The web platform and marketing site are the hub — they carry the full audit, glossary, pricing and system definition; the Figma plugin, three browser extensions (Chrome, Firefox, Safari), the VS Code and Xcode extensions bring the audit to the point of work; the native iOS Parlance Browser audits live and native experiences; and an MCP server exposes the same audits to AI agents. All of it is bound to the Lexicon token system through one SDK, so the whole platform flips to dark in a click and every finding is colour-true across hosts.

Parlance is a shipped, paid platform — not a demo. One token contract, packaged as a single SDK, is enforced across eight surfaces (Figma, Chrome, Firefox, Safari, VS Code, Xcode, iOS, and an MCP server for agents), with accessibility (WCAG 2.2, ARIA 1.2, Section 508, EN 301 549) and light/dark treated as structural guarantees rather than later passes. Getting there took the unglamorous craft: six fix phases, four security waves and three audit rounds to make one engine hold on every host at production quality. The contribution is the systems thinking that lets one language survive contact with a web platform and eight surfaces beyond it, and stay live.

“

Keep design and code telling the same story.