Toky CSS is built around three priorities:

Tokens First

Tokens define the design language of a project.

Colors, typography, spacing, layouts, themes, and component decisions should come from reusable tokens rather than hard-coded values scattered throughout a codebase.

Components Second

Components should consume tokens.

A button, card, modal, form field, or navigation item becomes easier to maintain when it relies on shared tokens rather than custom values.

Utilities Last

Utilities are useful, but they should not become the primary way a design system is built.

Toky CSS includes utilities for explicit control when needed while encouraging a token-driven approach for long-term consistency.

Flexibility Over Prescription

Toky CSS provides foundations, not finished designs.

The framework does not attempt to dictate visual style, design systems, branding, layouts, or creative direction.

Instead, it provides a structured foundation that makes those decisions easier to implement and maintain.