Extensions

parlance extensions bring your UI contracts into the tools your team already uses — the design canvas, the browser, your editor, native development, shipped apps and your AI agents. Every extension consumes the parlance client SDK and connects to your workspace, so each one audits against the very same contracts, glossaries and tokens. One source of truth, in every tool you reach for.

For how audits and findings work, see audits. To browse the extensions with feature detail, see the extensions showcase.

How extensions fit together

Each extension is a different lens on the same contract:

• It connects to your workspace, so it sees your projects, contracts and glossaries.
• It runs audits against the same contracts the platform uses — no separate rules per tool.
• It reports findings by severity and surfaces drift in context, then can push those findings back to your workspace.
• It consumes the client SDK, which is the single way every extension talks to parlance.

The result is that design, code, live products and native apps are all held to one definition, wherever the work happens.

The six extensions

Figma plugin

Audit designs against your contracts without leaving the canvas. Surface: design.

• Live contract checks on frames and components.
• Flags token, glossary and accessibility drift in place.
• Pushes findings back to your workspace.

Showcase: /extensions#figma-plugin.

Browser extension

Audit live production against the same contracts, in a real browser. Surface: live. Runs in Chrome and Chromium.

• Run audits on any URL.
• Inspect contrast, ARIA and token usage in the wild.
• Capture findings to a project.

Showcase: /extensions#browser-extension.

VS Code extension

Catch drift in the editor, as you write. Surface: code. Runs in CI too.

• Inline contract diagnostics.
• Jump from a finding to the offending line.
• Wire it into continuous integration to gate every change.

Showcase: /extensions#vscode-extension.

Xcode

Bring contracts to native iOS development. Surface: native, during development. Runs in Xcode against Swift.

• Audit SwiftUI and UIKit screens.
• Built on the shared ParlanceKit core.
• The same contracts as web.

Showcase: /extensions#xcode.

Native auditor

Audit shipped native apps against your design system. Surface: native.

• Token and accessibility checks on native UI.
• iOS today, more to come.
• One source of truth across platforms.

Showcase: /extensions#native-auditor.

MCP server

Give your AI agents and tools first-class access to parlance audits over the Model Context Protocol.

• Exposes contracts, glossaries and audits over the Model Context Protocol.
• Run audits from any MCP-compatible client.
• Automate enforcement in agentic workflows.

Showcase: /extensions#mcp-server.

Choosing the right extension

Pick by where the work happens:

• Designing in Figma — the Figma plugin.
• Checking a live product — the browser extension.
• Writing or reviewing code, or gating CI — the VS Code extension.
• Building native iOS — Xcode.
• Auditing shipped native apps — the native auditor.
• Driving audits from AI agents — the MCP server.

Next steps

• Audits — what audits report and how to read findings.
• Client SDK — the SDK every extension consumes.
• REST API — automate parlance in your own services.
• Extensions showcase — the full feature breakdown for each extension.