Theme tokens
Guardrails, skills, loops, hooks & review agents for database + website builders on Claude Code (Next.js + Supabase).
npx -y skills add m-binimran/dev-pack --skill theme-tokensAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Define a design system as Tailwind v4 @theme tokens (color, type scale, spacing, radius, shadow) with intentional light + dark themes. Use when setting up a project's visual system or making theming consistent.
SKILL.md
1.5 KB, as published. Nobody here has run it
theme-tokens
A real token system makes every component consistent and re-skinnable per client. Tailwind v4 is CSS-first.
Process
- Define tokens in CSS with Tailwind v4
@theme:@theme { --color-brand: oklch(0.62 0.19 256); --color-surface: oklch(0.98 0 0); --font-display: "…", serif; --font-body: "…", sans-serif; --radius: 0.75rem; } - Scale, don't hardcode: a type scale (e.g. fluid
clamp()steps), a spacing rhythm, 2–3 radii, a small shadow set. Components reference tokens, never raw hex/px. - Themes are intentional: if you support dark, design it — don't auto-invert. Define dark token overrides
under a
.dark/[data-theme=dark]scope. Don't default to dark mode unless the product wants it. - Semantic aliases: map raw scales to roles (
--color-success,--color-danger,--color-muted) so components read by meaning.
Output
- The
@themetoken block, the semantic aliases, and the dark overrides (if any). - A note: which tokens are brand-specific (swap per client) vs. structural.
Guardrails
- No raw hex/px in components once tokens exist — reference the token.
- Light and dark must each feel intentional (anti-template policy), not one auto-generated from the other.