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

Glass & glassmorphismcard-glass, glass, glass-light, navbar-glass — the v1 frosted surfaces.Neon componentsbtn-neon, card-neon, spinner-neon, neon glow helpers.Brutalist componentsbrutalist-card, brutalist-btn, brutal palettes.Minimalist componentsminimalist-card, minimalist-btn, minimal-ice palette.Neumorphism (neu-*)neu-light soft-extrusion helpers.Skeletonsskeleton-rect, skeleton-circle, skeleton-text — loading shimmer.Buttons (btn-*)btn, btn-neon, btn-glass, btn-brutal, btn-minimal, btn-outline, btn-ghost.Cards (card-*)card, card-glass, card-neon, card-hover.Navigationnavbar-glass, dropdown, accordion, tabs, pagination.Form controlsinput-*, form groups and validation styling.Alerts, badges & progressalert-*, badge-*, progress-* components.Hero sectionshero-* layouts and backgrounds.

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 plugins (addComponents) — or just copy the v1 rules you use.