timezone

Enforce Mountain Time date handling with UTC storage and ISO parsing.

1|Updated Oct 20, 2025

Search Tags:#timezone #getCurrentMountainTime #mountain-time #getMountainISODate #date-time

Ready to run

npx skills add https://github.com/zacjones93/sweet-angel-bakery --skill timezone

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: timezone
Source: https://github.com/zacjones93/sweet-angel-bakery/tree/main/.claude/skills/timezone
Command: npx skills add https://github.com/zacjones93/sweet-angel-bakery --skill timezone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces Mountain Time for all date/time logic to prevent timezone bugs, off-by-one errors, and scheduling issues across the application.

Core Features & Use Cases

Current MT time utility: Use getCurrentMountainTime() to obtain the current Mountain Time in server-side logic.
MT date formatting: Use getMountainISODate() to serialize MT dates as YYYY-MM-DD.
MT date parsing: Use parseMountainISODate() to parse MT midnight dates from strings.
Validation & consistency: All date inputs and cutoffs should be MT-aware, guaranteeing consistent behaviors across regions.

Quick Start

Use Mountain Time utilities to fetch the current MT time and format dates as a MT date string.

Frequently Asked Questions about timezone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent timezone bugs in date/time calculations across different regions?▼

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.

How do I get the current Mountain Time for server-side business logic?▼

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.

What's the best way to format and parse Mountain Time dates as strings?▼

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.

When should I use Mountain Time enforcement instead of storing dates in UTC?▼

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.

Can I use Mountain Time validation with existing input schemas?▼

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.

Why do countdown timers and scheduling features need Mountain Time context?▼

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.