What problem does it solve? Styling Jac client components involves several distinct approaches—Tailwind v4 setup, scoped CSS annex files, conditional class logic, and theme-aware tokens—and choosing the wrong one (especially in jac-shadcn projects) causes specificity conflicts and broken builds. This Skill provides the correct patterns for each scenario. ## Core Features & Use Cases - Tailwind v4 Setup: Step-by-step configuration of tailwindcss with the Vite plugin via jac.toml, with no tailwind.config.js required. - Scoped CSS Annex Files: Auto-scoped .style.css files paired by base name with components, including :global() opt-out rules. - cn() Utility: A Jac implementation of clsx + tailwind-merge for conditional and merged Tailwind classes. - Semantic Color Tokens: Guidance on theme-aware tokens like text-muted-foreground and bg-card instead of hardcoded hex values. - Use Case: When adding a dark-mode-aware dashboard to a Jac app, use this Skill to wire Tailwind v4, write conditional classes with cn(), and apply semantic tokens that adapt to the active theme. ## Quick Start Set up Tailwind v4 in my Jac project and show me how to write a conditional className for an active tab button using cn().
