Skip to content
Ritesh FirodiyaGet in touch

Work / Chitragupt / Wiki / Decisions

2026-05-30-foundational-mobile-uniwind-website-tailwind

Decisioncanonicalverified 2026-06-26

DECISION.2026-05-30.FOUNDATIONAL-MOBILE-UNIWIND-WEBSITE-TAILWIND

Mobile styling = Uniwind; Website styling = Tailwind v4

Note: Date 2026-05-30 is a placeholder — the decision predates the log.

Decision

Mobile uses Uniwind (Tailwind v4 for React Native). Website uses Tailwind v4. Both share the Tailwind class vocabulary; component code stays consistent.

Why

A shared class vocabulary keeps mobile and website components legible to the same developer. Avoids two style systems.

Impact

  • className= is the only styling primitive on both apps.
  • No StyleSheet.create and no inline style={} for static styles on mobile.
  • No uniwind import on website.
  • Enforcement lives in .claude/rules/mobile.md and .claude/rules/frontend.md.

Status

Active.

Sources

  • .context/wiki/decisions/* § "(foundational, undated) — Mobile styling = Uniwind; Website styling = Tailwind v4"

Every project of mine is written down like this.

Read the résumé