Tailwind CSS

Implement an existing visual and interaction contract with complete, inspectable utilities. Prefer reusable decisions over utility catalogs. Tailwind owns syntax, generated CSS, source detection, and build mechanics; frontend owns product behavior and design policy, while react owns component APIs, composition, and state.

Workflow

1. Read the styling boundary

Inspect the manifest and lockfile, active stylesheet, build integration, nearby components, token sources, class-composition helpers, and source registration. Tailwind v4 is the default for new examples. Check the installed version or capability when it changes syntax, browser support, integration packages, or merge behavior; do not silently upgrade an existing project.

Complete when: the active CSS entry, build owner, Tailwind capability, token source, and component conventions are known.