Use this skill when the user types "/convo-maker", "/convo", "make conversation", "영어 대화 만들어", "미국식 영어", "native english dialog", "session to english", "대화로 만들어", or wants to convert current session Q&A into natural American English conversations.
Transform your session Q&A into natural, native-sounding American English dialogues
Scans the current session's conversation history — your questions and Claude's answers — and rewrites them as a realistic dialogue between two Americans (Alex and Jamie). The output sounds like real casual or professional conversation, not textbook English.
Review the conversation so far in this session. Identify:
Skip meta-talk (greetings, "sure!", "of course!" etc.) and focus on .
For each Q&A pair, rewrite as a conversation between Alex (the asker) and Jamie (the knowledgeable friend). Apply these rules:
Language Style Rules:
Tone Options (choose based on topic):
Output the conversation in this format:
Setting: [1-line scene description — where/when/why they're talking]
Alex: [Opening line that naturally introduces the topic]
Jamie: [Response with key information, conversational tone]
Alex: [Follow-up question or reaction]
Jamie: [Deeper explanation or example]
Alex: [Clarifying question or "aha" moment]
Jamie: [Wrap-up with practical tip or summary]
| Expression | Meaning | Example from conversation |
|---|---|---|
| [phrase used] | [plain English meaning] | [quote from above] |
If the session covered "How does TypeScript help with bugs?":
Setting: Two dev friends catching up at a coffee shop after work.
Alex: Hey, so I keep hearing about TypeScript. Like, is it actually worth switching from plain JavaScript?
Jamie: Oh man, honestly? Yeah, it's totally worth it — especially if you're working on anything bigger than a side project. Here's the thing: TypeScript basically catches your bugs before you even run the code.
Alex: Wait, what do you mean before you run it?
Jamie: So you know how in regular JS you can just pass whatever into a function and it won't complain until it blows up in production? TypeScript won't even let you do that. It flags it right in your editor.
Alex: Oh, so it's like... a spellcheck but for your logic?
Jamie: Exactly! That's a great way to put it. It's like having a really picky coworker who catches all your typos before the code ships. Kinda annoying at first, but you get used to it fast.
Alex: Huh. And the learning curve — is it rough?
Jamie: Not really. If you already know JS, you're probably looking at a week or two before it clicks. I'd say just start with one file, add types gradually. No need to go all in from day one.
| Expression | Meaning | Example |
|---|---|---|
| "blows up in production" | causes an error when real users run it | "...it won't complain until it blows up in production" |
| "go all in" | commit completely from the start | "No need to go all in from day one." |
| "clicks" | suddenly makes sense / you understand it | "...before it clicks" |
/Users/gwanli/CS볼트V5/00. Inbox/08. 퀵캡쳐/영어메모/1. 영어메모_작업전/ as a .md file. File name format: convo_YYYY-MM-DD_[Topic].md (e.g., convo_2026-04-05_TypeScript.md). Use today's date and the first topic title. Do not ask — just save silently and confirm with the file path at the end.When the conversation is generated:
<promise>CONVO_MAKER_COMPLETE</promise>