i18n-and-timezones

What problem does it solve?

AI coding agents consistently produce broken internationalization and time zone implementations in Ruby on Rails applications, commonly hardcoding user-facing strings, misusing time APIs that ignore server versus user time zones, failing to handle daylight saving time edge cases, and skipping required locale fallback configuration.

Core Features & Use Cases

• Correct I18n implementation: Guides proper externalization of user-facing strings, lazy view lookup, locale fallback setup, and rails-i18n gem integration for multi-language Rails apps.
• Safe time zone handling: Enforces UTC storage for all database timestamps, per-request user time zone switching, and proper use of Time.current instead of server-local Time.now.
• DST edge case mitigation: Provides patterns to avoid bugs from daylight saving time transitions, including DST-safe date math and strategies for appointment booking use cases. For example, when building a multi-language appointment scheduling app, this Skill ensures all interface strings are translatable, appointment times are stored correctly in UTC, and DST transition gaps don't break booking availability.

Quick Start

Use this Skill to implement proper internationalization and time zone handling for your Rails application when adding multi-language support or resolving existing time-related bugs.