A personal side project, not an official Bootstrap thing.
I co-maintain Bootstrap, but this is mine, it is unaffiliated and unendorsed, and nothing in it is a plan of record for v6.
It is also early and openly draft, see the caveats at the bottom before you rely on any of it.

While reading v6-dev's Sass end to end I kept circling the same observation: Bootstrap 6 already has a real token system: oklch() scales generated with color-mix(), semantic $theme-colors, a per-component $*-tokens map emitted as custom properties. What it does not have is that system in a portable form, the kind a Figma library or a Style Dictionary pipeline can read.

So I spent some time on two things.

The tokens. Bootstrap 6 lifted into DTCG format, layered primitive → semantic → component, and exported to Sass, CSS custom properties, TypeScript, Style Dictionary and Figma. 1206 tokens, covering all 64 of upstream's $*-tokens maps. Extracted from v6-dev by a script, not by hand, so it can be re-extracted when upstream moves.

A Theme Builder. A browser app for designing a theme by editing those tokens, with real Bootstrap components re-theming beside you. Eight controls that each move a lot of the system (brand colour, radius, density, type, shadow) or all 1206 tokens if you want them. Light and dark side by side, because light-dark() means a v6 theme is always two themes. Contrast and colour-vision checks built in. Export gives you a custom.scss carrying only what you changed.

bstokens verify compiles upstream's bootstrap.scss and the configuration exported from these tokens, then asserts the resulting CSS is identical. Today it is, across all 18174 lines. CI runs that on every push, and a nightly job opens an
issue when v6-dev drifts from the committed document. So when I say the export is byte-identical to hand-written config, that is a test rather than a claim.

What's genuinely draft. It tracks the current v6-dev which will become 6.0.0-alpha1, and alphas move so token names will
change under it and saved themes will need migrating. Nothing is published to npm. The app is an evening-shaped thing in places.

One side effect worth mentioning. Doing this surfaced some findings about Bootstrap itself tracked on my repository. I'll analyze them precisely and create issues in this repository soon to improve Bootstrap 6 alpha.

If you like the idea of this tool, drop a ⭐ to let me know it’s something useful for the Bootstrap community.

You can also open an issue or share your thoughts in this discussion. I’m open to all kinds of feedback, including the negative stuff! Honest feedback is always welcome. 🙌

You can try it at https://julien-deramond.github.io/bootstrap-tokens/

This is MIT, the source is here https://github.com/julien-deramond/bootstrap-tokens