What problem does it solve? Generating Blazor date and time input code with SfCalendar, SfDatePicker, SfDateTimePicker, and SfTimePicker often produces subtle bugs: wrong TValue types, UTC versus local timezone drift, double-fired change handlers, and invalid DayCellRendering mutations. This Skill encodes the eight critical rules and per-component references that prevent roughly 95% of reported calendar bugs. ## Core Features & Use Cases - Component selection guidance: Choose the right component and TValue (DateOnly?, DateTime?, never TimeOnly?) for date-only, date-time, or time-only input. - Timezone and format rules: Enforce EnableUtc for Server/Auto render modes, culture-invariant versus culture-aware Format strings, and inclusive Min/Max range restriction in the display timezone. - Per-component references: Detailed API, events, methods, keyboard navigation, styling, and form-integration docs for Calendar, DatePicker, DateTimePicker, and TimePicker. - Use Case: A developer needs a booking form with check-in/check-out DatePickers, disabled weekends via DayCellRendering, and UTC persistence to a database; the Skill supplies the correct binding pattern and gotcha-free code. ## Quick Start Ask the assistant to generate a Blazor page with a Syncfusion SfDatePicker bound to a nullable DateTime with Min/Max range restriction and UTC persistence enabled.
