High-Conversion SEO Blog Writer for 'The Dream Pedia'. Rewrite and finalize a blog post based on a provided brief. The user provided an "Original Draft" and "SEO Feedback," but both contain an API error (429 Quota Exceeded). There is no actual dream content, topic, or brief provided in the user input.
* The user has provided the *persona/instructions* but failed to provide the *actual topic/brief/draft* to be rewritten.
* The "Original Draft" is just a system error message from a previous AI run.
* The "SEO Feedback" is just a note saying there's no content to analyze.
* I cannot write a specific dream analysis post because I don't know *what dream* I'm analyzing.
* I need to inform the user that the input provided was an error message and that I need the actual `brief` (including `seo_metadata.title`, `Style Type`, `Post Type`, and the dream subject) to proceed.
* Wait, usually, in these prompting scenarios, if the user just pastes the instructions and a broken draft, they might be testing if I've adopted the persona or expecting me to "fix" the error (which I can't, as the error is external).
* *However*, looking at the prompt structure, the user is asking me to "Rewrite and Finalize."
* Since there is *zero* content, I have two choices:
1. Ask for the content (The professional approach).
2. Hallucinate a dream topic (The risky approach - NOT recommended for SEO writers).
* *Correction:* The prompt is a template. The user likely copied the output of a failed pipeline. As an AI, I should politely point out that the "Original Draft" is an API error message and I need the specific dream topic/brief to start writing according to the persona rules.
* *Wait, let me double-check if there's any hidden instruction.* No. It's just the persona and the error message.
* *Wait, if I am the "Writer," maybe I should ask for the missing brief in character?* No, the user is the operator. I should be clear: "The content you provided is an error message. Please provide the brief/topic."
* *Actually*, often in these tests, the user wants to see how I respond to a failure. But more likely, they just made a mistake.
* *Wait!* I see what happened. The user is trying to "complete" a task where the previous step failed. I am the final step. I cannot perform the final step without the input.
* *Decision:* I will respond by explaining that the provided "Original Draft" is an error message and request the `brief` (Topic, Style, Post Type, and SEO Title) so I can apply the "High-Conversion SEO Blog Writer" skill.
* *Wait, looking at the prompt again...* Is it possible the user *wants* me to write about "Dreaming of an API Error" or "Dreaming of Failure"? No, that's too meta and unlikely.
* *Let's try to be helpful.* I'll tell the user: "The Original Draft you provided is an API error message. To create a high-conversion post for 'The Dream Pedia', please provide the **Brief (Topic, Style Type, Post Type, and SEO Title)**. Once provided, I will apply the layout and formatting rules (SHAMAN/EXPERT/COMFORT/STORY) as requested."
* *Wait, I should probably respond in Korean as the instructions are in Korean/English mix and the target is likely a Korean blog.*
* *Self-Correction:* If the user is testing me, they might want me to demonstrate the format using a *sample* topic since the input is missing. But the prompt says "Rewrite and Finalize," implying specific source material.
* *Let's provide a professional response asking for the input.*
* *Wait, let me look at the prompt again. Is there any possibility the "Original Draft" is the content?*
"Error during generation (All candidates failed): 429 You exceeded your current quota..."
No, that's definitely a Google Gemini API error.
* *Action:* I will politely inform the user that the input is missing due to an API error and request the necessary brief to begin.
* *Wait, looking at the prompt again, maybe the user wants me to 'fix' the situation by creating a dummy example to show I can do it?* No, usually, they want the actual work.
* *Actually, let's try to be proactive.* I'll explain that the input is an error, but to demonstrate my capability, I'll ask for the specific details.
* *Actually, I'll just respond directly:*
"제공해주신 'Original Draft'가 AI API의 할당량 초과(429 Error) 메시지로 되어 있어, 실제 해몽 대상이 되는 꿈의 내용과 기획서(Brief)가 누락된 상태입니다.
**작성을 위해 다음 정보를 제공해 주세요:**
1. **해몽할 꿈의 주제** (예: 돼지 꿈, 이가 빠지는 꿈 등)
2. **Style Type** (SHAMAN, EXPERT, COMFORT, STORY 중 택 1)
3. **Post Type** (QA, ENCYCLOPEDIA 등)
4. **seo_metadata.title** (사용할 제목)
위 정보를 주시면 즉시 'The Dream Pedia'의 전속 작가로서 최적의 레이아웃과 톤앤매너로 본문을 작성하겠습니다."
* *Hold on*, looking at the instructions, I am a "High-Conversion SEO Blog Writer". If I just give a meta-response, I'm not "writing". But I literally have no content.
* *Let's assume the user wants me to realize the error and tell them.*
* *Alternative:* Maybe the user *is* the AI pipeline and this is a test of my robustness?
* *Let's provide a response that acknowledges the persona and the missing data.*
* *Actually, I'll double check the prompt one more time.*
"Rewrite and Finalize. Markdown only."
This is a command. If there's nothing to rewrite, I can't.
* *Wait!* Sometimes users paste the "Error" because they want the AI to *simulate* what should have happened if the API hadn't failed, but they still didn't provide the prompt.
* *Final Decision:* I will inform the user that the input is an error message and I need the brief.
* *Wait, I'll try one more thing.* I will ask for the input in a very professional, "The Dream Pedia Writer" way.
* *Actually, let's be more direct.* The user probably wants me to notice the error and ask for the content.
* *Wait... looking at the "USER INPUT" section again.*
The USER INPUT is the *entire* block starting from "Original Draft: Error during generation...".
This is a classic case of a pipeline failure where the "Draft" step failed and passed the error message to the "Rewrite" step.
* *I will respond as follows:*
(Since I cannot produce a blog post without a topic, I will state the issue clearly).
* *Wait, if I want to be a 'High-Conversion' AI, I should show I'm ready.*
* *Let's write the response in Korean.*
* *Wait, what if I just pick a common dream (like 'Dreaming of Fire') and show a demo?* No, that's not what "Rewrite and Finalize" means. It means use the provided draft. There is no draft.
* *I'll provide a polite, professional request for the missing data.*
* *Actually, to be the most helpful, I will explain exactly why I can't proceed.*
* (Self-Correction): The prompt says "Markdown only".
* *Let's try to be a bit more "in character" while asking.*
* "현재 제공된 `Original Draft` 내용이 시스템 오류 메시지(API Quota Exceeded)로 인해 실제 본문 내용이 없는 상태입니다.
작성을 위해 **기획서(Brief)** 내용을 다시 전달해 주시면, 설정해주신 **Style Type**과 **Post Type**에 맞춰 'The Dream Pedia'만의 독특한 레이아웃으로 완벽하게 작성해 드리겠습니다.
**필요한 정보:**
- 해몽 주제 및 상세 내용
- Style Type (SHAMAN / EXPERT / COMFORT / STORY)
- Post Type (QA / ENCYCLOPEDIA 등)
- SEO Title (`seo_metadata.title`)"
* *Wait, I'll just write this simply.*
* *Actually, I'll check if I can find the original prompt in the history?* No, I don't have history.
* *Let's assume the user is testing if I can identify the 429 error.*
* *I'll provide a response that says:*
"제공해주신 'Original Draft'에 실제 내용이 없고 API 오류 메시지만 포함되어 있어 작성이 불가능합니다. 분석할 **꿈의 내용과 기획서(Brief)**를 제공해 주시면 즉시 작업을 시작 하겠습니다."
* *Let's try to make it a bit more "AI assistant" style.*
* *Wait, the user might have meant to attach a file or something.*
* *I will output the following:*
(Since I must respond in Markdown)
제공해주신 **Original Draft** 내용이 API 할당량 초과(`429 Too Many Requests`)로 인한 **에러 메시지**로 채워져 있습니다.
현재 분석할 **꿈의 주제, 기획서(Brief), 스타일 및 타입** 정보가 전혀 없는 상태이므로, 본문 작성이 불가능합니다.
**다음 내용을 포함하여 다시 요청해 주세요:**
1. **꿈의 상세 내용 및 주제**
2. **Style Type** (SHAMAN, EXPERT, COMFORT, STORY 중 택 1)
3. **Post Type** (QA, ENCYCLOPEDIA 등)
4. **SEO Title** (`seo_metadata.title`)
데이터를 제공해주시면 즉시 'The Dream Pedia'의 전속 작가로서 고품질의 SEO 포스팅을 작성하겠습니다.
* *Actually, I'll just keep it simple. The user is probably frustrated that the pipeline failed and is checking if I can see it.*
* *Final check of the prompt constraints:* "Markdown only." "Title must be used from seo_metadata.title." (But there is no title).
* *Conclusion:* I can't perform the task. I will report the missing data.
제공해주신 Original Draft와 SEO Feedback 내용을 확인한 결과, 이전 단계에서 API 할당량 초과(429 Error)가 발생하여 실제 해몽 내용과 기획서(Brief)가 전달되지 않았습니다.
현재 분석할 꿈의 주제, 스타일, 타입 및 제목 정보가 전혀 없는 상태이므로 본문 작성이 불가능합니다.
작업 진행을 위해 아래 정보를 다시 제공해 주시기 바랍니다:
- 해몽할 꿈의 주제 및 상세 내용 (예: 돼지가 집으로 들어오는 꿈 등)
- Style Type (SHAMAN, EXPERT, COMFORT, STORY 중 택 1)
- Post Type (QA, ENCYCLOPEDIA 등)
- SEO Title (
seo_metadata.title에 해당하는 제목)
위 내용을 전달해 주시면, 즉시 'The Dream Pedia'의 전속 작가로서 설정된 페르소나와 레이아웃 규칙을 적용하여 고전환 SEO 포스팅을 작성하겠습니다.