yknothing 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 and anti-pattern notes.
Inputs
I/O contract notes 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