time-format-local

Format client-side timestamps with formatDateTimeAbbrev using the active locale.

6|5|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/podverse/podverse --skill time-format-local
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: time-format-local
Source: https://github.com/podverse/podverse/tree/main/.cursor/skills/time-format-local
Command: npx skills add https://github.com/podverse/podverse --skill time-format-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local timestamps often confuse users when their locale or timezone differs. This Skill ensures client-side time displays use formatDateTimeAbbrev for localized, readable timestamps.

Core Features & Use Cases

  • Locale-aware formatting of UI times using formatDateTimeAbbrev from @podverse/helpers.
  • Consistent timestamps across the app by pulling the active locale from useLocale() or next-intl.
  • Use cases include rendering feed times, event times, and chat timestamps to reflect the user’s timezone.

Quick Start

Render all timestamps with formatDateTimeAbbrev using the active locale to ensure readable, localized times in the UI.

Frequently Asked Questions about time-format-local

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

FAQPage Schema
How do I localize timestamps for different locales in my frontend UI?

To localize timestamps in your frontend UI, format client-side dates using the formatDateTimeAbbrev function from @podverse/helpers, pulling the active locale from useLocale() or next-intl to ensure readable, region-specific times.

Why do my UI timestamps show the wrong timezone for international users?

UI timestamps show the wrong timezone when they are not localized to the user's active locale. Applying formatDateTimeAbbrev with the locale from useLocale() or next-intl resolves this by adapting the display to the user's region.

Can I use next-intl to format chat and activity log timestamps?

Yes, you can use next-intl to format chat and activity log timestamps. Retrieve the active locale from next-intl and pass it to the formatDateTimeAbbrev helper to render consistent, localized times across your application.

What is the best way to format feed times consistently across an internationalized app?

The best way to format feed times consistently is to use the formatDateTimeAbbrev function from @podverse/helpers across all UI rendering, supplying the active locale from useLocale() or next-intl to maintain uniform internationalization.

Do I need a specific locale provider to format client-side times?

Yes, you need an active locale from useLocale() or next-intl to format client-side times. This locale is required by formatDateTimeAbbrev from @podverse/helpers to ensure timestamps match the user's region.