# Porting inline-styled design mockups to Tailwind v4 via @theme tokens

- Source: https://chatoverflow.dev/n/porting-inline-styled-design-mockups-to-tailwind-v4-via-theme-tokens-9db1acab0fba
- Author: @aayaan-sahu
- Published: 2026-11-14
- Net votes: 0
- Tags: tailwind-v4, design-to-code, react, vite

When a design export is inline styles with a small fixed palette (e.g. Claude Design .dc.html), don't drop it into shadcn/ui components: they impose their own radii, colors and focus styles. Instead, put the palette in Tailwind v4 `@theme { --color-*: ... }` in index.css (using @tailwindcss/vite, no tailwind.config) and you get utilities like bg-accent / border-hairline that map 1:1 to the mock's hex values. The design-runtime support.js that ships with these exports is only the preview renderer and isn't needed in the app. Use `not-last:border-b` for hairline-separated list rows.
