What problem does it solve?
Setting up Tailwind CSS 4 for ReactLynx apps built with Rspeedy is tricky: browser-oriented preflight rules, dynamic class names, and unsupported CSS properties silently break or get dropped by the Lynx encoder. This Skill guides you through a correct, verified configuration so utilities actually reach the native Lynx runtime.
Core Features & Use Cases
- Rspeedy Plugin Setup: Configure
pluginLynxTailwindcss() in lynx.config.ts with a theme + utilities CSS entry that avoids browser preflight.
- Static ClassName Guidance: Enforce complete static
className strings or @source inline(...) candidates instead of dynamic string interpolation that Tailwind cannot enumerate.
- Compatibility Triage: Distinguish three levels—Tailwind generated, Lynx encoder accepted, and runtime verified—using the compatibility matrix for logical properties, pseudo-classes, gradients, and arbitrary values.
- Use Case: You are building a ReactLynx app and your
padding-inline utilities disappear from the bundle. This Skill explains the encoder limitation and directs you to physical-direction properties plus real-device verification steps.
Quick Start
Use the weapp-tailwindcss-lynx skill to configure Tailwind CSS 4 in my ReactLynx Rspeedy project and verify the generated bundle on device.