Tailwind Style Guidelines

PureChatNext Tailwind-first styling

Use this skill when creating a React component or changing its styles in PureChatNext.

Required decisions

• New components default to Tailwind CSS classes.
• Do not add createStaticStyles for a few simple static declarations such as layout, spacing, color, border, radius, or basic responsive rules.
• Keep createStaticStyles when the style is genuinely complex or dynamic: multiple selectors/states, container queries, keyframes, SVG animation, custom scrollbar geometry, calculated values, or shared UI bridge behavior.
• Prefer semantic theme variables and existing @pure/ui; do not introduce another styling library.
• Do not migrate @pure/ui internals as part of an unrelated business component change.
• If an exception is retained, leave a short reason near the style definition.

Workflow

1. Read the style guidelines for component-level rules.
2. Read the migration guide when converting existing createStaticStyles code.
3. Prefer the smallest change that keeps class names readable and preserves theme, responsive, and interaction behavior.
4. Remove unused antd-style imports, style constants, and test mocks after a successful simple-style migration.
5. Run targeted ESLint and pnpm exec tsc --noEmit when the change is complete.

Do not treat zero remaining createStaticStyles usages as the goal. The goal is that new code is Tailwind-first and remaining CSS-in-JS has a concrete complexity or public-component reason.