Create design tokens

Create a set of design tokens for the product's component library used by engineering. Extract spacing, border-radius, primary and neutral color values, font sizes and weights, and elevation shadows from the file named System Tokens v2. Export them as JSON and CSS variables, include clear names that match our component props (token names must match how engineers refer to them in code), and drop the files into the Shared Assets folder by Wednesday.

Before I publish the tokens to the team, make them easy for engineers to adopt: surface the token-to-prop mapping at the top, group tokens by usage (layout, typography, color, elevation), flag tokens that are duplicates or near-duplicates, and call out any tokens that will break existing components if renamed. Point out anything that would make an engineer hesitate to import them.

I exported a token JSON and engineers say the spacing tokens don't align with the variable names in the repo's component library. I don't know whether the mismatch came from an earlier rename in the design file or from my export settings. What’s the most likely cause and how should I correct it with minimal churn so we don't block the sprint? Should I rename tokens to match code, update the repo, or provide a compatibility map?

Over several releases we keep breaking components because token names change or values drift without coordination. This costs engineering time and trust. What habit should our design team adopt to stop this? Suggest a governance routine or a minimal naming convention and a release checklist that prevents accidental renames and makes token updates predictable.