Nakshora treats CSS the way a language treats words: utilities are vocabulary, tokens are grammar, and components are essays written in that language. The framework’s job is to keep the vocabulary complete, the grammar regular and the essays optional.

Five commitments#

  • One purpose per class — mt-4 does one thing forever; surprises are bugs.
  • Tokens over literals — every value traces to a scale (utility scales), so themes are systematic.
  • '+' composition over inheritance — no cascade magic; classes add, they don’t override-by-mystery.
  • The docs are the spec — if it isn’t documented with an example, it isn’t shipped.
  • Beauty is testable — lookbooks and blueprints (lookbooks & design guides) are reviewed artifacts, not mood boards.

The aesthetic lineage#

v1’s neon glow and glass (2024) taught the framework taste; v3’s parity taught it discipline. Both survive: see design components for the living descendants of the v1 look.

Tip. নকশা means pattern — and the philosophy is simply: trust the pattern. Layout patterns shows what that trust produces.