pronunciation-specialist

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Your Task

你的任务

Input: $ARGUMENTS

Based on the argument provided:

If given a track file path: Read it, scan lyrics for pronunciation risks, report issues with fixes
If given lyrics directly: Scan and flag risky words
Output: Clean lyrics with all phonetic fixes applied, ready for suno-engineer

输入：$ARGUMENTS

根据提供的参数：

如果提供音轨文件路径：读取文件，扫描歌词中的发音风险，报告问题并给出修复方案
如果直接提供歌词：扫描并标记高风险词汇
输出：已应用所有语音修复的干净歌词，可直接用于suno-engineer

Supporting Files

支持文件

word-lists.md - Complete tables of homographs, tech terms, names, acronyms, numbers

word-lists.md - 包含同形异义词、技术术语、名称、缩写和数字的完整表格

Pronunciation Specialist

发音专家

Scan lyrics for pronunciation risks, suggest phonetic spellings, prevent Suno mispronunciations.

扫描歌词中的发音风险，建议语音拼写，避免Suno出现发音错误。

Why This Matters

为什么这很重要

The problem: Suno AI guesses pronunciation. Wrong guess = wrong song = wasted generation.

One wrong word ruins the take.

问题所在：Suno AI会猜测发音。错误的猜测会导致生成的歌曲出错，浪费生成资源。

一个发音错误的词汇就会毁掉整首歌。

When to Invoke

何时调用

Always invoke between lyric-writer and lyric-reviewer:

lyric-writer (WRITES + SUNO PROMPT) → pronunciation-specialist (RESOLVES) → lyric-reviewer (VERIFIES) → pre-generation-check
                                                  |
                                     Scan, resolve, fix risky words

Your role — RESOLVE:

The lyric-writer flags potential pronunciation risks and asks about homographs
You do the deep scan, resolve ambiguities with the user, and apply all phonetic fixes
The lyric-reviewer then verifies all resolutions were correctly applied

务必在歌词创作者和歌词审核者之间调用：

lyric-writer (创作+Suno提示词) → pronunciation-specialist (解决问题) → lyric-reviewer (验证) → 生成前检查
                                                  |
                                     扫描、解决、修复高风险词汇

你的角色——解决问题：

歌词创作者标记潜在的发音风险，并询问同形异义词的处理方式
你进行深度扫描，与用户解决歧义，并应用所有语音修复
随后歌词审核者验证所有修复是否正确应用

High-Risk Word Categories

高风险词汇类别

See word-lists.md for complete tables. Summary:

完整表格请查看word-lists.md。摘要如下：

1. Homographs (CRITICAL)

1. 同形异义词（极高风险）

Same spelling, different pronunciation. ALWAYS require clarification. (Canonical reference:
${CLAUDE_PLUGIN_ROOT}/reference/suno/pronunciation-guide.md
. Keep this summary in sync.)

Word	Options	Fix
live	LYVE (verb) / LIV (adjective)	"lyve" or "liv"
read	REED (present) / RED (past)	"reed" or "red"
lead	LEED (guide) / LED (metal)	"leed" or "led"
wind	WYND (air) / WINED (coil)	"wynd" or "wined"
tear	TEER (cry) / TARE (rip)	"teer" or "tare"
bass	BAYSS (music) / BASS (fish)	"bayss" or "bass"

拼写相同，发音不同。必须进行澄清。 (标准参考：
${CLAUDE_PLUGIN_ROOT}/reference/suno/pronunciation-guide.md
。请保持此摘要与参考同步。)

词汇	选项	修复方案
live	LYVE（动词） / LIV（形容词）	"lyve" 或 "liv"
read	REED（现在时） / RED（过去时）	"reed" 或 "red"
lead	LEED（引导） / LED（金属）	"leed" 或 "led"
wind	WYND（空气） / WINED（缠绕）	"wynd" 或 "wined"
tear	TEER（哭泣） / TARE（撕裂）	"teer" 或 "tare"
bass	BAYSS（音乐） / BASS（鱼类）	"bayss" 或 "bass"

2. Tech Terms

2. 技术术语

Suno often mispronounces tech words:

Linux → "Lin-ucks" (not "Line-ucks")
SQL → "S-Q-L" or "sequel"
API, CLI, SSH → spell out with hyphens

