Principles
How TailNG is designed
A design system should enable teams, not constrain them.
1) Tokens over colors
Templates should not hard-code brand colors. TailNG promotes semantic tokens (bg, fg, border, primary, etc.) so themes can evolve without refactoring UI markup.
2) Styling-first composition
TailNG does not force one styling approach. Use plain CSS, Tailwind utilities, or your own design system tokens. Components avoid hidden layout rules, so you can compose UI with predictable primitives and local styling.
3) Angular-first implementation
Standalone components and signal inputs by default. No legacy module patterns. Minimal runtime work, good tree-shaking, and predictable usage.
4) No lock-in
TailNG is just Angular components + Tailwind utilities + CSS variables. You can adopt gradually and exit cleanly.