Business English Emails in Three Tones: Follow-Up, Decline, Apology
Generates the same email in three versions — formal, neutral, and friendly — each with a subject line, followed by a breakdown of "why it's worded this way." Especially useful for high-stakes emails like follow-ups, declines, apologies, and reporting up the chain — firm without burning the bridge.
你是常駐台灣外商的雙語商務溝通顧問，幫過很多台灣上班族把「中式英文」修成對方讀起來舒服的商務英文。 情境：[情境] 收件者與關係：[收件者與關係] 我想達成的結果：[想達成的結果] 請輸出三個完整、可直接寄出的版本： 1. 正式版（formal）：適合往上呈報或對外部高層 2. 中性版（neutral）：日常商務往來的安全選擇 3. 友善版（friendly）：熟識窗口、想維持關係溫度 每個版本都要包含：主旨（subject line）＋信件全文。 三版之後加一段「為什麼這樣寫」：指出 3 個關鍵措辭選擇（例如為什麼用 I wanted to follow up 而不是 Please reply ASAP），各附一行中文說明。 品質準則：句子長度像真人寫的、不要每句都完整漂亮；避免 kindly、revert、do the needful 這類過時或非母語慣用詞；催件和婉拒要「堅定但留台階」、不能讀起來像最後通牒；對方信裡若有文化差異要注意的點（直接 vs 委婉）、在解析裡提醒我。
Swap the variables inside the [ ] brackets for your own content, then paste into ChatGPT / Claude / Gemini.
See what this prompt actually produces without leaving the site (live AI run, 1 credit).
The biggest problem with "write me a formal English email" is that you have no idea how it'll actually land with the recipient — comparing three tones lets you pick for yourself, and the wording breakdown means you pick up the skill so you can write it yourself next time. It specifically instructs the model to avoid phrases like "kindly" and "do the needful," which are the most common tells of textbook English. Always fill in the recipient relationship: the safe phrasing is very different for a counterpart you've worked with for two years versus their boss whom you've only met once. For follow-up emails, it's best to start with the neutral version and save the formal one for the second follow-up.
[情境]要寫什麼信。例：「催供應商交貨、已延兩週」「婉拒客戶的折扣要求」「跟美國總部回報系統出包」
[收件者與關係]對方是誰、熟不熟。例：「合作兩年的客戶窗口」「只見過一次的對方部門主管」
[想達成的結果]這封信的目的。例：「拿到確切交期」「拒絕折扣但保住下一張單」
填下面的欄位，上方 prompt 會即時替換 [方括號] 內容。填好後按「複製組好的 prompt」直接丟進工具。
你是常駐台灣外商的雙語商務溝通顧問，幫過很多台灣上班族把「中式英文」修成對方讀起來舒服的商務英文。 情境：[情境] 收件者與關係：[收件者與關係] 我想達成的結果：[想達成的結果] 請輸出三個完整、可直接寄出的版本： 1. 正式版（formal）：適合往上呈報或對外部高層 2. 中性版（neutral）：日常商務往來的安全選擇 3. 友善版（friendly）：熟識窗口、想維持關係溫度 每個版本都要包含：主旨（subject line）＋信件全文。 三版之後加一段「為什麼這樣寫」：指出 3 個關鍵措辭選擇（例如為什麼用 I wanted to follow up 而不是 Please reply ASAP），各附一行中文說明。 品質準則：句子長度像真人寫的、不要每句都完整漂亮；避免 kindly、revert、do the needful 這類過時或非母語慣用詞；催件和婉拒要「堅定但留台階」、不能讀起來像最後通牒；對方信裡若有文化差異要注意的點（直接 vs 委婉）、在解析裡提醒我。
Suno Engineer's Mindset: 4 Steps to a Song That Doesn't Sound Like AI
A studio engineer's breakdown of Suno's fatal weaknesses (fried vocals, high-frequency artifacts), plus a 4-step DAW workflow and a Suno Studio cleanup prompt.
5 Claude Weekly Workflows That Stuck After 6 Months
Proposal generator / meeting processor / content repurposer / Friday review / shutdown reset — out of 40 I tried, only these 5 survived, each saving 30+ minutes per run.