Tutorials

Install ds-bridge, answer the preferences dialog, and read your very first lint finding — start to finish, in about ten minutes, no Figma account required.

Find every hardcoded color, spacing, and radius that should be a design token — and fix exact matches automatically.

Turn the checks you already run into numbers you can watch — on-system share and a system score, recorded run after run and on every push in CI — then set targets, share a one-page manager report, and export the numbers.

See every product repo that uses your design system in one ranked view — system score, on-system share, drift, contrast, readiness and freshness — built on your machine from the history each repo already records.

Not every deviation is a mistake. When a component keeps getting overridden run after run, ds-bridge flags it as needing an owner, so the team can decide whether to fix the usage or evolve the component, without ever hiding it from the numbers.

Diff your token source against built outputs to find stale, missing, and orphaned tokens — scored and trended over time.

Save your Figma token so it survives restarts, point ds-bridge at your design-system library, and register the product files your team designs in — the one-time setup behind every Figma-powered feature.

Score any Figma frame’s handoff readiness 0–100: detached instances, raw values, missing styles — before an engineer is blocked.

A component-by-component matrix of what exists in Figma, what exists in code, and where the props disagree.

Point figma-impl at a frame and get code assembled only from your registered components and exact tokens — with everything it can't resolve reported as a gap instead of invented.

Audit your color tokens for WCAG contrast across light, dark, and every other mode — read which pairings fail, see lightness-only fixes, and gate CI on the result.

Diff your published Figma library against the last snapshot, classify each change as breaking, additive, or cosmetic, see how many code call sites it touches, and gate CI on the breaking ones.

Turn your git history, Figma versions, and token changes into a single audience-segmented changelog — one document everyone on the team can read.

Pick a persona view — one of six roles or everything — so ds-bridge report opens the dashboard you actually read, from one shared history, in HTML, terminal, or a published site.

Turn your saved registry, a code scan, and your token map into one MDX page per component plus a machine-readable llms.txt — generated, gap-honest, and reviewable in a pull request.