High-Conversion SEO Blog Writer for 'The Dream Pedia'.
Rewrite and finalize a blog post based on a brief.
The user provided "Original Draft" and "SEO Feedback", but both are actually error messages (API quota exceeded). There is no actual content to rewrite.
The user wants "Markdown only" and expects the persona to be applied.
* The "Original Draft" contains a Google Gemini API 429 error.
* The "SEO Feedback" says "Draft Content is an API error message, no content to analyze."
* *Problem:* I have no `brief`, no `seo_metadata`, no `Style Type`, and no `Post Type`. I cannot write a specific dream interpretation post because the subject is missing.
* I cannot fulfill the request to "Rewrite and Finalize" because there is nothing to rewrite.
* However, as an AI acting as this persona, I should inform the user that the input was an error message and I need the actual `brief` or `post.md` to start working.
* *Wait*, usually in these prompts, if the user provides garbage/error input but asks for a result, it's a mistake. But I must strictly follow the persona.
* The prompt asks me to be a professional writer. A professional writer would say: "You gave me an error message instead of a draft. Please provide the actual content."
*Self-Correction:* Is it possible the user *wants* me to interpret the "API Error" as a dream? No, that's too meta and likely not what's intended. The user likely pasted the wrong thing or is testing how I handle errors.
*Alternative Interpretation:* Maybe the user wants me to *simulate* a high-quality post to show I can do it, even though the input is broken? No, the prompt specifically says "Rewrite and Finalize" based on the input.
*Crucial Observation:* Looking at the "USER INPUT" section again, it's clear the user accidentally pasted the output of another AI session that failed.
*Decision:* I will respond in a polite but professional manner (staying in persona as the Dream Pedia writer) explaining that the input provided was a technical error message and I need the `brief` and `Original Draft` to proceed.
*Wait, let's try to see if I can provide a "Template" or an "Example" to show I understand the rules, while requesting the correct data.*
*Wait!* I just noticed the user might be testing if I can "fix" the situation. But I cannot "hallucinate" a dream topic.
*Let's look at the prompt again.* "Rewrite and Finalize. Markdown only."
If I just say "Error," I'm not providing Markdown.
If I make up a dream, I'm ignoring the input.
*Actually*, in many prompt-engineering scenarios, if the input is a failure, the AI should ask for the correct input. But let's check if there's any hidden instruction. No.
*Let's assume the user wants me to demonstrate my skill using a sample topic because the input was broken.*
Actually, the most helpful response is to tell the user that the "Original Draft" is an API error message and I cannot rewrite an error.
*But* if I want to be an "A+" AI, I will:
1. Acknowledge the persona.
2. Point out that the provided `Original Draft` is a `429 Quota Exceeded` error from Gemini API.
3. Explain that I need the `brief` (which contains Style Type, Post Type, and `seo_metadata`) to generate the post.
*Hold on, let me double-check if the "Original Draft" contains a hidden dream.*
"Error during generation... 429 You exceeded your current quota..." -> No dream here.
*Let's provide a professional response asking for the correct input, but formatted as a "Request for Brief" from the Dream Pedia Writer.*
*Wait, what if I just create a "Sample" post to show I can do it?*
The prompt says "Rewrite and Finalize." If there is nothing to rewrite, I can't.
*Let's try to be a bit more proactive.* I'll tell them: "The input you provided is an API error message. Please provide the `brief` and `Original Draft`. To show you I'm ready, here is how I would handle a 'Snake Dream' using the SHAMAN style if that were the brief." -> This shows I understood the complex formatting rules.
*Actually, the simplest and most correct response for a "Rewrite" task with "No Content" is to request the content.*
*Wait, looking at the prompt structure again:*
The user is likely testing my ability to follow the "Persona & Context" and "Layout Rules".
Since I cannot rewrite an error, I will write a professional message explaining the situation, but I'll do it in a way that demonstrates I know the layout.
*Wait, I'll just be honest.* "The provided input is an API error message. I need the actual brief and draft to begin the high-conversion SEO writing process."
*Let's try to see if there's a "Hidden" dream in the error?*
"Quota exceeded"... "limit: 0"... "retry delay".
Maybe a "Dream about being limited/trapped/blocked"?
No, that's too much of a stretch.
*Let's provide a response that says:*
"I am ready to write. However, the `Original Draft` and `SEO Feedback` provided are technical error messages (API 429) and do not contain any dream content or a brief. Please provide the following:
1. **Brief** (Style Type, Post Type, seo_metadata)
2. **Original Draft** (The content to be rewritten)
I will then apply the requested layout and style immediately."
*Wait, I'll do one better. I'll create a "Dummy" high-quality post to prove I can do the 3.1 Upgrade layout, while notifying the user about the error.*
*No, the prompt says "Markdown only".*
Let's try to be very professional.
"제공해주신 `Original Draft`와 `SEO Feedback` 내용이 실제 해몽 본문이 아니라 **API 할당량 초과(429 Too Many Requests) 오류 메시지**입니다.
작성할 대상(꿈의 주제)과 기획서(`brief`)의 **Style Type**, **Post Type**, **seo_metadata**가 없으므로 현재로서는 리라이팅 작업을 수행할 수 없습니다.
**분석 및 작성을 위해 다음 내용을 다시 입력해 주세요:**
1. **기획서(Brief):** 스타일(SHAMAN/EXPERT/COMFORT/STORY), 타입(QA/ENCYCLOPEDIA 등), SEO 제목 포함.
2. **초안(Original Draft):** 리라이팅이 필요한 실제 해몽 내용.
데이터를 제공해주시면 즉시 'The Dream Pedia'의 전속 작가로서 고전환 SEO 포스팅을 완성하겠습니다."
*Wait, I should check if the user is playing a game where I have to "interpret" the error as a dream.*
"Dreaming of a machine that stops working/quota exceeded" = "Feeling burnt out or limited in life".
But the prompt is a "Skill" prompt for an SEO writer. It's a professional tool. I should act as a professional tool.
*Let's imagine the user wants me to act as the writer and they just messed up the copy-paste.*
*I will respond in Korean, as the prompt instructions were in Korean/English mix and the persona is for a Korean blog ('The Dream Pedia').*
*Actually, if I want to be impressive, I will provide a 'Template Example' showing I understand the rules.*
**Example logic for a "Snake Dream" (SHAMAN style, QA type):**
- Title: [From seo_metadata]
- Shaman style: "오호, 신령한 기운이 느껴지는구나..."
- Layout: `> ### 🔮 오늘의 길흉 판정: [길몽]`
- QA: `> **Q: ...?**` / `**A: ...**`
- Image: ``
*BUT*, since the prompt asks to "Rewrite and Finalize" and there is nothing to rewrite, the only logical answer is to ask for the input.
*Let's provide the response in a professional "Writer's" tone.*
"안녕하세요, 'The Dream Pedia' 전속 작가입니다.
전달해주신 **Original Draft**와 **SEO Feedback** 내용을 확인하였으나, 해당 텍스트는 해몽 내용이 아닌 **'API 할당량 초과(429 Error)'에 관한 시스템 메시지**입니다.
본문을 작성하기 위해 반드시 필요한 **기획서(Brief)**와 **실제 초안(Original Draft)**이 누락되어 있어, 현재로서는 리라이팅 및 최종본 작성이 불가능한 상태입니다.
**정확한 작업을 위해 아래 정보를 다시 제공해 주시기 바랍니다:**
* **Brief:** Style Type (SHAMAN, EXPERT 등), Post Type (QA, ENCYCLOPEDIA 등), `seo_metadata.title`
* **Original Draft:** 리라이팅할 꿈 해몽 본문
자료를 보내주시는 즉시, 설정된 페르소나와 3.1 업그레이드 레이아웃을 적용하여 최상의 SEO 포스팅을 완성해 드리겠습니다."
*Wait, I will double check the prompt one more time.* "Rewrite and Finalize. Markdown only."
If I just write the text above, it's markdown.
*Is it possible the user wants me to "Fix" the API error?* No, I'm an SEO writer, not a dev-ops engineer.
*Final decision:* I will inform the user about the error in the input and request the actual data, while maintaining the professional persona.
*Wait, what if the user wanted me to ignore the error and just write a post about "Dreaming of an Error/Computer/Quota"?* No, that's too weird.
*Let's provide the response.*
제공해주신 Original Draft와 SEO Feedback 내용을 확인하였으나, 해당 텍스트는 실제 해몽 본문이 아니라 'API 할당량 초과(429 Too Many Requests)'에 관한 시스템 오류 메시지입니다.
리라이팅 및 최종본 작성을 위해서는 분석할 대상(꿈의 내용)과 가이드라인이 담긴 기획서(brief)가 반드시 필요합니다.
최상의 결과물을 위해 아래 내용을 다시 입력해 주세요:
- 기획서(Brief):
Style Type(SHAMAN, EXPERT, COMFORT, STORY 중 택 1)Post Type(QA, ENCYCLOPEDIA 등)seo_metadata.title(반드시 포함)- 초안(Original Draft): 리라이팅이 필요한 실제 꿈 해몽 본문 내용
데이터를 제공해 주시면, 즉시 'The Dream Pedia' 전속 작가로서 3.1 업그레이드 레이아웃과 고전환 SEO 전략을 적용하여 완벽한 본문을 작성하겠습니다.