Compatibility with conviction — the Tailwind parity story

Compatibility is usually a claim. In Nakshora it is a test: a differential oracle compiles identical inputs through both engines and fails CI on *any* byte difference. Parity is a maintained property.

Why bother#

• Ecosystem transfer — every Tailwind 3.4 config, plugin and tutorial works (integrations).
• Hiring reality — teams already speak the grammar; Nakshora adds speed and tooling, not retraining.
• Escape hatches that work — nakshora migrate ports projects in both directions.

Conviction, not imitation#

The grammar is shared; the engine is original: JIT extraction, incremental cache, LSP, CSS-first config. Nakshora speaks the industry’s language with its own accent — see the design philosophy.