From skills
Decode Zhuyin (Bopomofo) text typed with English keyboard keys into Chinese characters. ALWAYS try this skill when encountering unrecognized short letter/number sequences mixed with Chinese text that don't look like real English words or acronyms - e.g. "e04", "cl3", "su3", "cp3". Also use when user explicitly mentions 注音文, or asks what a cryptic alphanumeric fragment means in a Chinese context.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skills:e04The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Decode "注音文" — Chinese text typed as English keyboard keys using the standard Zhuyin (Bopomofo) input method layout.
Decode "注音文" — Chinese text typed as English keyboard keys using the standard Zhuyin (Bopomofo) input method layout.
| Key | Zhuyin | Key | Zhuyin | Key | Zhuyin |
|---|---|---|---|---|---|
| 1 | ㄅ | r | ㄐ | 5 | ㄓ |
| q | ㄆ | f | ㄑ | t | ㄔ |
| a | ㄇ | v | ㄒ | g | ㄕ |
| z | ㄈ | 2 | ㄉ | b | ㄖ |
| w | ㄊ | e | ㄍ | y | ㄗ |
| s | ㄋ | d | ㄎ | h | ㄘ |
| x | ㄌ | c | ㄏ | n | ㄙ |
| Key | Zhuyin | Key | Zhuyin | Key | Zhuyin |
|---|---|---|---|---|---|
| 8 | ㄚ | 9 | ㄞ | 0 | ㄢ |
| i | ㄛ | o | ㄟ | p | ㄣ |
| k | ㄜ | l | ㄠ | ; | ㄤ |
| , | ㄝ | . | ㄡ | / | ㄥ |
| u | ㄧ | j | ㄨ | m | ㄩ |
| - | ㄦ |
| Key | Tone |
|---|---|
| space | ˉ (一聲,陰平) |
| 6 | ˊ (二聲,陽平) |
| 3 | ˇ (三聲,上聲) |
| 4 | ˋ (四聲,去聲) |
| 7 | ˙ (輕聲) |
3, 4, 6, 7) mark the END of a syllable. Structure: [consonant] + vowel(s) + tone3, 4, 6, 7) always terminates a syllableInput: e04
e → ㄍ, 0 → ㄢ, 4 → ˋInput: cl3
c → ㄏ, l → ㄠ, 3 → ˇInput: su3cl3 (multi-syllable)
s → ㄋ, u → ㄧ, 3 → ˇ (syllable break) | c → ㄏ, l → ㄠ, 3 → ˇWhen decoding, show:
「{input}」→ {zhuyin} → {chinese_character}
If a syllable maps to multiple possible characters, list the most common ones and ask the user which they meant (if context is insufficient).
84 = ㄚˋ = 啊)npx claudepluginhub shihyuho/skills --plugin skillsGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.