timezone

Timezone bugs occur when applications use local time instead of a consistent reference. This Skill enforces Mountain Time for all date/time logic, eliminating off-by-one errors and scheduling inconsistencies by standardizing how dates are parsed, formatted, and stored across your codebase.

Use getCurrentMountainTime() to retrieve the current time in Mountain Time for server-side operations. This utility replaces new Date() for business logic, ensuring all date calculations, scheduling decisions, and API serialization use consistent Mountain Time context rather than the system's local timezone.

Use getMountainISODate() to serialize dates as YYYY-MM-DD Mountain Time strings, and parseMountainISODate() to parse those strings back into Mountain Time midnight dates. This ensures consistent bidirectional conversion while maintaining timezone awareness throughout your application.

Store timestamps in UTC for database persistence, but enforce Mountain Time when performing date/time calculations, scheduling deliveries, setting content activation cutoffs, filtering calendar events, or validating HTML date inputs. This separates storage (UTC) from business logic (Mountain Time) while preventing timezone conversion errors.

Yes. Validate Mountain Time date inputs using Zod schemas alongside this Skill's parsing utilities. This approach catches invalid dates early, ensures all inputs conform to Mountain Time context, and provides consistent error handling across API endpoints, form submissions, and internal date operations.

Countdown timers and scheduling rely on precise time deltas; misaligned timezones cause pickups scheduled for the wrong hour, content activating off-cycle, or cutoff deadlines missed by regions. Mountain Time enforcement ensures all time-dependent features trigger at the correct Mountain Time boundary regardless of where the code runs.