Tailwind Modern

Write Tailwind as Tailwind v4-first by default.

Goal: always produce modern Tailwind syntax, config, and customization patterns. Avoid v3-era patterns unless the repo is clearly pinned to v3 and the task is intentionally legacy.

Default stance

• Prefer Tailwind v4 patterns.
• Prefer CSS-first config over JavaScript config.
• Prefer design tokens in @theme over tailwind.config.js theme extension.
• Prefer @utility over old custom utility patterns.
• Prefer static, detectable class strings.
• Prefer utility classes in markup over custom CSS.
• Use arbitrary values sparingly; promote repeated values into @theme.
• If a repo is on v3, either:
  • keep changes compatible with v3 if asked for a narrow fix, or
  • propose/perform a clean v4 migration.