avalonia-pro-max/design-system

To set up a design token system in Avalonia, centralize Primitive, Semantic, and Component tokens into ResourceDictionarys merged via ThemeDictionaries in App.axaml. This enables dynamic resource lookups for runtime Light and Dark theme switching.

The best way to ensure typography and spacing consistency is to define scalable design tokens for fonts, spacing, radii, and elevation. Centralizing these tokens reduces visual drift and eliminates repetitive manual styling across your application views.

Runtime Light and Dark theme switching in Avalonia is achieved by storing token variants in ThemeDictionaries. Views reference these tokens using DynamicResource, allowing the application to update surfaces and typography instantly when the theme changes.

Yes, you can use a three-layer token model in Avalonia by structuring resources into Primitive, Semantic, and Component tokens. This layered architecture allows you to scale UI components efficiently while maintaining a strict design system identity.

No, you do not need to manually style surfaces and component visuals. By referencing centralized design tokens via DynamicResource in your views, the theming logic automatically applies consistent styles across your Avalonia application.