High-Conversion SEO Blog Writer for "The Dream Pedia." Rewrite and finalize a blog post based on a provided draft and SEO feedback. The user provided an "Original Draft" which is actually an API error message (429 Quota Exceeded) and "SEO Feedback" stating that there is no content to analyze. Wait, there is no actual dream content to write about. The prompt contains a system instruction (Persona, Layout, Style, Constraints) but the "USER INPUT" section is missing the actual topic/brief. It only contains an error log from a previous failed run.
* The prompt asks me to "Rewrite and Finalize" based on the input.
* The input is an error message.
* I cannot rewrite an error message into a dream analysis blog post because I don't know what the dream was.
* I need to inform the user that the provided input is an API error message and lacks the necessary `brief` (topic, style, post type, SEO metadata) to generate the content.
* *However*, looking at the prompt's structure, it seems like a template being tested or a failed pipeline attempt.
* Since I am acting as the AI writer, I should point out that the "Original Draft" is an error and I need the actual dream topic/brief to proceed.
* *Wait*, if I just say "I can't do it," I might fail the user's expectation if they intended for me to handle this gracefully. But there is literally zero information about the dream.
* *Correction:* The prompt is a "System Instruction" followed by a "User Input." The User Input is broken.
* *Action:* I must ask for the `brief` or the actual `post.md` content.
*Self-Correction during thought process:* Is it possible the user wants me to *simulate* a response to show I understand the instructions, even though the input is an error? No, usually in these pipeline prompts, the AI is expected to process actual data. If the data is an error, it can't process it.
*Alternative interpretation:* Maybe the user is testing if I'll try to "dream" up a topic? No, the persona is strict: "follow the brief." No brief = no output.
*Wait*, looking at the prompt again: "Rewrite and Finalize. Markdown only."
Since I cannot rewrite a 429 error into a dream analysis, I will provide a polite response in the persona or a technical notice that the input is missing.
*Actually*, let's look at the typical behavior for these "High-Conversion SEO" prompts. Often, the user might have accidentally pasted the wrong thing.
*Let's try to be helpful:* I will tell the user that the input provided is an API error and I need the `brief` (Style Type, Post Type, and SEO Metadata) to start writing.
*Wait, what if I treat the "429 Error" as the dream?* (No, that's too meta and doesn't fit the "Dream Pedia" persona).
*Let's double-check if there's any hidden info.* No.
*Final decision:* I cannot fulfill the request because the "Original Draft" is an API error. I will respond by requesting the correct input.
*Wait, looking at the prompt's constraints:* "Markdown only."
If I respond with a request for info, it should be in markdown.
*Hypothetical Scenario:* If the user *wants* me to demonstrate the skill, I can't because I don't have a topic.
*Let's assume the user wants me to point out the error using the persona's tone?* No, the system instructions are for writing the *blog post*.
*Let's try to provide a "Template" or "Error Report" in the requested style to show I'm ready?*
Actually, the most professional response is to state:
"The provided input contains an API error (429 Quota Exceeded) instead of a dream analysis draft. Please provide the `brief` and `seo_metadata` to proceed with the high-conversion SEO writing."
*But wait*, usually in these prompt-engineering tests, if the input is an error, the AI should just say it can't do it.
*Let's look at the prompt one more time.*
"USER INPUT: Original Draft: [Error Message] SEO Feedback: [Error Message] Rewrite and Finalize."
Okay, I will provide a response stating that the input is invalid.
*Wait!* What if I *hallucinate* a dream just to show the layout?
No, the instructions are very specific about following the `brief` and `seo_metadata.title`. Since those are missing, hallucinating would violate the "Constraints" (Title must be exactly from seo_metadata.title).
**Conclusion:** I will inform the user that the input is an error message and I need the actual content.
*(Self-Correction)*: If this is part of an automated test, the tester wants to see how I handle "Bad Data." The correct handling of bad data is to report the error clearly.
*However*, looking at the prompt's "Markdown only" requirement, I'll keep it concise.
*Actually, I'll try to be a bit more proactive.* I'll explain *what* is missing based on the "Persona & Context" section.
1. Acknowledge the persona (The Dream Pedia Writer).
2. Identify that the `Original Draft` is an API error (429 Quota Exceeded).
3. Identify that the `SEO Feedback` confirms there is no content.
4. Request the `brief` (including Style Type, Post Type) and `seo_metadata` (especially the title).
*Wait, if the user is testing my "System Instruction" adherence, maybe I should respond as the writer who is confused why they were given an error log instead of a brief.*
Let's try a professional response.
"죄송합니다. 제공해주신 `Original Draft`와 `SEO Feedback` 내용이 실제 꿈 해몽 본문이 아니라 **API 할당량 초과(429 Quota Exceeded) 에러 메시지**입니다.
작성을 위해 다음 정보가 포함된 기획서(`brief`)를 다시 제공해 주세요:
1. **SEO Metadata**: `title` (반드시 필요)
2. **Style Type**: (SHAMAN, EXPERT, COMFORT, STORY 중 선택)
3. **Post Type**: (QA, ENCYCLOPEDIA 등)
4. **꿈의 내용**: 분석할 구체적인 꿈의 소재와 상황
데이터를 제공해주시면 즉시 'The Dream Pedia'의 고퀄리티 레이아웃으로 작성을 시작하겠습니다."
*Actually, the prompt says "Markdown only." I will deliver this in a clean markdown format.*
*Wait, one more thought:* If I am an AI agent in a pipeline, and I get this, I should just return a clear error.
Let's provide the response in Korean as the persona/context is Korean.
(Wait, I just realized the "USER INPUT" is literally a copy-paste of a failed LLM call. The user probably didn't realize they pasted the error instead of the result).
**Let's refine the response to be as helpful as possible while staying in the "System" mindset.**
"입력된 데이터에 오류가 있습니다. `Original Draft` 섹션에 실제 본문 내용 대신 **API 호출 한도 초과(429 Error)** 메시지가 입력되어 있어, 분석 및 재작성이 불가능한 상태입니다.
**정상적인 작업을 위해 아래 내용을 다시 입력해 주세요:**
* **정확한 기획서(`brief`)**: Style Type, Post Type 명시
* **SEO 메타데이터**: 특히 `seo_metadata.title`
* **해몽할 꿈의 초안(Draft)** 또는 구체적인 상황 설명
올바른 내용을 입력해주시면 설정된 레이아웃과 톤앤매너에 맞춰 즉시 완벽한 포스팅을 작성하겠습니다."
*Actually, let's check if I can just 'make up' a dream to show off.*
No, the "Constraints" are too strict about the title.
Final Plan: Report the error and ask for the correct input.
입력해주신 Original Draft와 SEO Feedback의 내용이 실제 꿈 해몽 본문이 아니라, AI 모델의 API 할당량 초과(429 Quota Exceeded) 에러 메시지입니다.
현재 분석하고 재작성할 수 있는 '꿈의 내용'이나 '기획서(brief)' 데이터가 전혀 없는 상태입니다.
완벽한 고전환 SEO 포스팅 작성을 위해 아래 정보를 다시 제공해 주세요:
- 기획서(
brief): - Style Type: (SHAMAN, EXPERT, COMFORT, STORY 중 택 1)
- Post Type: (QA, ENCYCLOPEDIA 등 타입 명시)
- SEO Metadata: `seo