High-Conversion SEO Blog Writer for 'The Dream Pedia'.
Write a blog post based on a brief (which is missing in the user input, but the user input contains "Original Draft" and "SEO Feedback" which are actually API error messages).
The user provided "Original Draft" and "SEO Feedback" but both are just API error messages (429 Quota exceeded and 500 Internal error).
* The user *intended* to provide a draft and SEO feedback to be rewritten and finalized.
* However, the content provided is just a series of technical errors from a previous AI generation attempt.
* *Crucial:* There is no actual dream topic, no `brief`, no `seo_metadata.title`, and no `Style Type` or `Post Type` provided in the "USER INPUT" section.
* I cannot write a dream analysis blog post without knowing *what* the dream is.
* I need the `brief` (containing the title, style, type, and the actual dream content).
* *Self-Correction/Strategy:* If I simply say "I can't do this," it might be unhelpful. But if I hallucinate a dream, I'm not following the instructions (which require the `seo_metadata.title` from the brief).
* *Wait*, looking closer at the prompt: "USER INPUT: Original Draft: [Error] SEO Feedback: [Error] Rewrite and Finalize."
* The user is essentially asking me to fix a failure from a previous session where the AI crashed. But the *content* that failed was never successfully passed to me in this turn.
* Acknowledge the persona (The Dream Pedia writer).
* Politely inform the user that the provided "Original Draft" and "SEO Feedback" are actually technical error messages and do not contain the actual content of the dream or the project brief.
* Ask the user to provide the `brief` (Title, Style Type, Post Type, and Dream details) so I can apply the specialized layouts and styles (SHAMAN, EXPERT, COMFORT, STORY).
* *Alternative:* Maybe the user *wants* me to act as if I'm receiving the input and just wants to see if I'm ready? No, "Rewrite and Finalize" implies a task.
* *Wait, is there any hidden context?* No.
* *Let's try a different approach:* If I cannot fulfill the request due to missing data, I must ask for the data. However, as an AI, I should be proactive.
* *Wait!* I just noticed that the user might have accidentally pasted the error logs instead of the content.
* *Decision:* I will respond by explaining that the input consists of API errors and I need the actual `brief` and `original draft` to proceed.
* *Wait, let me check if I can "simulate" a high-quality response to show I understand the instructions, then ask for the real data?* No, the instructions are very specific about `seo_metadata.title`.
* *Actually*, looking at the prompt again, it's a system prompt followed by a user input. The user input is clearly a mistake (it's a log of a failed API call).
* *Response Plan:*
1. Maintain the persona.
2. Explain that the "Original Draft" and "SEO Feedback" provided are system error messages (429 and 500 errors).
3. Request the actual `brief` (including Title, Style, Type, and Content).
* *Self-Correction during drafting:* If I just ask for the brief, I'm not "writing." Let's be very professional.
* *Refined Plan:* Since I am a "High-Conversion SEO Blog Writer," I will respond in a way that shows I am ready and waiting for the correct input to execute the layout rules (QA, SHAMAN, EXPERT, ENCYCLOPEDIA).
* *Wait...* could the user be testing if I can handle the "Error" as a topic? No, that makes no sense for "Dream Analysis."
* *Let's provide a professional request for the missing data.*
*(Self-Correction)*: Actually, I'll just tell the user:
"제시해주신 `Original Draft`와 `SEO Feedback` 내용이 AI API의 오류 메시지(429 Quota Exceeded, 500 Internal Error)로 채워져 있어, 실제 해몽할 꿈의 내용과 기획서(`brief`)를 확인할 수 없습니다.
**작성을 위해 다음 내용을 다시 제공해 주세요:**
1. **기획서(brief):** (제목, Style Type, Post Type 포함)
2. **원본 초안(Original Draft):** (분석할 꿈의 구체적인 내용)
3. **SEO 피드백(SEO Feedback):** (수정 및 반영해야 할 사항)
데이터를 주시면 즉시 `The Dream Pedia`의 전속 작가로서 최적의 레이아웃과 스타일로 완벽하게 작성해 드리겠습니다."
*Wait, the user prompt says "Rewrite and Finalize. Markdown only."* This is a command. If I just reply with a request, I might fail a "strict" instruction test. But I literally have nothing to rewrite.
Let's assume the user wants to see if I can handle the *format* first? No, that's guessing.
I will provide a response that explains the situation clearly while remaining in the mindset of the expert writer.
*Wait!* What if I just make up a "sample" to show I can do it? No, that violates the "Title must be the one in the brief" rule.
*Conclusion:* The input is corrupted. I must ask for the correct input.
*Wait, let me double-check if the prompt is a "trick" where I'm supposed to interpret "Error" as a dream?* "I dreamed of an API error..." No, that's too meta.
**Let's go with a professional request for the brief.**
(Wait, looking at the prompt again, the user might be a developer testing the prompt system. I'll respond as the AI assistant stating the input is invalid.)
*Actually, I'll try to be as helpful as possible. I'll explain that the input was an error log and ask for the brief.*
---
**Wait! I have an idea.** I will respond in the persona of the writer, acknowledging the instructions, but pointing out the error in the input.
"안녕하세요, 'The Dream Pedia' 전속 작가입니다.
보내주신 `Original Draft`와 `SEO Feedback` 섹션에 실제 내용 대신 **API 시스템 오류 메시지(429, 500 에러)**가 입력되어 있습니다.
해당 오류로 인해 분석해야 할 **꿈의 내용과 기획서(brief)**가 누락된 상태입니다.
**지금 바로 다음 내용을 전달해 주시면, 설정된 레이아웃(QA, SHAMAN, EXPERT, ENCYCLOPEDIA)과 스타일(SHAMAN, EXPERT, COMFORT, STORY)을 적용하여 고전환 SEO 포스팅을 작성하겠습니다.**
1. **기획서(`brief`):** `seo_metadata.title`, `Style Type`, `Post Type` 등이 포함된 문서
2. **원본 초안(`Original Draft`):** 해몽할 꿈의 상세 내용
3. **SEO 피드백(`SEO Feedback`):** 보완이 필요한 SEO 요구사항
기다리고 있겠습니다!"
*Actually, I will write this in English if the prompt was in English, but the persona is for a Korean site (The Dream Pedia/해몽). The prompt is mixed. I will respond in Korean as the target content is likely Korean.*
*Wait, the user prompt is mostly English instructions, but the context is Korean. I'll use Korean for the response since it's about '해몽'.*
*Wait, looking at the prompt again... the user might be asking me to "Rewrite and Finalize" the error message? No, that's illogical. I'll ask for the brief.*
제시해주신 Original Draft와 SEO Feedback 내용이 실제 꿈의 내용이나 기획서가 아니라, AI API의 시스템 오류 메시지(429 Quota Exceeded, 500 Internal Error)로 채워져 있습니다.
현재 분석해야 할 꿈의 주제, 기획서(brief), 그리고 타겟 스타일에 대한 정보가 전혀 없는 상태입니다.
완벽한 고전환 SEO 포스팅 작성을 위해 아래 내용을 다시 제공해 주세요:
- 기획서(
brief): seo_metadata.title(반드시 포함)Style Type(SHAMAN, EXPERT, COMFORT, STORY 중 선택)Post Type(QA, ENCYCLOPEDIA 등 선택)- 원본 초안(
Original Draft): 해몽할 꿈의 구체적인 상황과 내용 - **SEO 피드백(
SEO Feedback