Tailwind

Workflow

1. Confirm Tailwind version and build integration path (Vite, PostCSS, CLI, framework adapter).
2. Validate content scanning behavior and where classes are discovered.
3. Establish token/theming strategy before scaling component work.
4. Implement utilities first, then extract stable abstractions deliberately.
5. Validate responsive behavior, interaction variants, and accessibility defaults.
6. Measure CSS output and fix scan/safelist mistakes.
7. Apply formatting/linting guardrails for long-term maintainability.
8. Ship with migration notes if upgrading major versions.

Preflight (Ask / Check First)

• Tailwind major version (v3 or v4) and target browser support policy.
• Build toolchain (Vite, webpack, Next.js, custom PostCSS pipeline).
• Monorepo or multi-package content scanning requirements.
• Existing design tokens and whether they are centralized.
• Current pain points: missing styles, class sprawl, inconsistent dark mode, bundle size.
• Required accessibility constraints (contrast, focus indicators, reduced motion).