High-Conversion SEO Blog Writer for 'The Dream Pedia'. Rewrite and finalize a blog post based on a brief/draft.
* Original Draft: An API error message (429 Quota Exceeded).
* SEO Feedback: "Draft Content is an API error message... cannot analyze."
The user has not provided a brief or actual Original Draft content. They provided the error message that happened in a previous run.
* I cannot write a dream analysis post without knowing *what the dream is*.
* I need the `brief` (which usually contains `seo_metadata.title`, `style_type`, `post_type`, and the dream subject).
* However, the user's prompt says "Rewrite and Finalize. Markdown only."
* *Wait*, looking at the prompt again, the "USER INPUT" section contains the error message. It's a failure of a previous automation pipeline.
* *Problem:* I have no content to rewrite.
* *Action:* I must inform the user that the provided input is an API error message and that I need the actual `brief` and `Original Draft` content (or at least the dream subject/metadata) to perform the task according to the defined persona and layout rules.
* *Wait*, let me double-check if there's any hidden context. No. The "USER INPUT" is literally the error log.
* *Alternative interpretation:* Is the user testing if I can handle this error? Or did they accidentally paste the error instead of the content? Most likely the latter.
* *Correct response strategy:*
1. Acknowledge the Persona (The Dream Pedia Writer).
2. Politely explain that the "Original Draft" provided is a technical error message from an AI API, not a dream analysis draft.
3. Request the `brief` and the actual content to be rewritten.
* *Self-Correction:* If I just say "I can't do it," it might be too blunt. I should stay in character or at least be professional. But since I cannot *hallucinate* a dream, I must ask for the input.
* *Hypothetical Scenario:* What if the user *wants* me to make up a dream based on a generic theme? No, the prompt specifically mentions `seo_metadata.title` from the brief. Without the brief, I can't follow the "Constraints" (like using the specific title).
* *Drafting the response:*
"Hello, I am the official writer for 'The Dream Pedia'. I have reviewed the provided input, but the 'Original Draft' section contains an API error message (429 Quota Exceeded) instead of actual content. To provide a high-conversion SEO post with the correct Style Type and Layout, please provide the **Planning Brief (brief)** including the `seo_metadata.title` and the **Actual Draft Content**. I am ready to apply the SHAMAN, EXPERT, COMFORT, or STORY style as soon as the data is provided."
* *Wait*, if I am an AI in a pipeline, maybe the user expects me to *know* what to do if this happens? No, I'm the LLM. I just need the data.
* *Let's try to be helpful:* I will tell them exactly what is missing.
* *Wait!* Looking at the prompt again. It says "Rewrite and Finalize. Markdown only." If I just respond with a request for data, it's not "Markdown only" in the sense of a blog post. But I can't write a blog post about a "429 Quota Exceeded" error as a *dream analysis*. That would be absurd.
* *Final Plan:* Respond clearly stating that the input is an error log and the necessary `brief` is missing.
*(Self-Correction during final output generation)*: Actually, usually, in these prompt-engineering tests, the user might have made a mistake. I will provide a polite, professional response asking for the missing information.
*Wait, let me look at the prompt one more time.* Is there any chance the "Original Draft" *is* the dream? No, it's clearly a Google Gemini API error.
*Okay, I will write a response in Korean (as the persona instructions are in Korean) explaining the situation.*
"안녕하세요. 'The Dream Pedia' 전속 작가입니다.
제공해주신 `Original Draft` 내용이 실제 해몽 본문이 아니라, AI API의 할당량 초과 오류 메시지(429 Quota Exceeded)로 확인됩니다.
정교한 SEO 포스팅과 맞춤형 레이아웃(SHAMAN, EXPERT 등)을 적용하기 위해서는 다음 정보가 반드시 필요합니다:
1. **기획서(Brief):** `seo_metadata.title`, `Style Type`, `Post Type`이 포함된 내용
2. **실제 본문 초안(Original Draft):** 분석할 꿈의 내용
해당 데이터를 다시 제공해 주시면, 즉시 최적의 마크다운 레이아웃으로 완벽하게 작성해 드리겠습니다."
*Wait, the prompt says "Markdown only."* I'll keep it brief and professional.
*Actually, let's consider if this is a "trick" prompt.* If I can't do the task, I can't do it. But I will communicate it clearly.
*Refined response:*
Since I cannot fulfill the request without the content, I will ask for the content.
(Actually, if I want to be a "perfect" agent, I should tell the user that the input provided is an error message and I am waiting for the actual content to begin the writing process.)
*Let's try a different angle:* Maybe the user wants me to write a dream analysis *about* an API error? (Dreaming of computers crashing?). No, the SEO feedback specifically says "검수할 본문 내용이 없으므로 SEO 분석 및 데이터 추출이 불가능합니다." (There is no content to review, so SEO analysis is impossible). This confirms the user *intended* to provide a draft but provided an error instead.
I will respond by informing the user that the input is an error message.
---
*Wait, if I am in a "completion" mode, and the user says "Rewrite and Finalize", they might be expecting me to "fix" the situation.* But I can't fix a missing draft.
*I'll provide a response in Korean explaining the missing data.*
제공해주신 Original Draft의 내용이 실제 꿈 해몽 본문이 아니라, AI API의 할당량 초과 오류 메시지(429 Quota Exceeded)입니다.
현재 상태로는 분석할 꿈의 내용과 기획서(brief)의 세부 설정(Style Type, Post Type, SEO 제목 등)이 전혀 없기 때문에 본문 작성이 불가능합니다.
완벽한 고전환 SEO 포스팅을 위해 다음 내용을 다시 입력해 주세요:
- 기획서(Brief):
seo_metadata.title,Style Type(SHAMAN, EXPERT, COMFORT, STORY),Post Type(QA, ENCYCLOPEDIA 등)이 포함된 내용. - 실제 본문 초안(Original Draft): 분석하고자 하는 꿈의 구체적인 내용.
데이터를 제공해 주시면 즉시 'The Dream Pedia'의 스타일 가이드에 맞춘 최적의 마크다운 레이아웃으로 작성을 시작하겠습니다.