write-a-localization-brief
Write a localization brief that defines audience, market, purpose, source version, terminology, context, constraints, formats, review, and delivery evidence. Use when translators and localizers need enough information to produce accurate usable content.
ソース情報
- リポジトリ
- protosphinx/sphinxstack
- ソースの最終更新活動
- 2026年7月29日 13:55
- 検出された SKILL.md の言語
- 英語
- スター
- 3
- フォーク
- 0
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
ファイルエクスプローラー
2 ファイルSKILL.md を表示中
SKILL.md
ソースの指示 · 読み取り専用プレビュー- name
- write-a-localization-brief
- category
- write
- description
- Write a localization brief that defines audience, market, purpose, source version, terminology, context, constraints, formats, review, and delivery evidence. Use when translators and localizers need enough information to produce accurate usable content.
# write-a-localization-brief
Provide context and decision rules, not only source strings.
## When to use
- Use for product, website, support, policy, campaign, media, legal, or technical localization.
- Do not expose unnecessary personal, customer, security, or pre-release information.
## Procedure
1. Identify project, source version, content owner, target locales, markets, audience, purpose, and release date.
2. Describe channel, user journey, screenshots, character limits, variables, plural, gender, tone, and accessibility.
3. Provide approved terminology, do-not-translate list, product names, references, examples, pronunciation, and prior translations.
4. Explain legal, regulatory, cultural, safety, privacy, date, number, currency, address, and measurement constraints.
5. Define file format, encoding, tags, placeholders, layout, right-to-left, font, subtitle, or voice requirements.
6. Set translator, reviewer, in-market, legal, technical, and final approval roles.
7. Specify query, version, change, quality, testing, delivery, and correction workflows.
8. Package source, references, access, deadlines, and acceptance criteria; verify recipients can open them safely.
## Done
- A localization brief documents source, locales, audiences, context, terminology, constraints, files, roles, testing, and acceptance
- Version, placeholder, terminology, market, accessibility, format, security, reviewer, query, and package-access checks verify readiness
GitHubで見る