AI 영작문 코치 — 이메일·에세이·보고서 원어민 수준으로
비즈니스 이메일, 에세이, 보고서 등 목적별 영작문 프롬프트와 AI 첨삭 요청 템플릿을 제공하여, 원어민 수준의 영어 글쓰기를 달성합니다.
영어로 이메일 한 통 쓰는 데 30분이 걸린 적 있으신가요? 구글 번역에 한국어를 넣고, 나온 영어가 맞는지 다시 검색하고, 그래도 불안해서 동료에게 확인받고 — 이런 과정을 반복하고 계시다면, 이 챕터가 여러분의 영작문 시간을 1/10로 줄여드립니다.
AI를 영작문 코치로 활용하는 핵심은 단순 번역이 아니라 첨삭과 학습을 동시에 하는 것입니다. "이걸 영어로 번역해줘"가 아니라, "내가 쓴 영어를 고쳐주고 왜 그렇게 고쳤는지 설명해줘"라고 요청하는 차이가 실력 향상의 핵심입니다.
AI 영작문 코치 세팅 — 마스터 프롬프트
모든 영작문 연습 전에 이 프롬프트를 먼저 입력하세요. AI의 피드백 품질이 극적으로 달라집니다.
마스터 세팅 프롬프트
You are my English writing coach. Follow these rules for all writing feedback:
- My level: intermediate Korean English learner working in [your industry]
- When correcting my writing, use this format for EACH correction:
- ORIGINAL: [my text]
- CORRECTED: [your correction]
- WHY: [explanation in Korean]
- LEVEL UP: [a more sophisticated alternative for the same meaning]
- Rate my overall writing: Grammar (1-10), Naturalness (1-10), Vocabulary (1-10), Tone appropriateness (1-10)
- At the end, rewrite my ENTIRE text in a polished, native-level version
- If I ask you to write something from scratch, provide 2 versions: Standard and Premium (more sophisticated)
Confirm with 'Ready to coach your writing!'
이 세팅의 핵심은 LEVEL UP 항목입니다. 단순 교정에서 끝나지 않고, 같은 의미를 더 세련되게 표현하는 방법까지 배울 수 있습니다.
파트 1: 비즈니스 이메일 프롬프트
업무 이메일은 가장 빈번하게 영작이 필요한 영역입니다. 상황별 프롬프트와 Before/After 예시를 제공합니다.
프롬프트 01 — 미팅 요청 이메일
Write a professional email requesting a meeting. Context: I need to discuss the Q3 marketing budget with my team lead, Sarah. I'd like to meet this week, preferably Tuesday or Wednesday afternoon. Keep it concise (under 100 words). Provide two versions: formal (for a director-level meeting) and semi-formal (for a team lead you work with daily).
Before (한국인이 흔히 쓰는 버전): "Dear Sarah, I want to have a meeting with you about Q3 marketing budget. Can we meet on Tuesday or Wednesday afternoon? Please let me know your available time. Thank you."
After (AI가 다듬은 버전): "Hi Sarah, I'd like to schedule a quick meeting to go over the Q3 marketing budget. Would Tuesday or Wednesday afternoon work for you? I'm flexible on time — just let me know what's convenient. Thanks, [Name]"
차이 포인트: "I want to have a meeting" → "I'd like to schedule a quick meeting", "your available time" → "what's convenient"
프롬프트 02 — 정중한 거절 이메일
Write a polite decline email. Context: A vendor (James from TechSolutions) sent me a proposal for a new CRM system. The proposal is good but we already signed with a competitor last month. I want to decline without burning the bridge — we might work with them in the future. Keep the door open. Under 120 words.
프롬프트 03 — 독촉 이메일 (Follow-up)
Write a follow-up email. Context: I sent a report to my client (Mr. Park at Hyundai) 5 days ago and haven't heard back. I need his approval to proceed. This is my second follow-up. Be polite but convey urgency without being pushy. Include a soft deadline. Under 100 words.
프롬프트 04 — 감사 이메일
Write a thank-you email. Context: My team just finished a major product launch. I want to thank the cross-functional team (design, engineering, marketing) for their hard work over the past 3 months. Be genuine, specific (mention the late nights and creative problem-solving), and motivating. 150-200 words.
프롬프트 05 — 문의 이메일
Write an inquiry email. Context: I found a potential supplier (GlobalTech Inc.) for electronic components. I need to ask about: minimum order quantity, bulk pricing for 10,000+ units, lead time, and whether they can customize specifications. Professional but not overly formal. Under 150 words.
프롬프트 06 — 사과 이메일
Write an apology email. Context: Our team delivered a report to the client 3 days late. The delay was due to unexpected data issues. I need to apologize sincerely, explain briefly without making excuses, and outline steps to prevent this from happening again. The client is important but understanding. Under 150 words.
프롬프트 07 — 소개/추천 이메일
Write an introduction email. Context: I want to connect my former colleague (Jiyeon, a UX designer) with my current manager (David) because we're looking for a freelance designer. Jiyeon doesn't know David. Write the email to David introducing Jiyeon, highlighting her relevant skills, and asking if David would be open to a call. Under 120 words.
파트 2: 이메일 첨삭 요청 프롬프트
이미 작성한 이메일을 AI에게 첨삭받는 프롬프트입니다. 이것이 실력 향상의 핵심입니다.
프롬프트 08 — 기본 첨삭
Please review and correct my business email below. For each change you make, explain in Korean why the original was wrong or unnatural. Then provide a fully corrected version at the end.
[여기에 본인이 작성한 영어 이메일을 붙여넣으세요]
프롬프트 09 — 톤 분석 첨삭
Review my email below. Focus specifically on TONE. Is it too formal? Too casual? Too direct? Too passive? Rate the tone appropriateness (1-10) and rewrite it with the perfect tone for the situation I describe.
Situation: [이메일을 보내는 상황 설명] My email: [여기에 이메일 붙여넣기]
프롬프트 10 — 한→영 이메일 변환 (학습형)
I wrote an email in Korean. Please do the following:
- Translate it to English
- Then show me 3 expressions I should memorize from this email (with Korean explanation)
- Show me one common mistake Korean speakers would make when writing this email
- Rate the difficulty level of this email (beginner/intermediate/advanced)
Korean email: [한국어 이메일 붙여넣기]
단순 번역과 다릅니다. 학습 포인트를 함께 추출하므로, 같은 유형의 이메일을 다음에는 스스로 쓸 수 있게 됩니다.
파트 3: 에세이/리포트 작성 프롬프트
논리적 글쓰기는 영어 실력의 정점입니다. 구조부터 잡고, 문단별로 완성하는 프롬프트를 제공합니다.
프롬프트 11 — 에세이 구조 잡기
I need to write a 500-word essay on the topic: '[주제를 영어로 입력]'. Help me create an outline with:
- A hook (attention-grabbing opening sentence) — give me 3 options
- Thesis statement — give me 2 options (one direct, one nuanced)
- 3 body paragraph topics with 2 supporting points each
- A conclusion approach (summary, call to action, or thought-provoking question)
Don't write the essay. Just the skeleton. I'll write each section and ask for feedback.
이 접근법의 핵심은 AI가 대신 써주는 것이 아니라, 구조를 잡아주고 내가 쓰는 것입니다.
프롬프트 12 — 도입부 작성 + 피드백
I wrote the introduction paragraph for my essay on [주제]. Please:
- Check grammar and style
- Evaluate my hook — is it engaging? (rate 1-10)
- Is my thesis statement clear and arguable? (rate 1-10)
- Suggest improvements without rewriting the whole thing
- Show me 2 transition phrases I can use to start my first body paragraph
My introduction: [도입부 붙여넣기]
프롬프트 13 — 논증 강화
Read my body paragraph below. It's arguing that [주장]. My evidence feels weak. Help me:
- Identify logical gaps in my argument
- Suggest 2 types of evidence I could add (statistics, examples, expert quotes)
- Point out any logical fallacies
- Show me how to use hedging language ('tend to', 'it appears that', 'the evidence suggests') to make my argument more academic
My paragraph: [본문 문단 붙여넣기]
프롬프트 14 — 결론 작성 가이드
My essay argues that [주제/주장]. I've covered these 3 points: [포인트 1], [포인트 2], [포인트 3]. Help me write a strong conclusion. Rules:
- Don't just repeat the introduction
- Synthesize the arguments into a larger insight
- End with either a call to action, a question, or a forward-looking statement
- Provide 2 versions: safe (for academic settings) and bold (for opinion pieces)
프롬프트 15 — 전체 에세이 리뷰
Review my complete essay below using this rubric:
Category Score (1-10) Comments Thesis clarity Argument strength Evidence quality Organization/flow Grammar Vocabulary range Academic tone Conclusion impact After the rubric, list your top 5 specific suggestions for improvement. Then provide a revised version of my weakest paragraph only.
My essay: [전체 에세이 붙여넣기]
파트 4: 톤 조절 프롬프트
같은 내용을 상황에 따라 다른 톤으로 쓰는 능력은 고급 영작의 핵심입니다.
프롬프트 16 — 격식 수준 변환
Convert the following sentence into 4 different formality levels. For each, explain in Korean when you would use this level:
- Very formal (academic paper, legal document)
- Formal (business email to a client)
- Semi-formal (email to a colleague)
- Casual (text to a friend)
Original: [변환할 문장 입력]
실전 예시:
- 원문: "We need to talk about the project."
- Very formal: "I would like to request an opportunity to discuss the project status at your earliest convenience."
- Formal: "I'd appreciate the chance to discuss the project with you."
- Semi-formal: "Can we chat about the project sometime soon?"
- Casual: "Hey, we should talk about the project."
프롬프트 17 — 직접 표현 ↔ 간접 표현 변환
Convert these direct sentences into polite, indirect versions (and vice versa). Explain in Korean why the indirect version is sometimes more appropriate in English business culture.
Direct sentences to convert:
- 'You made a mistake in the report.'
- 'I disagree with your plan.'
- 'Send me the file by tomorrow.'
- 'This presentation is boring.'
- 'You're late again.'
이 프롬프트는 한국인이 가장 어려워하는 영역 중 하나를 다룹니다. 영어권에서는 직접적인 표현이 무례하게 들릴 수 있습니다.
프롬프트 18 — 긍정/부정 프레이밍
Rewrite these negative sentences in a positive frame. Show how the same message can sound constructive instead of critical. Explain the psychology behind positive framing in Korean.
- 'You failed to meet the deadline.'
- 'This idea won't work.'
- 'You don't have enough experience.'
- 'The product has too many bugs.'
- 'We can't afford this.'
파트 5: 문법 교정 프롬프트
프롬프트 19 — 설명 포함 교정
Correct the grammar in my text below. For EVERY correction, use this format:
[LINE NUMBER] WRONG: [original] [LINE NUMBER] RIGHT: [correction] [LINE NUMBER] RULE: [grammar rule in Korean, e.g., '관사 사용법 — 특정 명사 앞에 the 사용'] [LINE NUMBER] TIP: [how to remember this rule]
My text: [교정할 텍스트 붙여넣기]
프롬프트 20 — 수정만 (빠른 교정)
Proofread the following text. ONLY fix errors — do not change style or rewrite sentences. Mark each change with [FIXED] at the end of the corrected sentence. If a sentence is correct, mark it with [OK].
[교정할 텍스트 붙여넣기]
시간이 없을 때는 이 프롬프트로 빠르게 교정만 받으세요.
프롬프트 21 — 한국인 특화 문법 체크
Check my English text for common mistakes that Korean speakers make. Focus specifically on:
- Article errors (a/an/the/zero article)
- Preposition errors (in/on/at confusion)
- Singular/plural errors
- Tense consistency
- Subject-verb agreement
- Unnecessary passive voice (Korean speakers overuse passive)
- Word order (Korean SOV vs English SVO transfer errors)
For each error found, explain the Korean interference pattern causing it.
My text: [텍스트 붙여넣기]
이 프롬프트는 한국어 간섭 현상을 정확히 짚어줍니다. 예를 들어, 한국어에는 관사가 없기 때문에 "I went to school"과 "I went to the school"의 차이를 놓치는 패턴을 교정합니다.
파트 6: 표현 업그레이드 프롬프트
프롬프트 22 — 초급 → 중급 → 고급 변환
Upgrade my sentences through 3 levels. For each sentence:
Level 1 (Basic): [my original sentence] Level 2 (Intermediate): [improved vocabulary and structure] Level 3 (Advanced): [sophisticated, native-level expression]
Explain each upgrade step in Korean.
My sentences:
- 'The meeting was good.'
- 'I think this is a big problem.'
- 'We need to work harder.'
- 'The results were bad.'
- 'I'm happy about the news.'
예시 결과:
- Level 1: "The meeting was good."
- Level 2: "The meeting went well and we covered all the key points."
- Level 3: "The meeting was productive — we aligned on priorities and identified clear next steps."
프롬프트 23 — 동의어 뉘앙스 맵
Create a 'nuance map' for the word '[단어 입력]'. Show me:
- 5-8 synonyms arranged from weakest to strongest
- Formality level of each (casual/neutral/formal)
- Positive, negative, or neutral connotation
- Example sentence for each
- When a Korean speaker would typically misuse each one
Present as a table.
실전 예시 — "angry"의 뉘앙스 맵:
| 단어 | 강도 | 격식 | 감정색 | 예문 |
|---|---|---|---|---|
| annoyed | 약 | 중립 | 부정 | "I'm annoyed by the noise." |
| frustrated | 중 | 중립 | 부정 | "I'm frustrated with the delays." |
| upset | 중 | 중립 | 부정 | "She was upset about the decision." |
| angry | 강 | 중립 | 부정 | "He was angry at his manager." |
| furious | 매우 강 | 중립 | 강한 부정 | "She was furious when she found out." |
| livid | 최강 | 비격식 | 강한 부정 | "He was livid about being passed over." |
프롬프트 24 — 클리셰 제거
Review my writing and identify any clichés, overused expressions, or phrases that sound like they came from a textbook. Replace each with a more original, natural alternative. Explain in Korean why the original sounds cliché.
My text: [텍스트 붙여넣기]
한국 영어 교육에서 배우는 표현 중 상당수는 원어민이 잘 쓰지 않는 구식 표현입니다. "As a matter of fact", "In my humble opinion", "Last but not least" 같은 표현이 대표적입니다.
프롬프트 25 — 연결어/전환어 마스터
I tend to only use 'and', 'but', 'so', 'because' in my writing. Give me a comprehensive list of transition words and phrases organized by function:
- Addition (moreover, furthermore, in addition...)
- Contrast (however, nevertheless, on the other hand...)
- Cause/Effect (consequently, as a result, therefore...)
- Example (for instance, specifically, to illustrate...)
- Sequence (first, subsequently, finally...)
- Emphasis (indeed, in fact, notably...)
- Concession (admittedly, granted, although...)
For each, show formality level and give one example sentence. Mark the top 5 most useful ones for business writing with a star.
파트 7: 실전 작문 연습 프롬프트
프롬프트 26 — 일일 영작 챌린지
Give me a daily writing challenge. The topic should be relevant to [business/technology/daily life 중 선택]. Requirements:
- A specific writing prompt (what to write about)
- Target length (100-200 words)
- Required vocabulary: 3 words I must include
- Required grammar: 1 structure I must use (e.g., conditional, passive voice)
- Time limit: 15 minutes
After I submit, grade me on: task completion, grammar, vocabulary use, and naturalness.
프롬프트 27 — 이메일 체인 시뮬레이션
Let's simulate a realistic email chain. Scenario: I'm a project manager and a client just emailed me unhappy about the latest deliverable. You'll write the client's emails and I'll write my responses. The chain should go 4-5 emails. After the chain ends, review ALL my emails and give comprehensive feedback.
Start with the client's first (angry) email.
이 프롬프트는 실전에 가장 가까운 연습입니다. 실제 업무에서는 이메일이 한 통으로 끝나지 않고 주고받는 체인으로 이어지기 때문입니다.
프롬프트 28 — 보고서 작성 (비즈니스)
Help me write a one-page executive summary. Context:
- Project: [프로젝트명]
- Key results: [핵심 결과 한국어로 입력]
- Challenges faced: [직면한 문제 한국어로 입력]
- Next steps: [다음 단계 한국어로 입력]
First, write it for me as a model. Then give me a template I can reuse for future reports. Highlight 10 key business phrases I should memorize from this report.
프롬프트 29 — LinkedIn 포스트 작성
Help me write a LinkedIn post about [주제]. Requirements:
- Hook in the first line (make people stop scrolling)
- Personal story or insight (not generic advice)
- 3-5 actionable takeaways
- A question at the end to drive engagement
- Appropriate hashtags
- Length: 150-200 words
- Tone: professional but personable
Provide 2 versions: one conservative, one bold.
프롬프트 30 — 제안서/프로포절
I need to write a project proposal email to convince my manager to approve [프로젝트/아이디어]. Help me structure it using the BLUF (Bottom Line Up Front) method:
- One-sentence recommendation
- Key benefits (3 bullet points)
- Required resources (time, budget, people)
- Risk mitigation
- Proposed timeline
Write it under 200 words. Then explain the BLUF framework in Korean so I can use it independently.
한국인이 자주 하는 영작 실수 Top 10
AI에게 이 실수 패턴을 알려주면 맞춤형 교정이 가능합니다.
프롬프트 31 — 실수 패턴 교정 요청
As my writing coach, here are the common mistakes I make as a Korean English writer. Whenever you review my writing, pay special attention to these patterns:
- Missing articles (a/the) — Korean has no articles
- Wrong prepositions — I confuse in/on/at
- Overusing 'I think' at the beginning of every opinion
- Using 'very' too much instead of stronger adjectives
- Translating Korean sentence structure directly (SOV → SVO errors)
- Confusing countable/uncountable nouns (informations → information)
- Using formal expressions in casual contexts
- Missing subject ('Is good' instead of 'It is good' — Korean drops subjects)
- Confusing 'make' and 'do' (Korean uses 하다 for both)
- Overusing passive voice (Korean 되다 structure)
For my next piece of writing, flag any of these patterns with [K-ERROR #number] so I can track my improvement.
이 프롬프트를 한 번 입력해두면, 이후 모든 교정에서 한국인 특화 패턴을 집중 체크합니다.
| 실수 | 한국어 간섭 원인 | 틀린 예 | 맞는 예 |
|---|---|---|---|
| 관사 누락 | 한국어에 관사 없음 | "I went to hospital" | "I went to the hospital" |
| 전치사 혼동 | 한국어 '에'가 in/on/at 모두 커버 | "I arrived at Monday" | "I arrived on Monday" |
| 주어 생략 | 한국어는 주어 생략 허용 | "Is very important" | "It is very important" |
| 복수형 실수 | 한국어 복수 표시 약함 | "many information" | "a lot of information" |
| do/make 혼동 | 한국어 '하다' 하나로 통용 | "make homework" | "do homework" |
반복 학습 시스템: 주간 영작 루틴
프롬프트 32 — 주간 영작 리포트
Based on all the writing I've submitted to you this week, create a weekly writing report:
- Total corrections made (by category)
- Most improved area
- Persistent problem areas (still making the same mistakes)
- 5 new expressions I learned this week
- Recommended focus for next week
- Overall progress assessment
Present in Korean.
추천 주간 루틴
| 요일 | 활동 | 소요 시간 | 프롬프트 번호 |
|---|---|---|---|
| 월 | 비즈니스 이메일 작성 + 첨삭 | 20분 | #01~#07 중 택1 |
| 화 | 일일 영작 챌린지 | 15분 | #26 |
| 수 | 표현 업그레이드 연습 | 15분 | #22~#25 중 택1 |
| 목 | 이메일 체인 시뮬레이션 | 25분 | #27 |
| 금 | 자유 주제 에세이 (200단어) | 20분 | #11~#15 |
| 토 | 주간 리포트 확인 + 약점 복습 | 15분 | #32 |
| 일 | 휴식 또는 LinkedIn 포스트 | 10분 | #29 |
이 루틴을 4주만 유지하면, 영작 속도와 품질이 눈에 띄게 향상됩니다.
고급 활용: AI와 반복 수정하기
프롬프트 33 — 3단계 반복 수정
Let's do iterative writing improvement. I'll give you my draft. Process:
Round 1: Fix grammar and spelling only. Don't change anything else. Round 2: Improve sentence structure and flow. Keep my voice. Round 3: Upgrade vocabulary and add sophistication. Make it sound polished.
Show me the text after each round so I can see how it evolves. Explain major changes in Korean after each round.
My draft: [초안 붙여넣기]
이 프롬프트의 가치는 단계별 변화를 보여주는 것입니다. 한 번에 완벽하게 고치면 무엇이 바뀌었는지 알기 어렵지만, 3단계로 나누면 각 수준의 차이를 명확히 이해할 수 있습니다.
프롬프트 34 — A/B 버전 비교
I wrote two versions of the same email. Which is better and why? Analyze:
- Clarity of message
- Tone and professionalism
- Grammar accuracy
- Native-likeness (does it sound like a native wrote it?)
- Specific recommendations for the weaker version
Version A: [버전 A 붙여넣기]
Version B: [버전 B 붙여넣기]
자신이 쓴 두 가지 버전을 비교하면, 어떤 선택이 더 좋은지 판단력이 길러집니다.
프롬프트 35 — 역번역 학습법
Here's a well-written English paragraph from [The Economist / Harvard Business Review / etc.].
- First, translate it to Korean naturally
- Then I will try to translate it back to English without looking at the original
- Compare my version with the original and analyze the differences
Original English: [원문 붙여넣기]
역번역(back-translation)은 통번역사들이 사용하는 훈련법입니다. 원어민의 표현을 한국어로 이해한 뒤, 다시 영어로 표현해보면 자신의 표현력 한계가 명확히 드러납니다.
상황별 즉석 영작 프롬프트
급하게 영작이 필요할 때 바로 쓸 수 있는 프롬프트입니다.
프롬프트 36 — 긴급 이메일 생성
Write an urgent email for me RIGHT NOW. Situation: [상황을 한국어로 설명]. Tone: [formal/casual/apologetic/firm]. Length: under [단어 수] words. Include: [반드시 포함할 내용].
프롬프트 37 — 채팅/슬랙 메시지
Help me write a Slack message to my team. Context: [상황 한국어로 설명]. Keep it: casual, under 50 words, friendly but clear. Use emojis if appropriate. Give me 2 options.
프롬프트 38 — 영어 발표 스크립트
Write a 3-minute presentation script about [주제]. Structure: hook → 3 key points → closing. Include: transition phrases between sections, places to pause marked with [PAUSE], and a strong closing statement. Add pronunciation tips for difficult words in parentheses.
영작 실력 자가 진단 프롬프트
프롬프트 39 — 실력 테스트
Give me an English writing assessment test. Include:
- Grammar section: 10 error correction questions (find and fix the error)
- Vocabulary section: 5 'choose the better word' questions
- Writing section: Write a 100-word response to a prompt you give me
After I complete all sections, give me a CEFR writing level (A1-C2) with a detailed breakdown of my strengths and weaknesses. Present results in Korean.
프롬프트 40 — 월간 성장 기록
Create a monthly writing progress report template that I can fill in every month:
- Writing volume this month (how many emails, essays, etc.)
- Most common error type (from your corrections)
- New expressions mastered (at least 10)
- Areas of improvement since last month
- Challenge areas remaining
- Goal for next month
- Self-rated confidence level (1-10)
Make it a simple template I can copy and fill in. Include example entries.
다음 챕터 미리보기
말하기(챕터 2)와 쓰기(이번 챕터)의 기초를 다졌으니, 다음 챕터에서는 토익·토플 AI 정복법을 다룹니다. 토익·토플 파트별 AI 공략 프롬프트, 약점 분석 자동화, 모의문제 생성, 오답 분석 프롬프트를 제공하여 시험 준비를 체계적으로 도와드립니다.