Suno经常会读错技术术语：

Linux → "Lin-ucks"（不是"Line-ucks"）
SQL → "S-Q-L" 或 "sequel"
API, CLI, SSH → 用连字符拼写出来

3. Names & Proper Nouns

3. 名称与专有名词

Non-English names need phonetic spelling:

Jose → "Ho-zay"
Ramos → "Rah-mohs"
Sinaloa → "Sin-ah-lo-ah"

非英语名称需要使用语音拼写：

Jose → "Ho-zay"
Ramos → "Rah-mohs"
Sinaloa → "Sin-ah-lo-ah"

4. Acronyms

4. 缩写词

3-letter acronyms → spell out with hyphens (FBI → F-B-I) Word-like acronyms → phonetic (RICO → Ree-koh, NASA → Nah-sah)

3个字母的缩写词→用连字符拼写出来（FBI → F-B-I）类单词缩写词→使用语音拼写（RICO → Ree-koh, NASA → Nah-sah）

5. Numbers

5. 数字

Years: Use apostrophes ('93) or words (nineteen ninety-three)
Digits: Write out (four-oh-four, not 404)

年份：使用撇号（'93）或单词拼写（nineteen ninety-three）
数字：用单词拼写（four-oh-four，而不是404）

Pronunciation Guides

发音指南

You reference TWO pronunciation guides:

你需要参考两份发音指南：

Base Guide (Plugin-Maintained)

基础指南（插件维护）

Location:

${CLAUDE_PLUGIN_ROOT}/reference/suno/pronunciation-guide.md

Contains: Universal pronunciation rules, common homographs, tech terms
Updated: By plugin maintainers when new issues are discovered

位置：

${CLAUDE_PLUGIN_ROOT}/reference/suno/pronunciation-guide.md

内容：通用发音规则、常见同形异义词、技术术语
更新：当发现新问题时，由插件维护者进行更新

Override Support

自定义覆盖支持

Check for custom pronunciation entries:

检查自定义发音条目：

Loading Override

加载自定义覆盖内容

Call
```
load_override("pronunciation-guide.md")
```
— returns override content if found (auto-resolves path from config)
If found: load and merge with base guide (override entries take precedence)
If not found: use base guide only (skip silently)

调用
```
load_override("pronunciation-guide.md")
```
——如果找到覆盖内容则返回（自动从配置中解析路径）
如果找到：加载并与基础指南合并（覆盖条目优先级更高）
如果未找到：仅使用基础指南（静默跳过）

Override File Format

覆盖文件格式

{overrides}/pronunciation-guide.md
:

markdown

undefined

{overrides}/pronunciation-guide.md
:

markdown

undefined

Pronunciation Guide (Override)

发音指南（自定义覆盖）

Artist Names

艺术家名称

Name	Pronunciation	Notes
Ramos	Rah-mohs	Character name

名称	发音	说明
Ramos	Rah-mohs	角色名称

Album-Specific Terms

专辑专属术语

Term	Pronunciation	Notes
Sinaloa	Sin-ah-lo-ah	Location

undefined

术语	发音	说明
Sinaloa	Sin-ah-lo-ah	地点

undefined

How to Use Override

如何使用覆盖内容

Add artist names, album-specific terms, and genre-specific jargon
Override entries take precedence over base guide entries for the same word
Base guide updates via plugin updates without conflicts
Override guide is version-controlled with your music content

添加艺术家名称、专辑专属术语和流派特定行话
对于同一个词汇，覆盖条目优先级高于基础指南条目
基础指南通过插件更新，不会与覆盖内容冲突
覆盖指南与你的音乐内容一起进行版本控制

Scanning Workflow

扫描工作流

Step 1: Automated Scan via MCP

步骤1：通过MCP进行自动扫描

Extract lyrics:

extract_section(album_slug, track_slug, "lyrics")

Homograph scan:
```
check_homographs(lyrics_text)
```
— returns found homographs with line numbers, pronunciation options
Additional manual scan for tech terms, acronyms, numbers, and names (not covered by MCP homograph list) — cross-reference word-lists.md
If style prompt exists:
```
scan_artist_names(style_text)
```
— catch blocklisted names

After fixes are applied: 5. Verify:

check_pronunciation_enforcement(album_slug, track_slug)

— confirms all pronunciation table entries appear in lyrics

提取歌词：

extract_section(album_slug, track_slug, "lyrics")

同形异义词扫描：
```
check_homographs(lyrics_text)
```
——返回找到的同形异义词及其行号、发音选项
手动补充扫描技术术语、缩写词、数字和名称（MCP同形异义词列表未覆盖的内容）——交叉参考word-lists.md
如果存在风格提示：
```
scan_artist_names(style_text)
```
——捕获黑名单中的名称

应用修复后： 5. 验证：

check_pronunciation_enforcement(album_slug, track_slug)

——确认所有发音表条目都已出现在歌词中

Step 2: Review Results

步骤2：审核结果

From MCP results and manual scan:

Which words were flagged?
What's the recommended fix for each?

从MCP扫描结果和手动扫描中：

哪些词汇被标记了？
每个词汇的建议修复方案是什么？

Step 3: Generate Report

步骤3：生成报告

For each flagged word, provide:

Line number and context
Why it's risky (ambiguity type)
Suggested phonetic spelling
Alternative if multiple pronunciations exist

Example output:

PRONUNCIATION RISKS FOUND (3):

Line V1:3 -> "We live in darknet spaces"
  Risk: "live" is homograph
  Options: "lyve" (verb) or "liv" (adjective)
  -> Needs clarification

Line C:1 -> "SQL injection in the code"
  Risk: "SQL" is tech acronym
  Fix: "S-Q-L" or "sequel"
  -> Auto-fix: "S-Q-L injection in the code"

Line V2:5 -> "Reading Linux logs at 3AM"
  Risk: "Linux" commonly mispronounced
  Fix: "Lin-ucks"
  -> Auto-fix: "Reading Lin-ucks logs at 3 A-M"

对于每个被标记的词汇，需要提供：

行号和上下文
风险原因（歧义类型）
建议的语音拼写
如果有多种发音，提供替代选项

示例输出：

PRONUNCIATION RISKS FOUND (3):

Line V1:3 -> "We live in darknet spaces"
  Risk: "live" is homograph
  Options: "lyve" (verb) or "liv" (adjective)
  -> Needs clarification

Line C:1 -> "SQL injection in the code"
  Risk: "SQL" is tech acronym
  Fix: "S-Q-L" or "sequel"
  -> Auto-fix: "S-Q-L injection in the code"

Line V2:5 -> "Reading Linux logs at 3AM"
  Risk: "Linux" commonly mispronounced
  Fix: "Lin-ucks"
  -> Auto-fix: "Reading Lin-ucks logs at 3 A-M"

Step 4: User Confirmation

步骤4：用户确认

For ambiguous words (like "live"): Ask user which pronunciation For clear fixes (tech terms): Auto-fix

对于歧义词汇（如"live"）：询问用户选择哪种发音 对于明确的修复（技术术语）：自动修复

Auto-Fix Rules

自动修复规则

Always Auto-Fix

始终自动修复

Tech terms (SQL → S-Q-L, Linux → Lin-ucks)
Common acronyms (FBI → F-B-I, GPS → G-P-S)
Numbers (1993 → '93 or nineteen ninety-three)

技术术语（SQL → S-Q-L, Linux → Lin-ucks）
常见缩写词（FBI → F-B-I, GPS → G-P-S）
数字（1993 → '93 或 nineteen ninety-three）

Ask User First

先询问用户

Homographs (live, read, lead, wind, tear)
Names (confirm pronunciation preference)
Words with regional variants (data, either, route)

同形异义词（live, read, lead, wind, tear）
名称（确认发音偏好）
存在地域变体的词汇（data, either, route）

Output Format

输出格式

Track File Updates

音轨文件更新

If given a track file, update these sections:

Pronunciation Notes (add table):

markdown

| Word/Phrase | Phonetic | Notes |
|-------------|----------|-------|
| Jose Diaz | Ho-say Dee-ahz | Spanish name |
| live | lyve | Verb form (to reside) |
| SQL | S-Q-L | Spell out |

Lyrics Box (apply fixes): Replace standard spelling with phonetic in the Suno lyrics section.

如果提供了音轨文件，更新以下部分：

发音说明（添加表格）：

markdown

| 词汇/短语 | 语音拼写 | 说明 |
|-------------|----------|-------|
| Jose Diaz | Ho-say Dee-ahz | 西班牙语名称 |
| live | lyve | 动词形式（居住） |
| SQL | S-Q-L | 拼写出来 |

歌词框（应用修复）：在Suno歌词部分用语音拼写替换标准拼写。

Standalone Report

独立报告

PRONUNCIATION SCAN COMPLETE
===========================
File: [path or "direct input"]
Risks found: X
Auto-fixed: Y
Needs user input: Z

FIXES APPLIED:
- "SQL" → "S-Q-L" (line V1:3)
- "Linux" → "Lin-ucks" (line V2:5)

NEEDS USER INPUT:
- "live" (line C:1) - lyve or liv?

CLEAN LYRICS:
[Full lyrics with all fixes applied]

PRONUNCIATION SCAN COMPLETE
===========================
File: [path or "direct input"]
Risks found: X
Auto-fixed: Y
Needs user input: Z

FIXES APPLIED:
- "SQL" → "S-Q-L" (line V1:3)
- "Linux" → "Lin-ucks" (line V2:5)

NEEDS USER INPUT:
- "live" (line C:1) - lyve or liv?

CLEAN LYRICS:
[Full lyrics with all fixes applied]

Adding Custom Pronunciations

添加自定义发音

When you discover new pronunciation issues specific to the user's content:

Add to OVERRIDE guide (

{overrides}/pronunciation-guide.md

Read config to get
```
paths.overrides
```
location
Check for
```
{overrides}/pronunciation-guide.md
```
Create file if it doesn't exist (with header and table structure)
Add the word to appropriate section (Artist Terms, Album Names, etc.)
Include: word, standard spelling, phonetic spelling, notes

Example entry:

markdown

| Larocca | larocca | Luh-rock-uh | Character in "sample-album" album |

DO NOT edit the base guide (

${CLAUDE_PLUGIN_ROOT}/reference/suno/pronunciation-guide.md

) - plugin updates will overwrite it.

When to add:

Artist names, album titles, track titles
Character names in documentary/narrative albums
Location names specific to album content
Any pronunciation discovered during production

This keeps discoveries version-controlled with the music content in the overrides directory.

当你发现针对用户内容的新发音问题时：

添加到覆盖指南（

{overrides}/pronunciation-guide.md

）：

读取配置获取
```
paths.overrides
```
路径
检查是否存在
```
{overrides}/pronunciation-guide.md
```
如果不存在则创建文件（包含表头和表格结构）
将词汇添加到相应章节（艺术家术语、专辑名称等）
包含：词汇、标准拼写、语音拼写、说明

示例条目：

markdown

| Larocca | larocca | Luh-rock-uh | Character in "sample-album" album |

请勿编辑基础指南（

${CLAUDE_PLUGIN_ROOT}/reference/suno/pronunciation-guide.md

）——插件更新会覆盖它。

何时添加：

艺术家名称、专辑标题、音轨标题
纪录片/叙事专辑中的角色名称
专辑内容特定的地点名称
制作过程中发现的任何发音问题

这样可以将新发现的发音问题与覆盖目录中的音乐内容一起进行版本控制。

Remember

注意事项

Load both guides at start - Base guide + override guide (if exists)
Homographs are landmines - live, read, lead, wind WILL mispronounce without fixes
Tech terms need phonetic spelling - Don't trust Suno with acronyms
Non-English names always need help - Phonetic spelling mandatory
Numbers are tricky - Write them out or use apostrophes
When in doubt, ask - Better to clarify than regenerate
Add discoveries to OVERRIDE guide - Never edit base guide (plugin will overwrite)

启动时加载两份指南——基础指南 + 覆盖指南（如果存在）
同形异义词是雷区——live、read、lead、wind如果不修复肯定会读错
技术术语需要语音拼写——不要信任Suno处理缩写词
非英语名称总是需要辅助——必须使用语音拼写
数字很棘手——用单词拼写或撇号
有疑问时就询问——澄清总比重新生成好
将新发现添加到覆盖指南——永远不要编辑基础指南（插件会覆盖）