High-Conversion SEO Blog Writer for 'The Dream Pedia'. Dream Analysis/Interpretation. The user provided an "Original Draft" and "SEO Feedback" that are actually API error messages (429 Quota Exceeded and 500 Internal Error). There is no actual "brief" (Style Type, Post Type, SEO Metadata) provided in the input.
* The user input contains *no* actual content to rewrite. It contains system errors from a previous attempt at generation.
* As an AI, I cannot "Rewrite and Finalize" something that doesn't exist. I need a `brief` (the dream topic, the style, the post type, and the SEO metadata).
* *Direct approach:* Tell the user that the input is an error message and I need the actual brief to start writing.
* *Professional approach:* Acknowledge the persona but explain that the provided "Original Draft" and "SEO Feedback" are system errors, and therefore, there is no content to process.
* Wait, looking at the prompt structure again. It's a system-prompt-like setup followed by "USER INPUT".
* The USER INPUT is literally the error logs.
* Since I cannot fulfill the request without a topic, I must ask for the `brief` (Style Type, Post Type, SEO Metadata, and the dream topic).
* *Self-Correction/Alternative:* Is the user testing if I can handle "broken" inputs? Or did they accidentally paste the error log?
* Regardless, I cannot invent a dream topic and a style without instructions, as the persona requires adhering to a *specific* `brief`.
* "I'm ready to write as 'The Dream Pedia's' exclusive writer. However, the 'Original Draft' and 'SEO Feedback' you provided are API error messages (429 and 500 errors), not actual content. Please provide the `brief` including the **Style Type**, **Post Type**, **SEO Metadata (Title)**, and the **Dream Topic** so I can create the high-conversion SEO post for you."
* The prompt is very strict about formatting and rules. I should maintain the professional tone of the "Dream Pedia" writer.
*(Wait, if I just say "I can't do it," it's boring. Let me double-check if there's a hidden prompt. No. It's just the error logs.)*
*Decision:* I will inform the user that the input contains only error logs and request the necessary brief to begin the task.
*Wait, let me re-read the prompt again. Maybe the user wants me to *simulate* what happens when a draft is missing? No, that's unlikely. The instruction is "Rewrite and Finalize."*
*Wait, maybe the user wants me to act as if I'm fixing the error? No, the errors are from a different AI (Gemini). I am the "High-Conversion SEO Blog Writer".*
"안녕하세요! 'The Dream Pedia' 전속 작가입니다.
보내주신 **Original Draft**와 **SEO Feedback** 내용이 실제 원고가 아닌 **API 시스템 오류 메시지(429 Quota Exceeded, 500 Internal Error)**로 확인됩니다.
작업을 시작하기 위해 아래 정보가 포함된 **기획서(brief)**를 다시 전달해 주세요:
1. **Style Type** (SHAMAN, EXPERT, COMFORT, STORY 중 선택)
2. **Post Type** (QA, ENCYCLOPEDIA 등)
3. **SEO Metadata** (특히 `title` 필수)
4. **해몽할 꿈의 주제 또는 원문 내용**
정보를 주시면 즉시 독보적인 레이아웃과 고품질의 SEO 콘텐츠로 작성해 드리겠습니다!"
*Since the user asked for "Markdown only," I will keep it concise.*
*(Self-Correction)*: Actually, looking at the prompt again, the user might be testing if I'm an agent that can handle a failed pipeline. But as a LLM, I cannot "recover" data that was never sent.
Let's provide a response that explains the situation clearly.
안녕하세요. 'The Dream Pedia' 전속 작가입니다.
전달해주신 Original Draft와 SEO Feedback의 내용을 확인하였으나, 해당 내용은 실제 원고나 피드백이 아닌 AI 시스템의 API 오류 메시지(429 Quota Exceeded 및 500 Internal Error)입니다.
작업을 완벽하게 수행하기 위해, 분석 및 작성을 위한 기획서(brief)를 다시 제공해 주시기 바랍니다. 특히 다음 항목들이 반드시 포함되어야 합니다:
- Style Type: (SHAMAN, EXPERT, COMFORT, STORY 중 선택)
- Post Type: (QA, ENCYCLOPEDIA 등 선택)
- SEO Metadata: (
title포함) - 꿈의 주제 및 분석할 내용: (해몽하고자 하는 꿈의 구체적인 상황)
위 내용을 전달해 주시면, 즉시 설정된 페르소나와 레이아웃 규칙에 맞추어 2026년 기준의 고전환 SEO 블로그 포스팅을 작성하겠습니다. 기다리고 있겠습니다!