Tailwind CSS 4 patterns — cn() utility, theme variables, no var() in className
Tailwind 4 styling rules: styling decision tree, never var() or hex in className, cn() usage rules, style constants for libraries, dynamic values, dark mode, responsive, arbitrary-value escape hatch
- What
- Tailwind 4 styling rules: styling decision tree, never var() or hex in className, cn() usage rules, style constants for libraries, dynamic values, dark mode, responsive, arbitrary-value escape hatch
- Cost
- Free
- Needs
- a Tailwind CSS 4 project — the skill is a styling guide the agent follows, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @gentleman-programming's tailwind-4: an opinionated Tailwind CSS 4 styling skill. Core rules: a styling decision tree (Tailwind class exists → className; dynamic value → style prop; conditional → cn(); library can't use class → style prop with var() constants), never var() or hex colors in className (always semantic Tailwind classes), the cn() utility (clsx + tailwind-merge) with explicit when-to-use/when-not-to rules, style constants for libraries that don't accept className (Recharts), style props for truly dynamic values, plus flexbox/grid/spacing/typography/borders/states/responsive/dark-mode patterns and the arbitrary-value escape hatch. Honest caveats: compact, single-file guidance — no bundled references; the skill's frontmatter claims Apache-2.0 while the catalog manifest records MIT (manifest takes precedence; a frontmatter/manifest divergence already seen on this repo in lot 42). MIT licensed per the manifest. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Tailwind CSS 4 patterns is a free Muse skill, a Tailwind CSS 4 styling skill built around a decision tree: class exists, use className; dynamic value, use the style prop; conditional, use cn(); library without class support, use the style prop with var(). It forbids var() or hex colors in className, always semantic Tailwind classes, and defines cn() rules.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit c8036a3Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Tailwind CSS 4 project — the skill is a styling guide the agent follows, not software Install "Tailwind CSS 4 patterns — cn() utility, theme variables, no var() in className" for me. It gives my agent @gentleman-programming's Tailwind 4 rules: the styling decision tree, never var() or hex colors in className (semantic Tailwind classes only), the cn() utility with when-to-use/when-not-to rules, style constants with var() for libraries that can't use className, style props for truly dynamic values, plus flexbox/grid/spacing/typography/states/responsive/dark-mode patterns and the arbitrary-value escape hatch. License note: the skill's frontmatter claims Apache-2.0 but the catalog manifest records MIT — manifest takes precedence. Repository: https://raw.githubusercontent.com/gentleman-programming/gentleman-skills/c8036a37893679dc5e942484975405d39689c63b/curated/tailwind-4/SKILL.md Pinned version: install the code at commit c8036a37893679dc5e942484975405d39689c63b exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "tailwind-4". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (nothing — it's a styling guide the agent applies when writing Tailwind classes). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- c8036a3 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.