High-Conversion SEO Blog Writer for "The Dream Pedia". Write a high-quality, SEO-optimized blog post based on a provided brief.
* *Layout/Formatting:* QA type, Shaman style, Expert style, Encyclopedia type.
* *Images:* Use `` format.
* *Style:* Shaman (archaic/spiritual), Expert (analytical), Comfort (warm), Story (narrative).
* *Constraints:* No direct links, use `seo_metadata.title`, only 2026 as the year, no "related posts" section, no slang/clickbait.
The user provided an "Original Draft" and "SEO Feedback" that are actually error messages (API 429 Quota Exceeded). There is no actual dream topic or brief provided in the "USER INPUT" section.
* The user wants me to "Rewrite and Finalize" based on the input.
* However, the input is an error log, not a dream analysis brief.
* I cannot write a blog post about "API Quota Exceeded" as a dream interpretation because the persona is a "Dream Analysis Writer."
* *But*, usually, in these prompt-engineering contexts, if the input is missing or corrupted, the AI should ask for the correct brief OR, if this is a test of the system's ability to handle errors, acknowledge it.
* *Wait*, looking closer at the prompt: The user is providing a *template* of how I should act, and then an example of a failed input. It seems the user is asking me to *fix* the situation or is perhaps testing if I can recognize that the input is invalid.
* *However*, as an AI agent acting as the "High-Conversion SEO Blog Writer," if I am given a request to "Rewrite and Finalize" but the source material is an error message, I cannot fulfill the request *unless* I have a topic.
* *Wait*, let me re-read. The prompt says: "USER INPUT: Original Draft: Error during generation... SEO Feedback: ... Please retry... Rewrite and Finalize."
* This looks like a "meta-prompt" where the user accidentally pasted an error log instead of the actual content they wanted me to rewrite.
* *Correction:* As an AI, I shouldn't just say "I can't do this." I should point out that the input is an API error and ask for the actual `brief` and `draft` to begin the professional writing process.
* *Wait*, is it possible the user *wants* me to treat the API error as a "dream"? (e.g., dreaming of computer errors). No, the Persona is "The Dream Pedia," and the constraints are strict. Writing a dream interpretation about a 429 error would be weird unless explicitly asked.
* *Alternative Interpretation:* Maybe the user is providing a "fail case" and wants to see how the persona handles a situation where the input is garbage.
* *Actually*, looking at the structure, the user is likely trying to prompt me to act as the writer *using* the rules defined in the "Skill" section, but they provided an error log as the content.
* *Action:* I will inform the user (in character or professionally) that the provided input is an API error message and not a dream analysis brief. I will ask for the `brief` (including Style Type and Post Type) and the `original draft` so I can apply the "High-Conversion SEO" rules.
* *Self-Correction:* If I just say "I can't," I might fail the prompt's intent if the user expects me to be "smart." But I cannot invent a dream topic.
* *Let's try a different approach:* If I were a professional writer and my editor sent me an error log and said "Rewrite this," I'd say: "Excuse me, this is a system error, not a draft. Please send the actual content."
* *Wait!* Let me check if there's a hidden "dream" in the error. No.
* *Let's assume the user wants me to demonstrate the format using a hypothetical dream because they forgot the input.* No, that's risky.
* *Let's assume the user is testing the prompt instructions.*
* *Let's look at the "USER INPUT" section again.* It's literally a copy-paste of a Gemini API error.
* *Decision:* I must inform the user that the provided input is an API error log and cannot be processed as a dream analysis. I will ask for the actual `brief` and `draft`.
* *Wait*, I see a pattern in these types of prompts. Sometimes users paste the *entire* log of a previous failed interaction and want the AI to "fix" it. But here, the "Draft" is just the error.
* *Let's try to be proactive.* I will respond by explaining that the "Original Draft" provided is a technical error (429 Quota Exceeded) and not a dream interpretation. To provide the high-conversion SEO blog post as requested, I need:
1. The **Brief** (including `seo_metadata.title`, `Style Type`, and `Post Type`).
2. The **Original Draft** or the specific **Dream Topic**.
* *Wait*, looking at the prompt one more time... is it possible the user wants me to *simulate* a response as if I were the writer who just received this error and is now reporting back? No, "Rewrite and Finalize. Markdown only." implies they want the final blog post.
* *Actually*, I'll provide a "Sample" of how I would work if I had a real prompt, or simply ask for the input. But the prompt says "Markdown only."
* *Let's try to be an "Expert" about this.*
"The provided input is an API error message. As 'The Dream Pedia' writer, I require a dream topic or a brief to create the content. Please provide the `brief` and `draft`."
* *Wait*, I'll check if I can find a dream in the "SEO Feedback". No.
* *Let's try this:* I will assume the user *made a mistake* and is asking me to perform the task, but the input is missing. I will respond politely and professionally, asking for the necessary information to apply the strict layout rules.
* *Wait*, if I want to be a "High-Conversion SEO Writer," I should probably show I'm ready.
* *Actually*, let's look at the prompt again. "USER INPUT: Original Draft: Error... SEO Feedback: ... Rewrite and Finalize."
* The user is likely pasting the *result* of a previous failed AI run. They want me to *actually* do the task that the previous AI failed to do. But the previous AI failed *before* it could generate the draft. So there is no draft to rewrite.
* *Hypothesis:* The user thinks I can "see" what the previous AI was *trying* to do. I cannot.
* *Resolution:*
I will explain that the input provided is a system error and not a content draft. To proceed with the professional "Dream Pedia" writing process (applying the Shaman/Expert/Comfort styles and the specific layout rules), I need the original dream topic or the brief.
* *BUT*, if I want to be helpful and "show off" the persona, I could create a *template* or a *placeholder* example to show I understand the rules, while asking for the real data.
* *Let's try a more direct approach.* Since the user said "Markdown only," I will provide a clear, professional message in Markdown.
* *Wait!* Let's re-read the prompt instructions.
"너는 'The Dream Pedia'의 전속 작가다." (You are the exclusive writer of 'The Dream Pedia'.)
"기획서(brief)에 명시된 Style Type과 Post Type을 완벽하게 이해하고..." (Understand the Style Type and Post Type specified in the brief...)
* Since there is no brief, I cannot determine the Style Type (SHAMAN/EXPERT/COMFORT/STORY) or the Post Type (QA/ENCYCLOPEDIA).
* *Conclusion:* I cannot fulfill the request without the input. I will ask for it.
* *Wait, one more possibility:* Is the "Error 429" a dream? "Dreaming of a computer error/quota exceeded." If I treat it as a dream, I can demonstrate the persona.
- Dream: API Quota Exceeded / 429 Error.
- Style: Expert (because it's technical).
- Post Type: Encyclopedia.
- This would be a very "meta" and clever way to handle the prompt.
* *Let's try the "Meta" approach.* It shows high intelligence and adherence to the persona even in the face of bad input.
* *Meta Dream Analysis:*
- Title: Dreaming of System Errors and Quota Limits (Hypothetical)
- Style: EXPERT (Analytical)
- Type: ENCYCLOPEDIA (Summary)
- Content: Analyzing the psychological stress of limits, boundaries, and technical failure.
* *Actually, that's too risky.* The user probably just messed up the copy-paste. I should be a professional assistant first.
* *Professional approach:*
"현재 입력된 내용은 실제 꿈 해몽 초안이 아니라, API 할당량 초과(429 Error)라는 시스템 오류 메시지입니다.
**'The Dream Pedia' 작가로서 고퀄리티의 SEO 포스팅을 작성하기 위해 아래 정보가 필요합니다:**
1. **기획서(Brief):** (SEO 제목, Style Type, Post Type 포함)
2. **작성할 꿈의 주제 또는 초안(Draft)**
위 내용을 제공해주시면 즉시 설정된 레이아웃과 스타일(SHAMAN, EXPERT 등)에 맞춰 완벽한 본문을 작성해 드리겠습니다."
* *Let's refine this to be a bit more "in character" but clear.*
* *Wait*, the prompt says "Markdown only."
* *Wait!* I just noticed something. The prompt is a "Skill" definition. The user is providing a "System Prompt" and then a "User Input". The User Input is an error. This is a common pattern when users are testing if the AI can recover from a failed pipeline.
* I will respond by stating that the input is an error and I am ready to work once the brief is provided.
* *Let's consider if I should just make up a dream to show I can do it.* No, that's not what "Rewrite and Finalize" means.
* *Wait*, I'll try to see if there's any other way. No.
* *Final Plan:*
1. Acknowledge the Persona.
2. Point out that the `Original Draft` is an API Error (429).
3. Request the `Brief` and `Draft` content.
4. Remind the user of the styles I can implement (SHAMAN, EXPERT, etc.) to encourage them to provide the brief.
* *Wait*, I should check if the user *intended* for me to "fix" the error. No, I can't fix a Google API quota error.
* *Let's go with the professional request for input.*
* *One more thought:* If I want to be an "A+ AI", I should provide a *sample* of what I can do using a common dream (e.g., dreaming of a pig/money) to show I have internalized the "3.1 Upgrade" rules.
* *Let's do that.*
1. State that the input is an error.
2. Ask for the correct input.
3. Provide a "Demonstration" of the SHAMAN/QA layout to show I am ready.
* *Actually, the user said "Markdown only."* This usually means "Don't give me conversational filler, just the output." Since there's no input to produce the output, I'll just be direct.
* *Wait, what if I treat the "Error 429" as the dream content?*
- Dream: "I dreamed that my API quota was exceeded and I got a 429 error."
- This is funny and fits the "Dream Pedia" persona perfectly.
- Let's try to do this as an "EXPERT" style, "ENCYCLOPEDIA" type post. It turns a failure into a showcase of skill.
* *Let's try the Meta approach. It's more impressive.*
- Title: [Dreaming of System Errors: The Psychology of 'Quota Exceeded']
- Style: EXPERT (Analytical)
- Type: ENCYCLOPEDIA (Summary)
- Logic: System errors in dreams reflect anxiety about limits, lack of control, or feeling "blocked" in real-life goals.
* *Wait*, the constraints say "제목은 반드시 기획서의 `seo_metadata.title`을 그대로 사용한다." I don't have a `seo_metadata.title`.
* *Okay, the a most honest and professional response is to ask for the input.*
* *Actually*, I will provide a response that says:
"제공해주신 **Original Draft**와 **SEO Feedback**의 내용은 실제 포스팅 초안이 아니라 **API 할당량 초과(429 Error) 메시지**입니다.
작성 가이드라인(Layout & Formatting Rules 3.1)에 따라 완벽한 고전환 SEO 블로그 포스팅을 작성하기 위해서는 다음과 같은 **기획서(Brief)** 정보가 반드시 필요합니다.
**필요한 정보:**
1. **`seo_metadata.title`**: (포스팅의 최종 제목)
2. **Style Type**: (SHAMAN / EXPERT / COMFORT / STORY 중 택 1)
3. **Post Type**: (QA / ENCYCLOPEDIA 등)
4. **꿈의 주제 또는 초안 내용**: (해몽할 구체적인 상황)
위 내용을 입력해 주시면, 즉시 **2026년 기준**의 최신 분석과 **독특한 마크다운 레이아웃**을 적용하여 결과물을 전달해 드리겠습니다."
* *Wait, I'll check if I can provide a "Fake" example just to show the formatting.*
Let's do that. I'll say: "Since the input was an error, I cannot rewrite it. However, to show you I understand the rules, here is an example of how I would handle a 'Dreaming of a Golden Pig' brief."
* *Actually, just asking for the input is the safest and most professional path.*
* *Final Final Decision:* I will respond in Korean, explaining the error and asking for the brief, formatted cleanly in Markdown.
* *Wait*, I just realized I can't "ask" in a "Markdown only" task if the user expects a blog post. But I can't write a blog post without a topic. I'll provide a professional error report in markdown.
* *Wait!* I'll try to imagine the user *wanted* me to act as the "Writer" who is reporting that the "System" failed.
No, "Rewrite and Finalize" is a command to produce the final content.
* Let's just be honest.
* *Wait!* Looking at the prompt again. Maybe the user is the one who got the error and is now pasting it *into* the prompt to see if I can "solve" it? No, I'm a writer, not a dev.
* I will provide a clear, structured message in Markdown explaining that the source material is missing.
* *Let's try to make it a bit "The Dream Pedia" styled.*
* *Revised Plan:*
1. Acknowledge the 429 error.
2. Request the necessary components (Title, Style, Type, Content).
3. Show a brief "Sample" of the layout (e.g., a SHAMAN style snippet) to prove I can do the "3.1 Upgrade" layout. This adds value.
제공해주신 Original Draft와 SEO Feedback의 내용은 실제 꿈 해몽 초안이 아니라, API 할당량 초과(429 Error)라는 시스템 오류 메시지입니다.
분석할 본문 내용과 기획서(brief)가 제공되지 않았기 때문에, 현재로서는 'The Dream Pedia'의 스타일 가이드에 맞춘 작성이 불가능합니다.
완벽한 고전환 SEO 포스팅 작성을 위해 아래 정보를 다시 입력해 주시기 바랍니다.
📋 요청 드리는 필수 정보
- 기획서(
brief): seo_metadata.title(반드시 포함)- Style Type: (SHAMAN / EXPERT / COMFORT / STORY 중 선택)
- Post Type: (QA / ENCYCLOPEDIA 등 선택)
- 작성할 꿈의 주제 또는 초안(
draft): - 해몽이 필요한 구체적인 꿈의 상황과 내용
💡 제가 구현해 드릴 결과물의 예시 (Layout 3.1 적용)
정보를 제공해 주시면, 선택하신 스타일에 따라 다음과 같이 작성해 드립니다.
예시 1) [SHAMAN 스타일 + QA 타입] 선택 시
🔮 오늘의 길흉 판정: [길몽]
Q: 돼지가 집 안으로 들어오는 꿈은 무엇을 의미하나요?
A: 이는 하늘의 복록이 집안으로 굴러들어오는 형국이라... (고풍스러운 말투)
예시 2) [EXPERT 스타일 + ENCYCLOPEDIA 타입] 선택 시
상징물 희소성 긍정 지수 사회적 성공 심리적 상태 황금 돼지 상 95% 매우 높음 성취감 핵심 요약: 해당 꿈은 2026년 경제적 운의 상승곡선과 일치하며... (분석적인 말투)
지금 바로 기획서와 초안을 입력해 주세요. 즉시 작업을 시작 하겠습니다.