skills.rest
mykaarma
mykaarmaOFFICIAL
Explore all skills by this author →
WebsiteGitHub

localization-guidelines

Enforce attribute-based localization standards for UI and code artifacts.

Updated Aug 27, 2026
Search Tags:#localization#i18n#rtl#date-formatting#ui-guidelines#currency-formatting#locale-attributes
One-click install
npx skills add https://github.com/mykaarma/claude-sutras --skill localization-guidelines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: localization-guidelines
Source: https://github.com/mykaarma/claude-sutras/tree/main/skills/localization-guidelines
Command: npx skills add https://github.com/mykaarma/claude-sutras --skill localization-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear, actionable standard for building locale-aware UI and services so teams avoid hardcoded locale checks, layout breakage in right-to-left markets, and inconsistent currency/date/unit formatting across dealer and customer experiences.

Core Features & Use Cases

  • Attribute-driven rules: Emphasizes checking localeAttributes (textDirection, currency, units, date/time patterns) instead of branching on locale strings to future-proof code.
  • Layout & formatting guidance: Specifies logical layout properties, icon mirroring rules, and UI responsibility for formatting numbers, currencies, dates, and distances.
  • API reference & resolution: Directs teams to the dealer locale attributes API and defines resolution/fallback chains for dealer, advisor, and customer scenarios.
  • Use case: Audit a checkout component to ensure RTL flipping, correct currency symbol/placement, and date/time patterns are driven by dealer locale attributes.

Quick Start

Use the localization-guidelines skill to audit a UI component for RTL layout, currency placement, and date/time formatting against the localeAttributes API.

Frequently Asked Questions about localization-guidelines

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

FAQPage Schema
How do I implement right-to-left layouts without hardcoding locale checks?▼

To implement right-to-left layouts safely, use attribute-driven rules that check localeAttributes like textDirection instead of branching on locale strings. This approach future-proofs code and prevents layout breakage in RTL markets.

What is the best way to format currency and dates for different dealer locales?▼

The best way to format currency and dates is to keep formatting responsibilities in the UI layer and drive them using the dealer locale attributes API. This ensures consistent currency symbol placement and date/time patterns across interfaces.

How do I audit a UI component for i18n and RTL compliance?▼

To audit a UI component for i18n compliance, validate its use of the localeAttributes API, check logical layout properties, verify icon mirroring rules, and ensure number, currency, and date formatting is correctly delegated to the UI layer.

Does this localization approach work for both backend and frontend implementations?▼

Yes, this localization approach targets both frontend and backend developers. It enforces attribute-based standards for UI artifacts and defines resolution and fallback chains for dealer, advisor, and customer scenarios across both environments.

Why does my UI layout break in right-to-left markets?▼

UI layout breaks in right-to-left markets when developers use hardcoded locale checks instead of logical layout properties. Checking localeAttributes like textDirection and following icon mirroring rules resolves this layout breakage.

When do I need locale-aware formatting for distance and unit displays?▼

You need locale-aware formatting for distance and unit displays whenever building dealer and customer interfaces across different markets. The localeAttributes API provides the necessary unit patterns to ensure correct regional formatting.

Related Skills

Explore More Software Engineering Skills→
fabioc-alohafabioc-aloha
1

localization

Implements internationalization and localization patterns for multilingual software applications.

Community
Advanced
pratikrath126pratikrath126
42

i18n-localization

Detect hardcoded strings and validate locale files across React, Next.js, and Python projects.

Community
Intermediate
lexlerlexler
225

hexagonal-architecture

Define Domain, Application, and Adapter boundaries with ports and adapters.

Community
Basic
AbdullahmohammadarefAbdullahmohammadaref

i18n

Integrate next-intl or react-i18next for locale-aware text and formatting.

Community
Advanced