High-Conversion SEO Blog Writer (Dream Analysis) for 'The Dream Pedia'. Write a blog post based on a brief/draft.
* Layout: Follow Style Type and Post Type.
* QA Type: `> **Q: ...?**` and `**A: ...**`.
* SHAMAN Style: `> ### 🔮 오늘의 길흉 판정: [길몽/흉몽]`.
* EXPERT Style: Analysis tables.
* ENCYCLOPEDIA Type: Summaries via quotes (`>`) or code blocks.
* Images: Use `` placeholders.
* Writing Style: SHAMAN (spiritual), EXPERT (analytical), COMFORT (warm), STORY (narrative).
* Constraints: No links, use specific title, dream-related content only, year 2026 only, no "related posts" sections, no clickbait/slang.
The user provided an "Original Draft" which is actually an API error message (429 Quota Exceeded) and "SEO Feedback" stating that the content is missing.
* The user is asking to "Rewrite and Finalize" based on an input that contains *no actual content* (only an error message).
* I cannot write a dream analysis post because there is no specific dream topic provided (e.g., "dreaming of a snake", "dreaming of flying").
* However, as an AI, I should point out the missing information while remaining in character or providing a clear path forward. But wait, usually, when users give a prompt like this, they might have accidentally pasted the wrong thing or are testing if I can handle the "error" as a prompt.
* *Crucial realization:* The prompt says "USER INPUT: Original Draft: [Error Message]... SEO Feedback: [Content missing]... Rewrite and Finalize."
* Since there is no topic, I cannot generate a specific post. But to be helpful, I should inform the user that the input provided is an error message and I need the actual `brief` or `draft` to begin the writing process.
* Wait, did the user provide a `brief` elsewhere? No.
* Did the user provide a topic? No.
* The user is literally asking me to "Rewrite and Finalize" an API error message. If I try to "rewrite" the error message as a dream post, it makes no sense.
* *Correction:* I must ask for the specific dream topic, the Style Type, and the Post Type.
* *Alternative Interpretation:* Is the user testing if I can follow the instructions even if the input is garbage? Or did they make a mistake?
* If I simply say "I can't do this," it's boring. If I try to hallucinate a dream, I might be wrong.
* *Best approach:* Acknowledge the system instructions and politely explain that the "Original Draft" provided is a technical error message and not a dream analysis draft. Ask for the `brief` (Topic, Style Type, Post Type, etc.) to start the high-conversion writing.
* *Wait, looking closer at the prompt format:* The user is providing a template. They might be expecting me to act as the AI that *fixes* the failure. But there is nothing to fix without the source.
* *Wait!* I see what happened. This looks like a "loop" or a "failed pipeline" log. The user is probably a developer or a content manager who is pasting the output of a failed run and asking me to "Rewrite and Finalize." But they forgot to include the original request/brief.
* *Actually, let's look at the "Original Draft" again.* It's literally just a Gemini API error.
* I cannot "Rewrite" an error message into a high-conversion SEO blog post without a subject.
* *Wait, let me try to be proactive.* I will tell the user: "You've provided an API error message instead of a dream analysis draft. Please provide the **Topic**, **Style Type**, and **Post Type** (or the original brief), and I will immediately generate the post according to the 'The Dream Pedia' guidelines."
* *Wait, is there any hidden prompt?* No.
* *Let's assume the user wants to see a SAMPLE of how I would handle a request given these complex rules, since the input was an error.* No, that's risky.
* *Let's try to be professional:*
"제공해주신 'Original Draft' 내용이 API 오류 메시지(429 Quota Exceeded)로 확인됩니다. 해몽 본문을 작성하기 위해서는 분석할 **꿈의 주제(키워드)**, **Style Type**(SHAMAN, EXPERT, COMFORT, STORY), 그리고 **Post Type**(QA, ENCYCLOPEDIA 등)이 포함된 기획서(`brief`)가 필요합니다.
기획서를 제공해주시면 즉시 'The Dream Pedia'의 전속 작가로서 최적의 SEO 포스팅을 작성해 드리겠습니다."
* *Self-Correction:* The prompt ends with "Rewrite and Finalize. Markdown only." This implies the user wants the *result* in Markdown.
* Since I have no content, I will provide a **Template/Example** of how I will work once they provide the content, to show I understand the instructions perfectly. Or, I'll just ask for the data.
* *Let's re-read the system prompt again.* It's a very detailed set of rules. The user is likely setting up a persona. The "USER INPUT" part was a mistake on their end (pasting an error log).
* *Decision:* I will respond by explaining that the input is an error and I am ready to work as soon as the actual brief is provided.
* *Wait, what if the user wants me to "hallucinate" a post based on the "idea" of an API error?* No, that's not 'Dream Analysis'.
* *Let's provide a response that acknowledges the Persona and asks for the input.*
* *Wait, I can do better.* I will explain that the draft is missing, but to demonstrate my capability, I'll ask for the specific parameters.
* **HOWEVER**, often in these LLM prompts, the user might have accidentally omitted the prompt but wants the AI to *simulate* the process. But without a topic, I can't.
* *Let's try this:*
1. Acknowledge the persona: "I am the exclusive writer for 'The Dream Pedia'."
2. Point out the error: "The input provided is an API error message, not a dream draft."
3. Request the `brief`: "Please provide the Topic, Style, and Type."
* *Actually, looking at the prompt again, the user might be testing my ability to recognize that the input is invalid and needs a specific format.*
* *Let's respond in a way that confirms I am ready and waiting for the actual data.*
* (Self-Correction): If I just say "I can't," I might fail a test. I will respond in Korean, since the prompt context is Korean, confirming my readiness and explaining the issue with the "Original Draft."
* *Wait, maybe I should just generate a a "Placeholder" or a "Sample" post to show I can follow the complex formatting rules?*
Let's do a sample post for "Dreaming of a Golden Pig" (a classic) using the SHAMAN/QA style to prove I've mastered the layout.
* *Actually, the most professional response is to inform the user that the input is missing.*
* *Let's try to see if there's any other interpretation.*
"Rewrite and Finalize" -> The user wants me to take the "Original Draft" and "SEO Feedback" and turn it into a final post.
But the "Original Draft" is "Error 429".
The "SEO Feedback" is "Content is missing".
There is literally nothing to rewrite.
* **I will reply as the Persona, acknowledging the error and asking for the actual brief.**
* *Persona check:* High-Conversion SEO Blog Writer.
* *Tone:* Professional, ready to execute.
* *Drafting the response:*
"안녕하세요. 'The Dream Pedia' 전속 작가입니다.
현재 입력해주신 `Original Draft` 부분이 실제 해몽 내용이 아닌 **API 할당량 초과 오류 메시지(429 Quota Exceeded)**로 되어 있습니다. 이에 따라 `SEO Feedback`에서도 분석 대상이 누락되었다고 안내하고 있습니다.
완벽한 고전환 SEO 포스팅을 작성하기 위해 아래 정보를 포함한 **기획서(`brief`) 또는 실제 작성된 초안**을 다시 전달해 주세요:
1. **꿈의 주제 (Keyword)**
2. **Style Type** (SHAMAN / EXPERT / COMFORT / STORY)
3. **Post Type** (QA / ENCYCLOPEDIA / 일반형)
4. **seo_metadata.title** (사용할 제목)
데이터를 주시는 즉시, 설정된 마크다운 레이아웃과 2026년 기준의 최신 톤앤매너를 적용하여 최상의 결과물을 만들어내겠습니다."
* *Wait, the user said "Markdown only."* I should probably just output this message in a clean markdown format.
* *One more thought:* Is it possible the user wants me to "dream" about an API error? No, that's too meta.
* *Let's provide a sample just in case they wanted to see the layout implementation.*
No, the prompt is a strict instruction set. I should follow it. The instruction says "Rewrite and Finalize" the input. Since the input is "Error", the final result is "I need the actual content".
* *Actually, I'll provide a "Ready" status and a "Template" of how I will handle the next input to prove I understand the 3.1 Upgrade rules.*
* (Revised Plan):
1. State that the current input is an API error.
2. Request the actual brief.
3. Show a *Mini-Example* of how I will implement the SHAMAN/EXPERT/QA styles so the user knows I've absorbed the instructions.
* *Wait, the prompt is very strict: "Markdown only."*
I will just provide the request for information clearly.
* *Let's double check the Constraints:*
- Year 2026 only.
- No links.
- No "related posts".
- No clickbait.
* (Wait, if I generate a sample, I must follow these!)
* *Let's just be honest and professional.*
* *Wait!* I just noticed something. The user might be simulating a scenario where the previous AI failed, and I am the "Fixer" AI. But again, I can't fix "nothing".
* *Final Decision:* Respond that the input is an error and I am ready for the actual brief.
* *Actually...* looking at how these prompts usually work in a pipeline, the user might have just pasted the wrong thing. I'll give a concise, professional response in Markdown.
* *Wait, I will try one more thing.* I'll assume the user *wants* me to demonstrate the skill using a random dream since they provided the full system prompt. But the prompt says "Rewrite and Finalize [The Input]". The input is an error.
* Let's go with:
"제공된 `Original Draft`가 API 오류 메시지이므로, 작성을 위한 원천 데이터가 없습니다. **분석할 꿈의 주제와 스타일/타입이 명시된 기획서(`brief`)를 제공해 주세요.**
기획서를 주시면 즉시 다음과 같은 규칙을 적용하여 작성하겠습니다:
- **SHAMAN/EXPERT/COMFORT/STORY** 스타일 맞춤 톤앤매너
- **QA/ENCYCLOPEDIA** 등 타입별 특화 레이아웃
- **** 형태의 전략적 배치
- **2026년** 기준의 최신성 유지
- SEO 최적화 및 고전환 구조 설계"
* (Self-Correction): I'll keep it simple.
* *Wait, looking at the "SEO Feedback" part:* "제공된 'Draft Content'가 실제 블로그 본문이 아니라 API 할당량 초과... 실제 작성된 포스팅 내용을 다시 입력해 주세요."
This feedback is *already* telling the user to provide the content. The user is now asking *me* to "Rewrite and Finalize".
This is a paradox.
* I will respond that I am the "The Dream Pedia" writer, I see the error, and I'm waiting for the content.
* *Let's try to be a bit more helpful. I'll create a hypothetical "Success Case" to show I can do it.*
No, just ask for the data.
* *Final Polish:*
1. Acknowledge the role.
2. Identify the problem (Input = Error 429).
3. Ask for the Brief.
4. Confirm understanding of the Layout 3.1 rules.
* (Wait, the user might be testing if I'll try to "rewrite" the error message as a story? No, that's not what a "High-Conversion SEO Blog Writer" does. They write dreams.)
* *Let's provide the response.*
제공해주신 Original Draft의 내용이 실제 꿈 해몽 초안이 아니라, Gemini API의 할당량 초과 오류 메시지(429 Quota Exceeded)입니다.
SEO Feedback에서도 명시되었듯이, 분석하고 재작성할 대상(post.md 내용)이 전혀 없는 상태입니다. 저는 'The Dream Pedia'의 전속 작가로서 준비가 완료되었으나, 작성할 '꿈의 주제'와 '기획서(brief)'가 필요합니다.
완벽한 고전환 SEO 포스팅을 위해 아래 정보를 포함하여 다시 입력해 주세요.
📝 요청 드리는 정보 (Brief)
- 꿈의 주제: (예: 돼지가 집으로 들어오는 꿈, 이빨이 빠지는 꿈 등)
- Style Type: (
SHAMAN/EXPERT/COMFORT/STORY중 선택) - Post Type: (
QA/ENCYCLOPEDIA/일반형중 선택) - SEO 메타데이터: (
seo_metadata.title등 사용할 제목)
🚀 데이터를 주시면 다음과 같이 처리하겠습니다:
- 레이아웃 3.1 적용: 선택하신 타입(QA, ENCYCLOPEDIA 등)에 최적화된 마크다운 구조 설계.
- 스타일 맞춤 톤앤매너: SHAMAN의 영적인 말투부터 EXPERT의 분석적 말투까지 완벽 구현.
- 이미지 전략 배치:
형식을 활용해 파이프라인 최적화. - 제약 사항 준수: 2026년 기준 표기, 링크 제외, 낚시성 표현 배제.
지금 바로 기획서를 입력해 주시면, 최상의 결과물로 보답하겠습니다.