High-Conversion SEO Blog Writer (Dream Analysis) for 'The Dream Pedia'. Rewrite and Finalize a blog post based on a provided brief.
* *Original Draft:* An error message (429 Quota Exceeded).
* *SEO Feedback:* An error message (500 Internal error).
* *Constraint:* I have *no* actual content to rewrite. The user provided system instructions (Persona, Layout, Writing Style, Constraints) but the input for the specific dream topic is missing (it's just error logs).
* The user provided the *System Prompt* (the skill definition) and then provided "USER INPUT" which contains only technical errors from a previous API call.
* There is no `brief`, no `seo_metadata.title`, no `Style Type`, and no `Post Type`.
* I cannot write a dream analysis post without knowing *which dream* to analyze.
* I need to inform the user that the "Original Draft" and "SEO Feedback" they provided are actually error messages from an AI API, not the actual content/brief.
* I must ask for the `brief` (containing the dream topic, Style Type, Post Type, and SEO metadata) to proceed according to the persona.
* *Wait*, as an AI, if I just say "you gave me errors," it might be too blunt. I should be professional.
* However, the prompt says "Rewrite and Finalize. Markdown only." If I can't do it, I can't do it.
* *But*, looking closer at the user's prompt structure, it seems they might have accidentally pasted the error logs instead of the actual data.
* *Self-Correction/Assumption:* Since I am acting as the "High-Conversion SEO Blog Writer," I should respond in a way that indicates I am ready but need the correct data. But the prompt asks for "Markdown only" and "Rewrite and Finalize."
* *Alternative Interpretation:* Is the user testing if I can handle "empty" or "broken" inputs? Or did they genuinely make a mistake?
* If I try to "hallucinate" a dream, I'll likely fail the SEO metadata requirement (`seo_metadata.title`).
* Since the input is literally an error log, I cannot fulfill the request to "Rewrite and Finalize" a blog post.
* I will politely inform the user that the provided input consists of API error messages and I need the actual `brief` to start writing.
* *Wait!* Let me check if there's any hidden meaning. No, "429 You exceeded your current quota" is a classic API error.
* *Decision:* I will respond by explaining that the input provided is an error log and requesting the `brief` and `seo_metadata` to begin the work.
* *Hold on*, looking at the prompt again, it's a system instruction followed by a failed attempt to get content. The user is likely trying to "recover" the process.
* *Let's try to be a helpful assistant:* "The provided input contains API error messages instead of the blog brief. Please provide the `brief` including the **Style Type**, **Post Type**, and **SEO Metadata**, and I will immediately craft the high-conversion dream analysis post for 'The Dream Pedia' according to your rules."
* *Actually*, if I want to stay in character as the "The Dream Pedia's exclusive writer," I should say it like this:
"작가입니다. 보내주신 내용에 실제 기획서(`brief`) 대신 API 오류 메시지가 포함되어 있습니다. 분석할 꿈의 주제, 스타일 타입, 포스트 타입, 그리고 SEO 메타데이터가 담긴 기획서를 다시 전달해 주시면 즉시 최상의 퀄리티로 집필하겠습니다."
* *But* the prompt says "Markdown only."
* *Let's double-check the prompt one more time.*
USER INPUT:
Original Draft: [Error 429]
SEO Feedback: [Error 500]
Rewrite and Finalize. Markdown only.
There is absolutely no content. I cannot synthesize a dream post out of "Quota exceeded."
*Action:* Inform the user about the error logs.
*(Self-Correction)*: If I simply output an error message, it's not "Markdown only" in the sense of a blog post. But I can't write a blog post.
Let's try to provide a template or a request for data in a clean markdown format.
*Wait*, maybe the user wants me to *simulate* a post based on a random dream to show I can follow the rules? No, the rules are very specific about `seo_metadata.title`.
*Final Decision:* I will tell the user that the input is an error log and I need the brief.
*(Wait, let's look at the "Persona" again)*. I am the writer.
"안녕하세요, The Dream Pedia 전속 작가입니다.
현재 입력해주신 **Original Draft**와 **SEO Feedback** 내용이 API 시스템 오류 메시지로 확인됩니다.
작업을 진행하기 위해 아래 정보가 포함된 **기획서(brief)**를 다시 전달 부탁드립니다.
1. **분석할 꿈의 주제**
2. **Style Type** (SHAMAN, EXPERT, COMFORT, STORY 중 택 1)
3. **Post Type** (QA, ENCYCLOPEDIA 등)
4. **SEO Metadata** (특히 `title` 필수)
기획서를 받는 즉시, 정의된 레이아웃과 스타일 가이드에 맞춰 완벽한 포스팅을 작성하겠습니다."
*Wait, let me check if the user is actually asking me to "Fix" the error?* No, the system prompt defines me as a Blog Writer.
*Let's provide this response in Markdown.*
(Actually, looking at the prompt "Rewrite and Finalize", it's possible the user *thought* the content was there).
I will provide a response stating the data is missing.
*Wait... let me try one more thing.* If this is a prompt engineering test, the "correct" answer for a professional agent is to identify the missing input.
**However**, if I want to be proactive, I can't just guess the dream.
Let's respond clearly.
제공해주신 Original Draft와 SEO Feedback 내용이 실제 본문이 아닌 API 시스템 오류 메시지(429 Quota Exceeded, 500 Internal Error)로 확인됩니다.
작성해야 할 꿈의 주제와 구체적인 가이드라인이 누락되어 현재로서는 집필이 불가능합니다. 'The Dream Pedia'의 스타일 가이드에 맞춘 고퀄리티 포스팅을 위해, 아래 내용이 포함된 기획서(brief)를 다시 전달해 주시기 바랍니다.
📋 요청 드리는 필수 정보:
1. 분석할 꿈의 주제: (예: 돼지가 나오는 꿈, 이빨 빠지는 꿈 등)
2. Style Type: (SHAMAN, EXPERT, COMFORT, STORY 중 선택)
3. Post Type: (QA, ENCYCLOPEDIA 등 선택)
4. SEO Metadata: (특히 seo_metadata.title 필수 포함)
기획서를 전달해 주시면 즉시 2026년 기준의 최신 트렌드와 지정된 독특한 마크다운 레이아웃을 적용하여 최상의 전환율을 만드는 본문을 작성하겠습니다.