intl

Standardizes locale-aware content and Intl formatting across CMS fields and Astro components.

38|13|Updated Jun 30, 2025
One-click install
npx skills add https://github.com/jhb-software/payload-astro-website-template --skill intl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intl
Source: https://github.com/jhb-software/payload-astro-website-template/tree/main/.claude/skills/intl
Command: npx skills add https://github.com/jhb-software/payload-astro-website-template --skill intl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Internationalization rules ensure CMS fields are localized and all frontend formatting respects user locale, reducing hardcoded strings and locale errors.

Core Features & Use Cases

  • Localized fields in the CMS to ensure translations are stored per locale
  • Web: Labels, translations, and format handling across Astro components
  • Intl formatting: dates, numbers, currencies, and lists via built-in Intl APIs
  • Access localized labels and implement locale-aware display throughout UI

Quick Start

Configure content fields to be localized, and implement locale-aware formatting in your Astro components using the built-in Intl APIs.

Frequently Asked Questions about intl

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

FAQPage Schema
How do I handle multilingual formatting for dates and currencies in Astro components?

Handle multilingual formatting in Astro components by applying built-in Intl APIs for dates, numbers, and currencies. This ensures the display adapts to the current locale state instead of relying on hardcoded values.

What is the best way to localize CMS fields for a multi-language website?

The best way to localize CMS fields for a multi-language website is to configure content fields to be localized. This ensures translations are stored per locale and standardizes locale-aware content across the frontend.

Do I need to manually format localized lists and labels for client-side rendering?

You do not need to manually format localized lists and labels for client-side rendering. The approach uses built-in Intl APIs to automatically adapt list formatting and access localized labels based on the global locale state.

Why does my frontend display hardcoded strings instead of translated text?

Your frontend displays hardcoded strings because text fields are not enforced as localized. Enforcing localized CMS fields and relying on the global locale state for UI labels prevents these locale errors and ensures correct translations.

Can I use built-in Intl APIs for locale-aware formatting without external dependencies?

Yes, you can use built-in Intl APIs for locale-aware formatting without external dependencies. The system relies on these native APIs for date, time, number, currency, and list formatting across your Astro components and CMS fields.