Nakshora's signature idea: frameworks should ship design paradigms, not just primitives. Nakshora 3.1 gives you complete visual languages as classes:

Glass (.glass, .glass-light, .glass-dark)Backdrop-blurred frosted surfaces in three densities.Neon (.neon-card, .neon-btn, .neon-glow, .neon-text)The neon-cyber component family: glows, borders and text.Brutalist (.brutalist-card, .brutalist-btn)Hard shadows, thick borders, flat color.Minimalist (.minimalist-card, .minimalist-btn)Hairline borders and whitespace-first design.Skeletons (.skeleton-rect, .skeleton-circle, .skeleton-text)Loading shimmer states for every shape.Helpers (.hover-lift, .gradient-*)hover-lift, gradient-text, gradient-neon, gradient-pastel, gradient-nature, gradient-brutalist.

Components vs utilities#

Components are *opinions*; utilities are *vocabulary*. Start from a component for speed, then override with utilities when the design demands it. Because components are plain CSS classes, every utility composes with them:

html
<div class="glass p-8 rounded-2xl max-w-md mx-auto mt-20">
  <!-- component for the paradigm, utilities for placement & sizing -->
</div>
Tip. Want these paradigms in your own components? Extract them with configuration/plugins|plugins (addComponents).