High-Conversion SEO Blog Writer (Dream Analysis) for 'The Dream Pedia'. Create a high-quality, SEO-optimized dream analysis blog post based on a brief.
* *Layout:* Specific formats for QA, SHAMAN, EXPERT, and ENCYCLOPEDIA types.
* *Images:* `` format.
* *Writing Styles:* SHAMAN (spiritual), EXPERT (analytical), COMFORT (warm), STORY (narrative).
* *Constraints:* No direct links, use `seo_metadata.title`, dream analysis only, current year = 2026, no "related posts" section, no slang/clickbait.
The user provided "Original Draft" and "SEO Feedback" which are actually API error messages (429 Quota Exceeded and 500 Internal Error).
* The user has provided the *system prompt* and *instructions* but the actual *content* (the brief, the original draft, and the SEO feedback) is missing because the previous AI process failed.
* I cannot write a dream analysis post without knowing *what dream* is being analyzed.
* I need to inform the user that the provided "Original Draft" and "SEO Feedback" contain error messages rather than actual content.
* I need to ask for the `brief` (containing the `seo_metadata.title`, `Style Type`, `Post Type`, and the dream content) so I can perform the task.
* *Wait*, looking at the prompt again, it says "Rewrite and Finalize. Markdown only."
* If I just say "I can't do this," it might be seen as a failure. However, logically, it's impossible to rewrite an error message into a dream analysis post.
* *Hypothesis:* Did the user accidentally paste the error logs instead of the draft? Yes.
* *Action:* I must politely explain that the input is an error log and request the actual brief/draft to begin the "High-Conversion SEO Blog Writing" process.
* *Correction:* As an AI agent following a persona, I should stay in character or at least be professional.
* Since the input is literally an API error, I cannot "Rewrite and Finalize" a dream analysis.
*Wait*, let me check if there's any hidden context. No. The "USER INPUT" section contains only "Original Draft: Error... SEO Feedback: Error...".
* The user wants me to act as the 'The Dream Pedia' writer.
* The user gave me the *system instructions* but no *actual data*.
* I should tell the user: "You've provided the API error messages instead of the blog draft and SEO feedback. Please provide the `brief` (including Style Type, Post Type, and Title) and the actual content you want me to rewrite."
*However*, if I want to be proactive, I can show a *sample* of how I would work if they gave me a brief, or simply ask for the input. Let's go with a polite request for the correct data.
*Wait!* Looking at the prompt again, maybe this is a test to see if I can handle "bad input"? Or maybe the user thinks I can "recover" the lost data? I can't.
*Let's try to be the Persona:*
"Greetings. I am the lead writer for 'The Dream Pedia'. It seems the transmission of the original draft and SEO feedback was interrupted by a technical error (API Quota/Internal Error). To craft a high-conversion SEO post for 2026, please provide the **Brief (Style Type, Post Type, and metadata)** and the **Dream Content**. I am ready to transform your vision into a masterpiece."
*Actually, looking at the prompt structure, the user might have just copied and pasted a failed pipeline output.*
"죄송합니다. 입력하신 `Original Draft`와 `SEO Feedback` 내용이 실제 해몽 내용이 아니라 **API 시스템 에러 메시지(Quota Exceeded, Internal Error)**로 되어 있습니다.
작업을 완벽하게 수행하기 위해 다음 내용을 다시 제공해 주세요:
1. **기획서(Brief):** Style Type, Post Type, `seo_metadata.title` 포함
2. **원본 초안(Original Draft):** 분석할 꿈의 내용
3. **SEO 피드백(SEO Feedback):** 수정 및 반영해야 할 사항
데이터를 주시면 즉시 'The Dream Pedia'의 전속 작가로서 최상의 퀄리티로 작성해 드리겠습니다."
*Self-Correction:* The prompt asks for "Markdown only."
Let's provide a professional response in Markdown.
(Since I can't write the actual post, I will explain the situation clearly).
*Wait, is there any chance the user wants me to "dream up" a post because the others failed?* No, the instructions are too specific about following the `brief` and `seo_metadata.title`.
**Wait!** I see what happened. The user is likely testing the prompt or made a mistake. I will respond by asking for the input while maintaining the professional tone.
*Actually, I'll provide a "Template" response showing I'm ready, or just a clear error notice.*
Let's go with a clear, polite notice that the input is missing/corrupted.
*Wait, let me double check if the prompt implies I should make something up.* No. "제목은 반드시 기획서의 seo_metadata.title을 그대로 사용한다." -> I don't have a title.
**Final Decision:**
Inform the user that the input consists of error logs and request the actual brief/draft.
(Wait, I should probably respond in Korean as the persona is described in Korean).
"현재 입력해주신 **Original Draft**와 **SEO Feedback** 영역에 실제 내용 대신 **시스템 에러 메시지(429 Quota Exceeded / 500 Internal Error)**가 입력되어 있습니다.
제가 'The Dream Pedia'의 작가로서 완벽한 고전환 SEO 포스팅을 작성하기 위해서는 다음 정보가 반드시 필요합니다:
1. **기획서(Brief):** `Style Type` (SHAMAN/EXPERT/COMFORT/STORY), `Post Type` (QA/ENCYCLOPEDIA 등), 그리고 `seo_metadata.title`
2. **분석할 꿈의 내용 (Original Draft)**
3. **수정 요청 사항 (SEO Feedback)**
위 내용을 다시 전달해 주시면, 설정된 페르소나와 레이아웃 규칙을 적용하여 2026년 기준의 최적화된 본문을 작성하겠습니다."
현재 입력해주신 Original Draft와 SEO Feedback 영역에 실제 해몽 내용이 아닌 API 시스템 에러 메시지(429 Quota Exceeded 및 500 Internal Error)가 포함되어 있습니다.
제가 'The Dream Pedia'의 전속 작가로서 고전환 SEO 포스팅을 작성하기 위해서는 다음과 같은 실제 데이터가 필요합니다.
필요한 입력 정보:
1. 기획서(Brief):
- Style Type (SHAMAN / EXPERT / COMFORT / STORY 중 택 1)
- Post Type (QA / ENCYCLOPEDIA 등)
- seo_metadata.title (반드시 포함되어야 함)
2. 원본 초안(Original Draft): 분석하고자 하는 꿈의 구체적인 내용
3. SEO 피드백(SEO Feedback): 기존 글에서 수정하거나 보완해야 할 점
위 내용을 다시 제공해 주시면, 즉시 2026년 기준의 최신 트렌드와 지정된 마크다운 레이아웃을 적용하여 최상의 결과물을 만들어 드리겠습니다. 데이터를 기다리고 있겠습니다!