ChatGPT 프롬프트 템플릿 라이브러리

You are a senior content strategist. Topic: [TOPIC]; audience: [AUDIENCE]; target keywords: [KEYWORDS]. Deliver: 1) three title options; 2) H2/H3 outline; 3) section bullets with suggested word counts; 4) opening hook and closing CTA. Tone: [TONE].

Rewrite the text below in a [professional/friendly/concise] tone, about [WORD COUNT] words. Keep key facts and numbers; remove empty filler. Original:
[PASTE]

You are an SEO editor. Keyword: [PRIMARY]; related terms: [RELATED]; intent: [informational/comparison/how-to]; audience: [AUDIENCE]. Write a ~[WORD COUNT]-word draft with H1/H2s, answer-first intro, bullet takeaways, internal-link placeholders, and a 3-question FAQ. Avoid keyword stuffing.

Turn [TOPIC] into a [X/LinkedIn] thread of [N] posts. Post 1 is a strong hook; each post stands alone; conversational but concrete; end with a CTA. Audience: [AUDIENCE].

Localize from [SOURCE LANG] to [TARGET LANG] for channel [social/website/email] and audience [AUDIENCE]. Keep brand name [NAME]. Add translator notes where culture differs. Source:
[TEXT]

You are a career coach. Target role: [ROLE]. Rewrite the experience into 5–8 achievement bullets: verb-led, quantified where possible, impact-first. Drop empty adjectives. Experience:
[PASTE]

Turn the idea [DESCRIPTION] into an image prompt: subject, setting, lighting, lens/composition, style refs, color, and negative prompt (what to avoid). Output English and Korean versions for easy paste into common image models.

You are a senior [LANGUAGE] engineer. Review this code: list issues by severity, concrete fixes, test ideas, then provide improved full code.
```
[CODE]
```

Explain the following code for a [beginner/intermediate] developer: purpose, step-by-step logic, key APIs, common pitfalls, and a minimal runnable variant.
[CODE]

You are a debugging expert. Stack: [LANG/FRAMEWORK]. Error:
[PASTE]
Related code:
[CODE]
Output: most likely causes (ranked), how to verify, minimal patch, and how to prevent recurrence.

Generate unit tests for this [LANGUAGE] function (framework: [Jest/pytest/other]): happy path, edges, failures; state intent per case; provide runnable test code.
[CODE]

From requirement [DESCRIPTION], design an API: resources, methods and paths, sample request/response JSON, auth, main error codes, pagination. List assumptions and open questions. Style: [REST/RPC].

You are a refactor coach. Goal: improve [readability/performance/testability] without changing behavior. Code:
[CODE]
Output: risks, stepwise plan, verification per step, and target structure notes.

You are a patient tutor. Topic: [TOPIC]. Confirm my level, then use Socratic questions. Ask only 1–2 questions at a time; give hints—not full answers—when I am wrong.

Read the material and output: 1) one-sentence conclusion; 2) problem and method; 3) key results; 4) limits and debates; 5) three implications for my work in [SCENARIO]. Material:
[PASTE OR SUMMARY]

Topic: [TOPIC]; level: [beginner/intermediate/advanced]. Create [N] questions (mix MCQ + short answer). For each: correct answer, brief rationale, and a common misconception.

Goal: [GOAL]; level: [LEVEL]; hours/week: [HOURS]; duration: [WEEKS]. Output a weekly plan, daily tasks, checkpoints, and resource types (do not invent paid affiliate links).

Answer question [QUESTION] using ONLY the materials below. Rules: cite the source span for each claim; if uncovered, say “insufficient material”; invent no links or numbers. Materials:
[PASTE]

Topic: [TOPIC]. Create [N] flashcards: front question, back answer (2–4 sentences), one memory hook. Level: [beginner/intermediate]. Avoid long paragraphs.

Structure these meeting notes into: topic summary, key decisions, action items (owner + due date), open questions, and risks. Formal and concise. Notes:
[PASTE]

From the idea [DESCRIPTION], write a lean PRD: background and goals, user stories, scope (including non-goals), acceptance criteria, priorities, risks, and success metrics. Audience: [PM/eng/design].

Write outreach to [ROLE/COMPANY]. Value: [OFFER]; proof: [CASE/METRIC]; ask: [meeting/trial]. Provide 3 subject lines, body under 150 words, no hype, clear CTA.

You are a business analyst. From this data description, output: key trends, anomalies, hypothesized causes, questions to validate, and three actions for [ROLE]. Data:
[PASTE]

For [PRODUCT/PLAN] vs competitor [NAME], produce a SWOT (3–5 bullets each). End with a go/no-go recommendation and key assumptions. Audience: [exec/product].

You are a support specialist. Issue: [CUSTOMER ISSUE]; allowed facts/policy: [DISCLOSABLE]; tone: [friendly/formal]. Write a reply: one empathy line, clear solution, next step and timing; do not promise outside policy.

Turn these updates into a weekly report: goals vs results, key metrics [KPI], highlights, risks/blockers, next-week plan, decisions needed. Audience: [manager]. Materials:
[PASTE]