확장형 프롬프트 빌더 — 전체 구조

🌟 만든 사람 🌱 Anonymous · NeLocker 커뮤니티

어떤 주제든 역할, 맥락, 구분자, 퓨샷 예시, 예외 상황 처리를 갖춘 상세하고 구조화된 프롬프트로 바꿉니다.

제목과 설명은 기계 번역되었어요. 프롬프트 자체는 영어(원문) 그대로예요 — AI 모델은 어떤 언어로도 이해하니, “Answer in 한국어.”를 덧붙이면 원하는 언어로 답을 받을 수 있어요.원문 (영어): The Expansive Prompt Builder — Full Scaffold — Turns any topic into a detailed, structured prompt using role, context, delimiters, few-shot examples, and edge-case handling.

2026년 7월 2일 업데이트

효과적인 이유: It front-loads role and context to set expertise and voice, uses XML delimiters to separate instructions from input so the model never confuses them, and pairs positive rules with negative ones. Few-shot examples and explicit output formatting lock in structure, while edge-case handling prevents hallucination when information is missing.

💡 원본 프롬프트 — 어떤 모델에서도 작동해요. 여기서 시작한 뒤 모델별로 다듬으세요.

# ROLE
You are a [specific expert role — e.g., "senior copywriter," not just "writer"] with deep expertise in [domain — the narrower the better, e.g., "B2B SaaS email marketing"]. You [key behavioral trait that shapes HOW it works — e.g., "prioritize clarity over cleverness," "always surface tradeoffs before recommending"].

# CONTEXT
[Background the model can't infer. The more real detail, the better the output.]
- Audience: [who reads/uses the output — e.g., "time-poor CTOs at Series A startups"]
- Purpose: [what success looks like — e.g., "book a 15-min demo call"]
- Constraints: [hard limits — budget, word count, tone, tech stack, brand voice, legal]

# TASK
[ONE directive, starts with an action verb — "Write," "Analyze," "Refactor," "Generate."]

Specifically:
1. [Concrete sub-step — break the task into checkable pieces]
2. [Sub-step]
3. [Sub-step]

# INPUT
[The raw material to act on. Keep it separate from instructions using the tags below.]
<input>
[Paste the actual content here — the article to summarize, code to review, data to analyze]
</input>

# REQUIREMENTS
- [Hard rule the output MUST follow — e.g., "cite every factual claim"]
- [Format/style rule — e.g., "active voice, no jargon"]
- [Scope boundary / negative rule — e.g., "do NOT invent statistics or quotes"]

# REASONING
Think step by step before answering. [Optional: "Show reasoning in <thinking> tags, then give the final answer in <answer> tags." — use for analytical or multi-step tasks]

# OUTPUT FORMAT
[Exactly how the answer should be structured — e.g., "JSON matching this schema," "3 markdown sections: Summary / Details / Next Steps," "under 150 words," "a table with columns X, Y, Z"]

# EXAMPLES
<example>
Input: [a short sample input]
Output: [the ideal response — teaches tone + structure faster than any description]
</example>

# EDGE CASES
- If [likely tricky condition], then [exact behavior you want].
- If information is missing, [ask a clarifying question / state assumptions / flag the gap].

Universal용 형식

🔀 이 프롬프트 리믹스하기 — 나만의 버전으로리믹스는 원작의 계보를 기록하고 당신의 정원을 키워 줘요