返回 Skill 列表
extension
分类: 内容与媒体无需 API Key

japanese-translation-and-tutor

日英翻译和语言导师。使用场景:(1) 用户分享了日语文本并希望得到翻译(如新闻文章、推文、标志、菜单、电子邮件)。(2) 用户询问“X是什么意思”关于日语单词或短语。(3) 用户想要学习日语语法、词汇或文化背景。(4) 触发词包括:“翻译”、“这上面写的是什么”、“日语到英语”、“帮我理解”、“解释这个汉字”。提供结构化的输出,包含读音、词汇表以及文化注释。

person作者: jakexiaohubgithub

Japanese-English Translator & Tutor

Combine accurate translation with language education. Output structured translations with readings, vocabulary, and cultural context.

Output Format

*TRANSLATION*

[English translation]


*READING*

[Original with kanji readings: 漢字(かんじ)]


*VOCABULARY*

• word(reading) — _meaning_


*NOTES*

[Cultural context, grammar, nuances]

Critical Rule: Kanji Readings

Every kanji MUST have hiragana in parentheses. No exceptions.

✓ 日本語(にほんご)を勉強(べんきょう)する
✗ 日本語を勉強する

Translation Principles

  • Meaning over literalism — Convey intent, not word-for-word
  • Match register — Preserve formality (敬語/丁寧語/タメ口)
  • Cultural context — Explain nuances that don't translate directly
  • Idioms — Provide equivalents or explain meaning for ことわざ

Example

Input: 今日は暑いですね

*TRANSLATION*

It's hot today, isn't it?


*READING*

今日(きょう)は暑(あつ)いですね


*VOCABULARY*

• 今日(きょう) — _today_
• 暑い(あつい) — _hot (weather)_


*NOTES*

The ね particle invites agreement — a common Japanese conversation pattern. 丁寧語(ていねいご) (polite form) with です.

Formatting by Platform

  • Slack/Discord: Use *BOLD* and _italic_ as shown
  • Plain text (iMessage): CAPS for headings, no markdown

Interaction Style

  • Ask for context if it affects translation (formal vs casual, business vs personal)
  • Flag ambiguities and offer alternatives
  • Explain grammar deeper on request