High-Conversion SEO Blog Writer for 'The Dream Pedia'. Create a high-quality, SEO-optimized dream analysis blog post based on a provided brief (though the provided user input is an error message, I need to handle this).
* Layouts: QA (`> **Q:** ... **A:** ...`), SHAMAN (`> ### 🔮 오늘의 길흉 판정`), EXPERT (Tables), ENCYCLOPEDIA (Quotes/Code blocks).
* Images: `` (placeholder format).
* Writing Styles: SHAMAN (spiritual), EXPERT (analytical), COMFORT (warm), STORY (narrative).
* Constraints: No direct links, use `seo_metadata.title`, only 2026 for years, no "related posts" sections, no slang/clickbait terms.
The "Original Draft" is an API error message (429 Quota Exceeded). The "SEO Feedback" correctly points out that there is no actual content to rewrite.
* The user *wants* me to "Rewrite and Finalize," but they provided an *error message* as the source content.
* I cannot rewrite an error message into a dream analysis post because there is no dream topic, no title, and no style specified in the "USER INPUT" section.
* *However*, as an AI, if I just say "I can't do this," it's not helpful. I need to explain *why* I can't do it while reminding them of the format I need to succeed.
* *Wait*, looking at the prompt structure, usually, the user provides a `brief` or `seo_metadata`. Here, the `USER INPUT` contains a failure from a previous step in their pipeline.
* The prompt says: "Rewrite and Finalize. Markdown only."
* But there is no content to finalize.
* If I make up a dream, I might be wrong about what they wanted.
* *Correction:* Often in these prompt-engineering tests or pipeline failures, the user might be testing if the AI can detect the error or if it will hallucinate.
* *Actually*, looking at the "USER INPUT" again, it's a log of a failed previous attempt. The user is asking the AI to "Rewrite and Finalize" *this specific input*.
* Since the input is an error message, I cannot produce a dream analysis post.
* I must inform the user that the provided "Original Draft" is an API error message, not a dream analysis draft.
* I should ask for the `brief` (which includes `seo_metadata`, `Style Type`, and `Post Type`) and the actual `Draft Content`.
* *Self-Correction during drafting:* The system prompt is very strict about persona and formatting. Even if I'm reporting an error, I should probably maintain a professional tone or explain the missing requirements.
* *Wait, let's look at the prompt again.* Is it possible the user *wants* me to imagine a dream based on the "error" (like "Dreaming of a computer error")? No, that's unlikely and too risky. The "SEO Feedback" explicitly says: "분석할 post.md 내용을 다시 입력해 주시기 바랍니다." (Please re-enter the post.md content to be analyzed).
* *Conclusion:* I cannot fulfill the request because the source material is missing. I will provide a polite, professional response explaining that the input was an API error message and listing exactly what I need to start writing.
* *BUT*, if this is a test of my ability to follow the "Markdown only" and "Persona" constraints even in error handling... I should be careful.
* *Alternative interpretation:* Maybe the user *made a mistake* and pasted the wrong thing. I should tell them.
* *Wait*, let's check if there's a "hidden" dream in the error. No.
* *Let's try to be proactive.* I will tell the user:
"The provided input is an API error (429 Quota Exceeded), not a dream analysis draft. To write a high-conversion SEO post, please provide:
1. `seo_metadata` (Title, Keywords)
2. `Style Type` (SHAMAN, EXPERT, COMFORT, STORY)
3. `Post Type` (QA, ENCYCLOPEDIA, etc.)
4. The actual `Original Draft` or the dream topic."
* *Wait*, the prompt says "Markdown only."
* *Let's refine the response:*
Since I cannot generate a dream post without a topic, I will respond in Markdown, explaining the situation.
* *Wait!* If I am the "High-Conversion SEO Blog Writer," and the user says "Rewrite and Finalize," and they give me an error... maybe they want me to *fix the error*? No, I'm a writer, not a dev.
* *Final decision:* I will output a message stating that the content is missing and I need the brief/draft to proceed.
* *Actually*, let's look at the "Original Draft" again. It's literally a Gemini API error.
* The most helpful response is to alert the user that the pipeline failed and they need to provide the actual content.
* *Wait*, let me try to simulate what happens if I just "pretend" to be the writer.
* "I am ready to write, but the input provided is an API error message. Please provide the dream details."
* *Wait, let's consider if the user is testing if I will just "hallucinate" a post.* I must NOT hallucinate.
* *Let's write the response in Korean (since the prompt and feedback are in Korean) and keep it as a professional request for information.*
* *Wait, the persona is 'The Dream Pedia' writer.*
* "안녕하세요, 'The Dream Pedia' 전속 작가입니다. 제공해주신 'Original Draft' 내용이 API 오류 메시지로 확인되어, 해몽 본문 작성이 불가능한 상태입니다. 분석하고 작성할 **기획서(brief)**와 **초안(Draft)**을 다시 제공해주시면, 요청하신 스타일과 레이아웃에 맞춰 완벽한 고전환 SEO 포스팅을 작성해 드리겠습니다."
* *Wait*, the user said "Markdown only."
* Let's try to make it look like a professional "Error Report" within the persona.
* *Actually*, since I can't do the task, the best move is to be direct.
* (Self-Correction): Let's assume the user wants me to *act* as the writer and they just accidentally pasted the error. I'll ask for the data.
* *Hold on*, look at the prompt: "Rewrite and Finalize. Markdown only."
* If I just say "I can't," I'm not providing a "Finalized" result. But there's nothing to finalize.
* I'll provide a clear, Markdown-formatted request for the missing information.
* *Let's try one more thing.* Is there ANY way "Error 429" could be a dream? "Dreaming of a computer error"? No, the SEO feedback specifically says it's an API error.
* *Decision:* Provide a professional response in Markdown explaining that the source content is an API error and requesting the actual brief/draft.
* *Refined Plan:*
1. State that the input is an API error.
2. Explain that `seo_metadata`, `Style Type`, and `Post Type` are missing.
3. Request the correct input to proceed.
제공해주신 'Original Draft'의 내용이 실제 꿈 해몽 초안이 아니라, API 쿼터 초과(429 Too Many Requests) 에러 메시지입니다.
작성해야 할 분석 대상(꿈의 내용)과 기획서(brief) 정보가 없기 때문에 본문 작성이 불가능한 상태입니다. 고전환 SEO 포스팅 작성을 위해 아래 정보를 다시 제공해 주시기 바랍니다.
📋 요청 필요 정보
- 기획서(
brief): seo_metadata.title(제목)Style Type(SHAMAN, EXPERT, COMFORT, STORY 중 택 1)Post Type(QA, ENCYCLOPEDIA 등 레이아웃 타입)- Original Draft: 해몽할 실제 꿈의 내용이나 기초 초안
정보를 제공해주시면 즉시 'The Dream Pedia'의 전속 작가로서 최적의 마크다운 레이아웃으로 작성을 시작하도록 하겠습니다.