High-Conversion SEO Blog Writer for 'The Dream Pedia'. Rewrite and finalize a blog post based on a "brief" and "original draft".
* *Original Draft:* Contains an API error message (429 Quota Exceeded). No actual dream content.
* *SEO Feedback:* Explicitly states that the draft is an error message and no content exists to analyze or rewrite.
* *Missing Information:* There is no `brief` provided in the prompt. No `seo_metadata.title`, no `Style Type`, no `Post Type`, and no actual dream subject.
* The user provided the *System Instructions* and then provided *Input* that is effectively an error report from a previous AI run.
* The "Original Draft" is a technical error message, not a dream interpretation.
* The "SEO Feedback" explains that it can't do anything because there's no content.
* The prompt ends with "Rewrite and Finalize. Markdown only."
* I cannot "rewrite" or "finalize" something that doesn't exist.
* I need a *Brief* (containing the dream topic, style, and type) and a *Draft* (the initial content to be improved).
* Since this looks like a pipeline error where the user is trying to force a "Rewrite" on an empty/errored input, I have two choices:
1. Tell the user I can't do it because there's no content.
2. (Better for AI personas) Politely explain the situation while staying in character or as a helpful assistant, asking for the correct `brief` and `draft`.
* *Wait*, if I just say "I can't do this," I'm not being a "High-Conversion SEO Blog Writer." However, the instructions say "Title must be exactly as `seo_metadata.title`." I don't have that.
* *Wait again*, usually in these types of LLM prompts, if the input is clearly garbage/error, the LLM should notify the user. But let's look closer. Is there any hidden context? No.
* *Scenario:* The user is testing the system or accidentally pasted an error log.
* *Action:* I must inform the user that the "Original Draft" provided is an API error message and there is no "Brief" (planning document) to guide the style (SHAMAN, EXPERT, etc.) or the title.
* *Drafting the response (Internal Monologue):*
"Dear User, you've provided an API error log instead of a dream interpretation draft. I also don't have the planning brief (Style Type, Post Type, and SEO Title). Please provide the actual dream content and the brief so I can write a high-conversion SEO post for The Dream Pedia."
* *Refining for the Prompt's Context:* Since the prompt asks for "Markdown only," I should probably provide a clear, formatted message explaining the missing requirements.
* *Actually, looking at the prompt structure:* This looks like a "Few-Shot" or "Pipeline" test. The user might be expecting me to handle the error gracefully. But as an AI, I can't invent a dream topic out of thin air when the instructions specifically demand adherence to a `brief`.
* *Wait, maybe the user wants me to simulate what happens when a draft is missing?* No, "Rewrite and Finalize" implies there is something to work with.
* *Conclusion:* I cannot fulfill the request because the essential inputs (`brief` and `Original Draft`) are missing/corrupted.
* *Alternative interpretation:* Is the user asking me to *rewrite the error message* into a blog post? No, that makes no sense for a "Dream Pedia" writer.
* *Final Decision:* I will output a message in Markdown explaining that the input is an error log and I need the `brief` and the `Original Draft` to proceed.
*(Self-Correction during drafting)*: If I am an AI agent in a pipeline, and I receive an error as input, I should flag it.
*Let's try to be as helpful as possible. I'll tell them exactly what's missing based on the "Persona & Context" section.*
1. Missing `brief` (Style Type, Post Type, etc.).
2. Missing `seo_metadata.title`.
3. Original Draft is a 429 Error.
*Wait, if I just output an error message, I might fail a "test" if the user wants me to just "make something up." But the instructions are very strict about the brief and title. I will stick to the facts.*
*Let's provide a response that explains the situation clearly.*
**BUT**, usually, when users paste this into an LLM, they might have made a mistake. I'll provide a polite, professional notification.
"죄송합니다. 제공해주신 `Original Draft` 내용이 실제 해몽 본문이 아니라 **API 호출 한도 초과(429 Quota Exceeded) 에러 메시지**입니다. 또한, 작성을 위해 반드시 필요한 **기획서(`brief`)**와 **SEO 메타데이터(`seo_metadata.title`)**가 누락되어 있습니다.
정확한 고퀄리티 포스팅 작성을 위해 다음 내용을 다시 제공해 주세요:
1. **기획서(brief):** Style Type(SHAMAN, EXPERT 등), Post Type(QA, ENCYCLOPEDIA 등) 포함.
2. **SEO 메타데이터:** 사용할 제목(`title`).
3. **Original Draft:** 분석할 실제 꿈 해몽 초안 내용.
내용을 입력해주시면 즉시 'The Dream Pedia'의 스타일로 완벽하게 리라이팅하겠습니다."
*Wait, the prompt says "Markdown only." I will keep it clean.*
Actually, looking at the prompt again, it's a "system prompt" followed by a "user input." The user input is the error. This is a classic case of a failed pipeline step being passed to the next step.
I will output a professional notification that the input is invalid.
(Wait, could I "hallucinate" a dream to show off my skills? No, that violates the "Constraints" regarding the title and brief. I must be precise.)
*Final Plan:*
- Acknowledge the error.
- List missing requirements.
- Request the correct data.
*Wait*, let me check if I can find any "dream" keywords in the error. No. It's purely technical.
Let's try to be a bit more proactive. I'll explain *why* I can't proceed based on the rules I was just given.
"**[작성 불가 안내]**
현재 입력된 데이터로 작업을 진행할 수 없습니다.
**사유:**
1. **초안 내용 부재:** `Original Draft`에 실제 꿈 해몽 내용 대신 API 에러 메시지(429 Quota Exceeded)가 입력되었습니다.
2. **기획서(Brief) 누락:** `Style Type`, `Post Type` 등 레이아웃과 톤앤매너를 결정할 기획서가 제공되지 않았습니다.
3. **제목 누락:** `seo_metadata.title` 정보가 없어 제약 사항(제목 그대로 사용)을 준수할 수 없습니다.
**요청 사항:**
정상적인 **기획서(Brief)**와 **해몽 초안(Draft)**을 입력해 주시면, 즉시 'The Dream Pedia'의 고전환 SEO 포스팅으로 완성해 드리겠습니다."
*Let's double check if the user wants me to "act" like the AI that failed? No, "Rewrite and Finalize" is the instruction.*
Okay, I'll provide the response in a clean Markdown format.
[작성 불가 안내]
현재 입력된 데이터로는 포스팅 작성이 불가능합니다. 그 이유는 다음과 같습니다.
- 초안 내용 부재:
Original Draft섹션에 실제 꿈 해몽 내용이 아닌, API 호출 한도 초과(429 Quota Exceeded) 에러 메시지가 입력되어 있습니다. - 기획서(Brief) 누락: 본문의 레이아웃과 말투를 결정짓는 Style Type(SHAMAN, EXPERT, COMFORT, STORY)과 Post Type(QA, ENCYCLOPEDIA 등) 정보가 포함된 기획서가 제공되지 않았습니다.
- 제목 누락: 제약 사항인
seo_metadata.title정보가 없어 제목을 설정할 수 없습니다.
정상적인 결과물을 위해 다음 내용을 다시 입력해 주세요:
* 기획서(brief): 스타일 타입, 포스트 타입, 핵심 키워드 등이 포함된 내용
* SEO 메타데이터: 사용할 최종 제목(title)
* Original Draft: 리라이팅할 실제 꿈 해몽 초안 내용
내용을 제공해 주시면 즉시 'The Dream Pedia'의 전속 작가로서 고전환 SEO 포스팅을 작성하겠습니다.