# Pc Internationalization

> Use when user-facing text, locale-sensitive formatting, or multi-language behavior need explicit rules so copy, layout, and data presentation stay correct across locales.

- Skill: `yknothing/pc-internationalization` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add yknothing/pc-internationalization`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yknothing/pc-internationalization/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: yknothing (https://skillmd.com/u/yknothing)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/yknothing/pc-internationalization

---


# Internationalization

> Treat locale behavior as a system contract, not as a late translation task.

## Context

Use this skill when the work introduces or changes user-facing text, date and number formatting, pluralization, locale selection, or language fallback behavior.

See [context](references/context.md) and [anti-pattern](references/anti-patterns.md) notes.

## Inputs

[I/O contract notes](references/io-contract.md) define required inputs and authority.

## Process

### Step 1: Define the locale surface

Identify all strings, formats, and locale decisions touched by the change.

### Step 2: Make fallback rules explicit

Document what happens when a translation is missing, a locale is unsupported, or layout expands because text length changes.

### Step 3: Capture formatting requirements

Record how dates, times, numbers, currency, and plural rules must behave.

### Step 4: Turn requirements into review checks

Describe what implementation and QA must verify before release.

## Outputs

Produce only declared outputs at their documented quality boundary.

## Quality Gate

- [ ] Affected user-facing strings and locale-sensitive formats are identified
- [ ] Fallback behavior is explicit
- [ ] Reviewers can verify locale behavior without inventing policy during QA