gsp-brand-sync

To reconcile brand drift, you need to perform a brand sync that detects divergences between shipped implementation and source definitions. This process diffs design tokens, samples user-facing copy, and inspects visual patterns to generate an actionable sync report with file:line evidence.

A brand audit for a design system codebase is a four-dimension analysis that detects divergences across tokens, voice and tone, visual component patterns, and personality. It samples shipped code and content to prevent drift between design intent and the final product.

You can generate a SYNC-REPORT.md by running an automated brand sync against your project. This report includes token diff tables, divergence classifications, and an Update Map providing precise file:line evidence for targeted edits.

Yes, you can update brand definitions mid-development using an interactive sync process. It requires explicit confirmation before writing brand files, shows before/after changes, and supports per-dimension selection to ensure manual tweaks are intentionally reconciled.

Brand sync works with projects where a linked brand exists in .design/branding or project config files. It analyzes these source definitions against the shipped codebase to correct the baseline for future builds.

You should avoid automated brand sync when your project lacks a linked brand definition in .design/branding or config files, as the tool requires this canonical baseline to detect token, voice, and visual pattern divergences accurately.