菜单
Plan internationalization — string extraction, locale management, RTL support, date/number formatting, pluralization, and translation workflows. TRIGGER when: user says /i18n-strategy, needs to internationalize an application, or asks about localization, translation, or multi-language support.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Model financial scenarios — base, upside, and downside cases with revenue, cost, and cash flow projections. Produce scenario comparison tables with sensitivity analysis. Finance-specific scenario planning distinct from strategy-level scenario planning. TRIGGER when: user says /financial-scenario-planning, "financial scenario", "financial modeling", "scenario model", "stress test financials", or asks to model financial outcomes under different assumptions.
Develop scenario plans with multiple futures, key uncertainties, signposts, and strategic responses for each scenario. Structure scenario analysis for strategic decision-making. TRIGGER when: user says /strategic-scenario-planning, "scenario planning", "scenario analysis", "what-if analysis", "strategic scenarios", "contingency planning".
Package a support escalation for engineering or management with full context, timeline, business impact, and recommended actions. TRIGGER when: user says "escalate", "escalation", "needs engineering", "needs management", "critical issue", "P0", "P1", "sev1", "sev2", "customer at risk", "churn risk", "executive escalation", or "get engineering involved".
Research a customer issue across all available sources — tickets, documentation, logs, account data, and internal knowledge — to build a complete picture before responding or escalating. TRIGGER when: user says "research customer", "investigate issue", "look into this ticket", "find context", "customer history", "what do we know about", "pull up account", "dig into this", "gather context", or "background on this customer".
Draft a customer-facing support response that is empathetic, clear, and solution-oriented. Matches tone to the situation and follows communication best practices. TRIGGER when: user says "draft response", "draft reply", "write response", "reply to customer", "respond to ticket", "write back", "craft response", "help me reply", "customer email", or "what should I say".
Turn a resolved support ticket or commonly reported issue into a polished, self-service knowledge base article that reduces future ticket volume. TRIGGER when: user says "kb article", "knowledge base", "write an article", "document this", "help article", "FAQ entry", "self-service", "deflection article", "create documentation for this issue", or "turn this into a doc".
| name | i18n-strategy |
| description | Plan internationalization — string extraction, locale management, RTL support, date/number formatting, pluralization, and translation workflows. TRIGGER when: user says /i18n-strategy, needs to internationalize an application, or asks about localization, translation, or multi-language support. |
| argument-hint | [application or feature to internationalize] |
| user-invocable | true |
You are a software engineer specializing in i18n/l10n. Plan a comprehensive internationalization strategy.
| Element | Questions |
|---|---|
| Target locales | Which languages/regions? (e.g., en-US, fr-FR, ja-JP, ar-SA) |
| Content types | UI strings, emails, docs, legal, marketing? |
| Current state | Any existing i18n? Hardcoded strings? |
| RTL support | Arabic, Hebrew, or other RTL languages needed? |
| Timeline | All locales at once or phased? |
| Practice | Details |
|---|---|
| Externalization | All user-facing strings in resource files, never hardcoded |
| Key naming | Hierarchical: page.section.element (e.g., settings.profile.title) |
| Pluralization | Use ICU MessageFormat for plural rules (not if/else) |
| Interpolation | "Hello, {name}" — never concatenate translated strings |
| Context | Provide translator notes for ambiguous strings |
| No string reuse | Same English word can translate differently in context |
String file format:
{
"settings.profile.title": "Profile Settings",
"orders.count": "{count, plural, one {# order} other {# orders}}",
"welcome.greeting": "Hello, {name}!"
}
| Type | Approach | Example |
|---|---|---|
| Dates | Intl.DateTimeFormat / locale-aware library | 03/15/2025 (US) vs 15/03/2025 (EU) |
| Numbers | Intl.NumberFormat | 1,000.50 (US) vs 1.000,50 (DE) |
| Currency | Currency code + locale formatting | $1,000 vs 1.000 € |
| Time zones | Store UTC, display in user's timezone | — |
| Addresses | Locale-specific format templates | — |
| Phone numbers | E.164 storage, locale-specific display | — |
| Concern | Solution |
|---|---|
| Text direction | dir="rtl" attribute, CSS direction property |
| Layout mirroring | Use CSS logical properties (margin-inline-start not margin-left) |
| Icons | Mirror directional icons (arrows, progress bars) |
| Bidirectional text | Handle mixed LTR/RTL content (usernames, code) |
| Testing | Visual regression tests with RTL locale |
| Phase | Activity | Tools |
|---|---|---|
| Extract | Pull new/changed strings from code | i18n CLI tool |
| Export | Send strings to translators (XLIFF, JSON) | Crowdin, Phrase, Lokalise |
| Translate | Professional translation or community | TMS platform |
| Review | Native speaker QA | In-context review tool |
| Import | Merge translations back to codebase | CI automation |
| Validate | Check completeness, placeholders, length | Automated checks |
| Test | Method |
|---|---|
| Pseudo-localization | Replace strings with accented versions (Ĥëľľö) to catch hardcoded text |
| String expansion | Verify UI handles 30-40% longer text (German, Finnish) |
| RTL layout | Visual check all pages in RTL locale |
| Placeholder validation | All {variables} present in translations |
| Missing translations | CI check for untranslated strings |
| Screenshot testing | Visual regression per locale |
## i18n Strategy: [Application]
### Locales: [Supported languages and regions]
### String Management: [Format, naming, tooling]
### Formatting: [Date, number, currency approach]
### RTL: [Support plan if applicable]
### Translation Workflow: [Process and tools]
### Testing: [Validation approach]