adapter-tailwind

Files (1)

• SKILL.md

SKILL.md (first lines)

# Adapter: Tailwind CSS

## Focus

- Consistent utility-first styling without ad hoc CSS sprawl.
- Centralized design tokens instead of one-off values.
- Predictable, readable conditional class composition.

## Starter Checklist

- [ ] New styling uses Tailwind utilities, not standalone component CSS, unless global/base-level.
- [ ] Colors/spacing/typography reuse existing design tokens, not raw one-off values.
- [ ] Conditional classes go through the project's class-merge helper, not manual string
      concatenation.

## Implementation Pattern

Evidence: 2-repo field extraction (Tailwind v3 config-based, Tailwind v4 CSS-based) — see
`.ai/MERGE_REPORT.md`.

- Compose conditional/variant class names through one shared helper (commonly `cn()` via
  `clsx` + `tailwind-merge`) in reusable UI primitives; never manually concatenate conditional
  Tailwind strings.
- Define design tokens in exactly one place for the project's Tailwind version — either
  `tailwind.config.*` (v3-style) or CSS custom properties mapped via `@theme` (v4-style). Detect
  which convention the project already uses before adding new tokens; do not introduce the other
  convention alongside it.

If the current project already has an established pattern for either of these, follow the
existing pattern instead of this default.

From JahacksV1/day-one-agent-kit, MIT.

More from JahacksV1/day-one-agent-kit