timezone-santiago

Enforce Santiago timezone for all user-visible dates and timestamps.

Updated Nov 25, 2025
One-click install
npx skills add https://github.com/filimorniga-ux/farmacias-vallenar-suit --skill timezone-santiago
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: timezone-santiago
Source: https://github.com/filimorniga-ux/farmacias-vallenar-suit/tree/main/.agent/skills/timezone-santiago
Command: npx skills add https://github.com/filimorniga-ux/farmacias-vallenar-suit --skill timezone-santiago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill ensures that every user-facing date and time in the application reliably reflects local Chile time (America/Santiago) including daylight saving transitions, preventing reporting errors, misplaced sales by day, and confusion in tickets, exports and attendance records while keeping internal storage in UTC.

Core Features & Use Cases

  • Centralized TIMEZONE constant to avoid scattered timezone strings and accidental misuse.
  • Formatting helpers for full datetime, date-only, and time-only displays using Intl.DateTimeFormat or date-fns-tz where available.
  • Database guidance to store timestamps as TIMESTAMPTZ in UTC and convert with AT TIME ZONE for grouping, ranges and TimeScaleDB continuous aggregates.
  • Deployment and environment recommendations (TZ env, Docker, Vercel) plus a validation checklist to verify UI, tickets, exports, logs and reports use Santiago time.
  • Use Case: Generate daily sales reports and POS receipts that correctly group late-night Chile sales into the intended Chilean date despite UTC offsets.

Quick Start

Use the timezone-santiago skill to convert and format all display dates to America/Santiago before rendering user interfaces, tickets, or exported files.

Frequently Asked Questions about timezone-santiago

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

FAQPage Schema
How do I enforce the America/Santiago timezone globally across my web UI and database?▼

To enforce the America/Santiago timezone globally, use a centralized TIMEZONE constant for UI formatting with Intl.DateTimeFormat or date-fns-tz, store timestamps as TIMESTAMPTZ in UTC, and apply AT TIME ZONE conversions in your SQL queries.

Why do my daily sales reports group late-night Chilean transactions into the wrong date?▼

Daily sales reports group transactions incorrectly when UTC offsets shift late-night Chilean sales across date boundaries. Converting TIMESTAMPTZ storage to America/Santiago using AT TIME ZONE before grouping fixes the report boundaries.

Does TimescaleDB support continuous aggregates with timezone-aware conversions for Chile?▼

Yes, TimescaleDB continuous aggregates support timezone-aware conversions. You can store base data as TIMESTAMPTZ in UTC and apply the AT TIME ZONE 'America/Santiago' conversion during aggregation to respect Chilean daylight saving transitions.

What is the best way to configure timezone settings for deployments in Chile?▼

The best way to configure deployments for Chile is setting the TZ environment variable to America/Santiago across your infrastructure, such as Docker or Vercel environments, ensuring server-side exports and PDF reports reflect local time.

Can I use date-fns-tz to format timestamps for POS tickets in Chilean deployments?▼

Yes, you can use date-fns-tz to format timestamps for POS tickets. By applying a centralized TIMEZONE constant set to America/Santiago, date-fns-tz ensures receipts display full datetime, date-only, and time-only values in local Chile time.

When should I not use UTC storage for datetime values in an application deployed in Chile?▼

You should not avoid UTC storage. Keep timestamps as TIMESTAMPTZ in UTC internally to maintain data integrity, and only apply the America/Santiago timezone conversion at the presentation layer for UI, exports, and attendance logs.