What problem does it solve?
This guide helps teams generate StyleSet definitions for new components that align with the v2.0.0+ conventions, ensuring consistent typing, CSS variable exposure, and scalable design patterns across the codebase.
Core Features & Use Cases
- Conventional Type Systems: Extend CSSProperties to define a typed StyleSet, including root properties and nested sub-objects for slots, elements, and child components.
- Structured Naming: Enforces clear, semantic names for
$X primitives and nested StyleSets to avoid ambiguity.
- Incremental Adoption: Supports gradual adoption by combining root CSSProperties with optional
$X objects and child StyleSets, without breaking existing components.
- Use Case: When designing a new VsCard, you can declare $header, $body, and $footer sub-StyleSets to centrally control layout, spacing, and theming while keeping the root API stable.
Quick Start
Provide a guided, interactive workflow to generate a Vs<ComponentName>StyleSet that adheres to the v2 conventions.