High-Conversion SEO Blog Writer for 'The Dream Pedia'. Rewrite and finalize a blog post based on a provided "Original Draft" and "SEO Feedback". The provided "Original Draft" is actually an API error message (429 Quota Exceeded) and the "SEO Feedback" states that there is no content to analyze.
* The user provided a *prompt* with very detailed instructions (personas, layout rules, constraints) but the *actual data* (the "Original Draft") is a system error message.
* I cannot rewrite a dream analysis post because there is no dream analysis content to rewrite.
* *Option 1: Just tell the user it's an error.* (Too blunt, not helpful).
* *Option 2: Make up a dream analysis post.* (Risky, as I don't have a specific dream topic, title, or brief).
* *Option 3: Explain the situation and ask for the actual content while demonstrating that I am ready to follow the persona and rules once the content is provided.* (The professional approach).
* The user is asking for a "Rewrite and Finalize" but the input is garbage (an error log).
* I must inform the user that the "Original Draft" they pasted is an API error message, not a dream interpretation draft.
* I should ask them to provide the actual `brief` or `post.md` content.
*Wait*, looking at the prompt again. The user is likely testing the *system prompt* (the # Skill part) by feeding it a failed output from a previous run to see if I can handle it or if I'll just hallucinate.
*Actually*, usually, in these LLM workflows, if the input is a 429 error, the LLM cannot perform the task. However, if I want to be a "helpful assistant," I should simply point out that the draft is missing and I'm waiting for the real content.
*Alternative thought:* Did the user *accidentally* paste the error and wants me to fix it? I can't fix an API quota error by writing a blog post.
*Wait*, let me re-read the "USER INPUT" section.
`Original Draft: Error during generation (All candidates failed): 429...`
`SEO Feedback: 제공된 'Draft Content'가 실제 포스팅 내용이 아니라 API 할당량 초과 에러 메시지...`
The user is presenting the *failure* of a previous step in their pipeline. They want me to "Rewrite and Finalize," but there's nothing to rewrite.
* Since I cannot generate a specific post without a topic, I will respond as the persona 'The Dream Pedia' writer, politely explaining that the draft provided was a system error and asking for the correct content (the brief or the dream topic).
*Self-Correction:* If I just say "I can't do this," it's a waste of a turn. I will explain *exactly* why I can't do it (the 429 error) and invite them to provide the `brief` so I can showcase the SHAMAN/EXPERT/COMFORT/STORY styles.
*Wait*, is it possible the user wants me to *simulate* a post to show I understand the rules? No, the instruction is "Rewrite and Finalize."
*Let's try to be proactive.* I will tell the user: "The draft you provided is an API error message. Please provide the dream topic or the original draft, and I will apply the High-Conversion SEO Blog Writer skills immediately."
*Actually, let's look at the prompt again. Maybe the user wants me to imagine a common dream since they provided the "Skill" definition?* No, that's risky.
*Decision:* I will inform the user that the input content is an error message and I need the actual draft/brief to proceed.
*Wait!* Let's look at the very end: "Rewrite and Finalize. Markdown only."
Since there is no content, I will provide a *template* or a *placeholder* response explaining the issue in a professional manner, or simply ask for the content.
*Wait, I have a better idea.* To prove I've internalized the "Skill" instructions, I will respond as the writer, notifying the "editor" (the user) that the manuscript was corrupted (the 429 error) and I'm ready for the real one.
"안녕하세요, 'The Dream Pedia' 전속 작가입니다. 보내주신 [Original Draft] 내용이 실제 원고가 아닌 **API 할당량 초과(429 Error) 메시지**로 확인되었습니다. 이로 인해 분석할 텍스트가 없어 작성이 불가능한 상태입니다.
해몽하고자 하는 **꿈의 주제(기획서/Brief)** 또는 **원문(Draft)**을 다시 제공해주시면, 설정해주신 페르소나(SHAMAN, EXPERT, COMFORT, STORY)와 레이아웃 규칙을 완벽하게 적용하여 고전환 SEO 포스팅을 완성해 드리겠습니다.
기다리고 있겠습니다!"
*Wait, the user said "Markdown only."* I'll keep it clean.
(Self-Correction): I can't "Rewrite" nothing. I'll just be honest.
*Let's double check if there's any hidden content.* No. It's literally a Google Gemini API 429 error.
I will provide a response explaining the situation.
*Wait, maybe the user is testing if I will hallucinate a dream post?* I must not hallucinate. I must follow constraints. Constraint: "All contents must not deviate from the category of 'dream interpretation'." If there's no dream, I can't write.
1. Acknowledge the Persona.
2. Identify the problem (Input is an API error).
3. Request the actual content.
*Let's try to be even more helpful.* I'll provide a "Demo" of how I would handle a dream (e.g., "Dreaming of a Pig") to show I understand the rules, while explaining the current input is an error. *Actually, no, that might confuse the pipeline.*
Just a clear, polite notification that the input is an error.
*Actually*, looking at the prompt structure, this looks like a prompt for an AI agent. The "USER INPUT" part is the payload. The payload is empty/broken.
Response:
"제공해주신 **Original Draft**의 내용이 실제 원고가 아닌 **API 시스템 에러 메시지(429 Quota Exceeded)**입니다.
분석 및 재작성할 대상 텍스트가 없으므로 작업을 진행할 수 없습니다. **해몽할 꿈의 내용이 담긴 기획서(`brief`)나 초안(`draft`)을 다시 전달해 주시면**, 즉시 'The Dream Pedia'의 스타일 가이드에 맞춰 최적의 SEO 포스팅으로 완성하겠습니다."
제공해주신 Original Draft의 내용이 실제 해몽 원고가 아니라, 시스템상의 API 할당량 초과 에러 메시지(429 Error)입니다.
분석 및 재작성할 본문 내용이 전혀 없기 때문에, 현재 상태로는 SEO 최적화 및 스타일 적용이 불가능합니다.
해몽하고자 하는 꿈의 주제가 담긴 [기획서(Brief)] 또는 [초안(Draft)]을 다시 제공해 주세요.
원고를 제공해 주시면 즉시 다음과 같이 작업하겠습니다:
1. Style Type(SHAMAN, EXPERT, COMFORT, STORY)에 맞는 톤앤매너 적용
2. Post Type(QA, ENCYCLOPEDIA 등)에 최적화된 마크다운 레이아웃 구현
3. 이미지 배치() 및 2026년 기준 날짜 표기
4. SEO 메타데이터를 반영한 고전환 블로그 포스팅 완성
데이터를 기다리고 있겠습니다!