skills/tailwind-patterns/SKILL.md
Tailwind CSS v4 design decisions. Use when: Tailwind, utility-first, container query, design tokens, dark mode strategy.
npx skillsauth add thkt/dotclaude tailwind-patternsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Design-level decisions that linters cannot catch.
| Topic | Key Point |
| -------------------- | -------------------------------------------------------------- |
| Container Query | Reusable component → @container, page layout → viewport |
| Color Token | Primitive + Semantic minimum. Arbitrary values = missing token |
| Dark Mode | v4: @custom-variant in CSS, no darkMode config key |
| Layout Selection | flex (1-axis), grid (2D), grid+spans (Bento) |
| Component Extraction | Same class combo 3+ times → extract. No @apply in v4 |
| Anti-Patterns | No dynamic class strings, no !important, no arbitrary values |
| v4 CSS-First Config | @theme in CSS replaces tailwind.config.js |
→ Details: Container Query, Color Token, Dark Mode, Layout, Component Extraction, Anti-Patterns, v4 Config
tools
Delegate implementation to codex (coder) via the herdr-agentchat plugin and drive a two-pane conversation to completion.
development
Extract recurring patterns from past closed PRs/issues and the research findings in workspace/research/, verify them against the latest code, and propose them to docs/wiki/ via PR.
development
Create Decision Records (DR) in MADR v4 format with auto-numbering.
development
Detect flaky tests by shaking them — repeated runs under varied order, parallelism, and seed — plus a static smell scan that flags latent flakiness in tests that currently pass. Classify each target as confirmed-flaky, latent-flaky, or stable and fix the root cause without weakening the test. Do NOT use to fix a confirmed single bug (use /fix) or for static-only code review (use /audit).