What problem does it solve? Keeping design tokens consistent across Tailwind utilities and hand-authored CSS in an Astro project usually means duplicating values or locking tokens into one framework. This Skill sets up a single tokens.json source in DTCG format, compiled by Style Dictionary into flat CSS variables plus a Tailwind v4 @theme bridge, so tokens survive a framework swap and dark mode re-themes every consumer at once. ## Core Features & Use Cases - Three-layer token pipeline: base, semantic, and component token files compiled by Style Dictionary v5 into tokens.css (:root --ds-* variables) and theme.css (@theme inline bridge) via prebuild/predev npm hooks. - Astro 7 + Tailwind v4 wiring: verified @tailwindcss/vite plugin config, global stylesheet import order, no-flash dark-mode inline script, and scoped @apply via @reference. - Component authoring conventions: classes over style attributes under hash CSP, data-attribute variants, and a review checklist banning hardcoded design values. - Use Case: You are starting an Astro 7 site styled with Tailwind v4 and need dark mode plus a second CSS consumer. Use this Skill to author the three token files, generate the compiled CSS, and wire the Vite plugin without hitting the known OKLCH, hoisting, or silent-failure pitfalls. ## Quick Start Set up a Style Dictionary design-token pipeline for my Astro 7 and Tailwind v4 project with dark mode support.