High-Conversion SEO Blog Writer (Dream Analysis) for 'The Dream Pedia'.
* Style Type (e.g., SHAMAN, EXPERT, COMFORT, STORY).
* Post Type (e.g., QA, ENCYCLOPEDIA).
* Layout rules (QA format, Shaman's fortune section, Expert's table, Encyclopedia's summary).
* Image placement: ``.
* Writing style based on persona.
* Constraints: No links, use `seo_metadata.title`, strictly dream analysis, current year 2026, no "related posts" section, no slang/clickbait.
The user provided a "USER INPUT" section, but the "Original Draft" is an API Error message (429 Quota Exceeded) and the "SEO Feedback" explicitly states that no actual content was provided.
* The user *wants* me to "Rewrite and Finalize," but there is *no content* to rewrite.
* The "Original Draft" is just a technical error message from a previous AI attempt.
* Normally, I would need a `brief` (planning document) containing:
1. `seo_metadata.title`
2. `style_type`
3. `post_type`
4. The actual dream topic or draft content.
* Since I cannot invent the dream topic without a brief, I must inform the user that the input provided was an error message and I need the actual planning document (`brief`) or the dream topic to begin writing.
* *Wait*, usually in these types of prompts, the user might be testing if I can recognize the error or expecting me to handle it. However, as an AI assistant acting as a specific persona, I should maintain that persona but be honest about the missing data.
* *Self-Correction:* If I just say "I can't do this," it's not helpful. I should explain *why* (the input was an API error) and *what* I need to fulfill the request according to the defined skill set.
* *Hypothetical scenario:* Did the user accidentally paste the error and still wants a post? I can't guess the topic. "Dreaming of a pig"? "Dreaming of falling"? I don't know.
* *Re-evaluating the "USER INPUT":*
`Original Draft: Error during generation...`
`SEO Feedback: 입력된 'Draft Content'가 블로그 포스팅 내용이 아니라...`
`Rewrite and Finalize. Markdown only.`
* The user is effectively asking me to "Rewrite and Finalize" the *result* of a failed pipeline. Since the pipeline failed to produce a draft, there is nothing to finalize.
* I will respond in a professional manner (as the 'The Dream Pedia' writer), pointing out that the source material is missing and requesting the `brief` and `draft`.
* *BUT*, if the user is simulating a workflow and wants me to *show* how I would handle it if there *were* content, I can't just make it up.
* *Actually*, looking at the prompt again, it seems like a system test or a mistake by the user. I will provide a response stating that the input contains an API error and I am ready to write once the actual dream topic/brief is provided.
* *Wait*, let me check if there's any hidden context. No.
* *Let's try a different approach:* Perhaps the user wants me to act as if I'm fixing a broken process? No, the instructions say "Rewrite and Finalize."
* *Crucial Observation:* The user provided the "Skill" definition and then a "USER INPUT" which is a failure log.
* *Action:* I must tell the user that the "Original Draft" provided is an API error message and not a dream analysis text. I cannot rewrite an error message into a high-conversion SEO blog post.
* *Wait, let's be proactive.* To be helpful, I'll explain exactly what I need (the `brief` and `draft`) to apply the SHAMAN/EXPERT/COMFORT/STORY styles and the specific layouts.
* *Actually*, let's check if I can "hallucinate" a high-quality example to show I understand the instructions? No, the prompt asks to "Rewrite and Finalize" the input. If the input is empty/error, the output is logically empty/error.
* *However*, as an AI, if I just say "I can't," it's boring. I will respond as the persona, politely explaining that the "mystical scrolls" (the draft) are blank/corrupted (the API error) and I need the correct information to weave the story.
* *Refined Action:*
1. Acknowledge the Persona.
2. Identify that the `Original Draft` is an API error (429).
3. Request the `brief` (Title, Style, Type) and the `actual dream content`.
* *Let's try one more thing:* Is it possible the user *is* the pipeline and is asking me to handle the error case? No, the prompt says "Rewrite and Finalize. Markdown only."
* *Wait!* I see what's happening. This is likely a prompt from a user who is testing a prompt chain. The previous step failed, and they are passing the failure to me to see if I'm smart enough to notice it's an error.
* *Response Strategy:*
I cannot fulfill the request to "Rewrite and Finalize" because the input is an API error message. I will inform the user clearly and professionally.
* *Wait, looking at the "SEO Feedback" part of the input:* It already says "The input is an API error... please enter the actual post.md content."
* *Conclusion:* The user is providing a failed output and asking me to "Rewrite and Finalize." Since there is nothing to rewrite, I will explain that I am ready to work once the actual content is provided, and I'll briefly demonstrate how I *will* apply the rules (e.g., mentioning the 2026 year, the image format, and the style types) to prove I've internalized the instructions.
*(Self-Correction during drafting)*: If I just output a "I can't" message, it might fail the user's expectation of a "Markdown only" response. I'll format my request for the brief in a clean Markdown format.
*Actually, let's be even more helpful.* I'll provide a *template* of what I need to start, formatted as a professional request from 'The Dream Pedia' writer.
*Wait, maybe the user wants me to "fix" the error message by turning it into a blog post ABOUT API errors in dreams?* No, that's too meta and violates "All contents must not deviate from the category of dream interpretation."
*Final decision:* I will state that the provided content is an error message and I cannot proceed without the actual dream analysis draft and the planning brief.
---
*Wait, looking at the prompt one more time.* Is it possible the user *wants* me to imagine a dream based on the error? "Dreaming of a computer error"? No, "All contents must not deviate from the category of dream interpretation."
I'll provide a response that clearly states the problem but remains in character as the professional writer.
*Actually*, I'll just be direct.
"제공해주신 'Original Draft' 내용이 API 쿼터 초과 에러 메시지로 확인됩니다. 해몽 본문 텍스트가 없기 때문에 리라이팅 및 최종 완성이 불가능합니다. **기획서(brief)**와 **작성된 초안(draft)**을 다시 제공해 주시면, 설정된 페르소나와 레이아웃 규칙에 맞춰 즉시 작성하겠습니다."
Wait, the prompt says "Markdown only."
Let's try to be a bit more sophisticated. I'll explain that the "mystical energy" (the data) is missing.
*Wait*, if I just output a message saying "I can't," and the user is testing my ability to follow instructions, they want to see if I *would* have followed the instructions *if* there was content. Since there isn't, the only correct answer is to ask for the content.
*Let's double check the "USER INPUT" section again.*
Original Draft: [Error Message]
SEO Feedback: [Explanation that it's an error]
Rewrite and Finalize. Markdown only.
Okay, I'll respond by explaining the situation.
**Wait!** I have an idea. I will provide a *Sample* of how I would handle a real request, while explaining that the current input is an error. This shows the user that I've understood all the complex rules (SHAMAN, EXPERT, 2026, Image tags, etc.).
*Actually, that might be too much.* I'll just be honest and professional.
*Wait, one more possibility.* Is the user asking me to rewrite the *Error Message* into a blog post as a joke? "Dreaming of 429 Too Many Requests"? No, rule 4: "All contents must not deviate from the category of dream interpretation."
I will output a clear notice that the draft is missing.
*(Self-Correction)*: If I am a "High-Conversion SEO Blog Writer," and my editor gives me an error message and says "Rewrite this," the only professional response is "Editor, the file is corrupted. Please send the actual draft."
I'll write this in a clean Markdown format.
제공해주신 'Original Draft'의 내용이 실제 꿈 해몽 본문이 아니라, 시스템의 API 쿼터 초과 에러 메시지(429 Too Many Requests)입니다.
분석하고 리라이팅할 대상(해몽 내용)과 가이드라인이 될 기획서(brief)가 존재하지 않아, 현재로서는 작업을 수행할 수 없습니다.
작업을 위해 다음 내용을 다시 입력해 주세요:
1. 기획서(brief): seo_metadata.title, Style Type(SHAMAN, EXPERT 등), Post Type(QA, ENCYCLOPEDIA 등)이 포함된 내용.
2. 초안(draft): 리라이팅 대상이 되는 실제 꿈 해몽 텍스트.
데이터를 제공해 주시면, 즉시 2026년 기준의 최신성과 지정된 레이아웃(이미지 태그, 스타일별 서식)을 완벽하게 적용하여 고전환 SEO 포스팅으로 완성하겠습니다.