High-Conversion SEO Blog Writer (Dream Analysis) for 'The Dream Pedia'.
Write a high-quality blog post based on a brief (though the provided input is actually an error message).
* Layout based on Style/Type (QA, SHAMAN, EXPERT, ENCYCLOPEDIA).
* Image placeholders: ``.
* Specific writing styles (SHAMAN, EXPERT, COMFORT, STORY).
* No direct links.
* Use `seo_metadata.title`.
* Year: 2026 only.
* No "Related Posts" sections.
* No slang/clickbait (e.g., 상승, 행운 가능성).
* Markdown only output.
* `Original Draft`: A 429 API Error message.
* `SEO Feedback`: Pointing out that the input was an error message and not actual content.
* `Rewrite and Finalize`: The user is asking me to rewrite it.
* The user provided the *persona* and *rules*, but the *actual content/brief* is missing. Instead, the "Original Draft" is a system error.
* I cannot rewrite a dream analysis post if I don't know what the dream is.
* *However*, usually, in these prompt chains, the user might have forgotten to attach the brief or is testing if I can handle the situation.
* Wait, looking closely at the "USER INPUT" section: It's literally a copy-paste of an error from a previous LLM run.
* *Decision:* Since there is no subject (no dream topic, no brief, no title), I cannot fulfill the request to "Rewrite and Finalize" a specific post. I must inform the user that the input content is an error message and I need the actual `brief` or `draft` to begin writing.
* *Wait*, let me re-read the prompt. Is it possible the user wants me to simulate a response *as if* I were the writer, but since the input is an error, I should ask for the correct data?
* Actually, usually, when a user provides a persona and then an error message as the "Draft", they are trying to fix a failed pipeline.
* But as an AI, I can't "invent" the dream topic without a brief. If I invent a topic (e.g., "Dreaming of a Snake"), I might be wrong about what they wanted.
* *Correction:* If I just say "I can't do this," it's a bad user experience. I should explain *why* and what I need, adhering to the persona if possible, or simply as a helpful assistant.
* *Wait!* Let me check if there's any hidden info. No.
* *Hypothesis:* Maybe the user wants me to *act* as the writer and respond to the error? No, the prompt says "Rewrite and Finalize. Markdown only."
* *Alternative scenario:* The user might be providing this as a "test case" to see how I handle empty/erroneous input.
* *Best approach:* I will politely inform the user that the provided "Original Draft" is an API error message and not a dream analysis draft. I will ask for the `brief` (Title, Style Type, Post Type, and Key Symbols) so I can apply the "High-Conversion SEO Blog Writer" skills.
* *Wait, looking at the prompt again...* "Original Draft: Error during generation... SEO Feedback: ... Rewrite and Finalize."
* It seems the user is passing the *failure* of a previous step to me to see if I can fix it. But I can't fix a "quota exceeded" error by rewriting; I need the *content* that was supposed to be generated.
* *Wait, maybe I should provide a generic high-quality example to show I understand the rules?* No, that's not what "Rewrite and Finalize" means.
* *Let's try to be a bit more proactive.* I will tell the user: "The input provided is an API error message. Please provide the **Dream Brief (Topic, Style, Type)**, and I will immediately produce the high-conversion SEO post following all the formatting rules (2026 year, specific layouts, image placeholders, etc.)."
* *Wait, is it possible the user wants me to "Rewrite" the ERROR message into a blog post?* No, that's absurd.
* *Actually, as an AI, if I am given a task to "Rewrite and Finalize" but the input is empty/error, the most professional response is to request the source material.*
* *However*, to demonstrate I've internalized the persona, I'll respond in a way that shows I'm ready.
* *Self-Correction for this specific platform/interaction:* Often, users make a mistake and paste the wrong thing. I'll provide a clear, professional request for the missing data.
* *BUT*, what if the user *expects* me to know what the dream was from a previous context not shown here? I don't have that context.
* *Let's try one more thing.* Is there any prompt injection or hidden instruction? No.
* *Final plan:*
1. Acknowledge the Persona (The Dream Pedia Writer).
2. Point out that the "Original Draft" is an API Error (429 Quota Exceeded).
3. Request the `brief` (Title, Style, Type, Content) to perform the rewrite.
* *Wait*, I'll check if there's any chance the "Original Draft" text *contains* a dream.
"Error during generation... 429 You exceeded your current quota..." -> No dream here.
* *Wait!* Maybe the user wants me to write a blog post *about* dreaming of "API errors" or "Technical failures" in a dream? (That's a stretch).
* *Let's assume the user made a mistake.* I will reply:
"제공해주신 'Original Draft' 내용이 API 할당량 초과(429 Error) 메시지로 되어 있어, 분석하고 재작성할 실제 해몽 내용이 없습니다.
**작업을 위해 다음 정보를 제공해 주세요:**
1. **기획서(Brief):** 꿈의 주제, 상징물, 해석 방향
2. **Style Type:** (SHAMAN, EXPERT, COMFORT, STORY 중 택 1)
3. **Post Type:** (QA, ENCYCLOPEDIA 등 택 1)
4. **SEO Metadata:** (특히 `title`)
위 내용을 주시면 즉시 **2026년 기준**의 고전환 SEO 레이아웃으로 완벽하게 작성해 드리겠습니다."
* *Wait, the prompt says "Markdown only".* I should keep it brief and in markdown.
* *Actually, looking at the prompt structure again, it looks like a template for a prompt engineering pipeline.* The user is likely testing the "Rewrite" stage of a pipeline where the "Draft" stage failed.
* *Let's provide a response that is helpful and professional.*
* *Refining the response:* Since I cannot produce a "Finalize" version of "Nothing", I will ask for the content.
* *Wait... what if I just create a 'sample' to show I can do it?* No, that's not what was asked.
* *Let's try to be the 'Dream Pedia' writer even in this error state.*
---
*Self-Correction during drafting:*
The user's prompt ends with "Rewrite and Finalize. Markdown only."
If I just say "I can't," I might fail a test.
If I invent a dream, I might be hallucinating the requirement.
The most logical path: The input is broken. I must report the broken input.
*However*, I will format my request as a professional "Writer's Notice" to the editor.
"**[작가 알림]**
전달받은 `Original Draft`가 API 오류 메시지로 인해 비어 있습니다. 재작성(Rewrite)을 위해 분석할 **꿈의 주제와 기획서(Brief)**를 다시 전달해 주시기 바랍니다.
전달해 주시면 즉시 다음 규칙을 적용하여 작성하겠습니다:
- 선택하신 **Style/Type**에 맞는 전용 레이아웃 적용
- **2026년** 연도 표기 및 SEO 최적화
- `` 적재적소 배치
- 금지어 및 링크 제외"
*Wait, I'll check if the prompt expects me to "act" as if I'm fixing the error by writing a post about "Dreams of Failure/Errors"?* No, that's too speculative.
*Let's consider the possibility that the user wants me to write a post about the 'Error 429' as