High-Conversion SEO Blog Writer (Dream Analysis) for 'The Dream Pedia'. Persona, Layout/Formatting Rules (QA, Shaman, Expert, Encyclopedia), Writing Styles (Shaman, Expert, Comfort, Story), and Constraints.
* Original Draft: Error (429 Quota exceeded).
* SEO Feedback: Error (500 Internal error).
* Task: "Rewrite and Finalize. Markdown only."
The user provided the prompt but failed to provide the actual content (the brief, the dream topic, the SEO metadata, etc.) because the previous generation failed. The "Original Draft" and "SEO Feedback" are literally error messages from an AI API.
* I cannot write a dream analysis post if I don't know *what dream* to analyze.
* The input is essentially empty of actual content, containing only system error messages.
* I need to inform the user that the provided input contains only API error messages and no actual draft or brief to work with.
* However, as an AI assistant following a persona, I should be helpful and ask for the specific `brief` (Style Type, Post Type, SEO Metadata, and the Dream Topic) so I can execute the task according to the high-conversion SEO rules.
* *Wait*, if I just say "I can't do this," it's a boring response. I should respond *as* the 'The Dream Pedia' writer, acknowledging that the "transmission" (the draft) was corrupted (mirroring the error messages) and asking for the correct files to begin the high-conversion writing process.
* *Self-Correction:* The prompt asks me to "Rewrite and Finalize." Since there is nothing to rewrite, I must politely request the source material.
* *Alternative interpretation:* Did the user accidentally paste the error and expect me to *know* what the previous context was? (I don't have memory of previous sessions unless provided in the prompt).
* *Action:* I will tell the user that the input provided consists of technical error messages and I need the `brief` (Dream topic, Style, Post type, and SEO metadata) to start writing.
* *Actually, looking closer at the prompt structure:* The user might be testing if I can handle a failure or just made a mistake.
* *Wait!* If I am a "High-Conversion SEO Blog Writer," and the user gives me "Error" as the draft, I cannot magically invent a dream topic without a brief.
* *Drafting the response:*
"안녕하세요, 'The Dream Pedia' 전속 작가입니다.
현재 입력해주신 내용에 **Original Draft와 SEO Feedback 부분이 API 오류 메시지로 대체되어 있어, 구체적인 꿈의 주제나 기획서(brief) 내용을 확인할 수 없습니다.**
완벽한 고전환 SEO 포스팅을 위해 다음 정보를 다시 제공해주시면 즉시 작성을 시작하겠습니다:
1. **기획서(brief):** 꿈의 주제, Style Type(SHAMAN, EXPERT, COMFORT, STORY), Post Type(QA, ENCYCLOPEDIA 등)
2. **SEO Metadata:** `seo_metadata.title` 및 핵심 키워드
3. **분석할 꿈의 내용:** (기존 드래프트가 있다면 해당 내용)
자료를 주시는 즉시, 2026년 기준의 최적화된 레이아웃으로 마법 같은 해몽 글을 완성해 드리겠습니다."
* Does it follow constraints? Yes.
* Is it professional? Yes.
* Does it address the "Error" input? Yes.
*(Self-Correction during output generation)*: Since the user asked for "Markdown only," I will provide a clean, professional request for the missing data in Markdown.
*Actually, looking at the prompt again, maybe the user wants me to *simulate* a successful rewrite of a hypothetical dream because they are testing the prompt?*
No, that's risky. It's better to ask for the brief.
*Wait, maybe I can provide a "Template" of how I will work once I get the brief to show I understand the instructions?*
Yes, that's a great way to add value.
1. Acknowledge the error messages in the input.
2. Request the `brief` and `seo_metadata`.
3. Show a small example of how I'll implement the rules (e.g., a Shaman-style layout) to prove I've internalized the instructions.
*Let's refine:* The user probably just wants the work done. If the input is broken, I can't work. I will simply and clearly ask for the brief.
*Wait, looking at the prompt "Rewrite and Finalize", if the input is just errors, I can't rewrite errors into a dream post.*
*Decision:* I will respond stating that the source text was missing due to the API error and I am ready to write as soon as the brief is provided.
*(Actually, let's provide a sample based on a common dream like "Dreaming of a Pig" just to show the prompt works, but explicitly state that the input was empty).*
*Actually, the most professional thing is to ask for the brief.*
"제공해주신 `Original Draft`와 `SEO Feedback` 내용이 시스템 오류 메시지(429 Quota Exceeded, 500 Internal Error)로 채워져 있어, 분석할 꿈의 주제와 기획서 내용을 확인할 수 없습니다.
**작성을 위해 다음 내용을 다시 전달해 주세요:**
1. **기획서(`brief`)**: 꿈의 주제, Style Type (SHAMAN/EXPERT/COMFORT/STORY), Post Type (QA/ENCYCLOPEDIA 등)
2. **SEO 메타데이터**: `seo_metadata.title` 및 타겟 키워드
3. **꿈의 상세 내용**: 해몽이 필요한 구체적인 상황
정보를 주시면 즉시 **2026년 기준의 최신 SEO 가이드라인과 지정하신 독특한 마크다운 레이아웃**을 적용하여 고전환 본문을 작성하겠습니다."
*Let's double check the prompt rules one last time.*
- Markdown only? Yes.
- No links? Yes.
- No related posts? Yes.
- Current year 2026? Yes.
I will send this.
제공해주신 Original Draft와 SEO Feedback 내용이 모두 시스템 API 오류 메시지(429 Quota Exceeded, 500 Internal Error)로 채워져 있어, 분석해야 할 꿈의 주제와 기획서(brief) 내용을 확인할 수 없는 상태입니다.
완벽한 고전환 SEO 포스팅을 위해 다음 내용을 다시 제공해주시면 즉시 작성을 시작하도록 하겠습니다.
📝 작성을 위해 필요한 정보:
1. 기획서(brief):
- 분석할 꿈의 주제 (예: 돼지 꿈, 이빨 빠지는 꿈 등)
- Style Type: (SHAMAN / EXPERT / COMFORT / STORY 중 택 1)
- Post Type: (QA / ENCYCLOPEDIA / 일반 분석 중 택 1)
2. SEO 메타데이터:
- seo_metadata.title (본문에 그대로 사용할 제목)
- 핵심 타겟 키워드
3. 참고 내용: (기존에 작성된 드래프트가 있다면 해당 내용)
🚀 자료를 주시면 다음과 같이 구현하겠습니다:
- SHAMAN 선택 시: 🔮 오늘의 길흉 판정 섹션과 고풍스러운 영적 말투 적용
- EXPERT 선택 시: 상징물별 분석 지표를 담은 Table(표) 서식과 냉철한 분석 적용
- QA 타입 선택 시: > **Q: ...?** / **A: ...** 구조의 명확한 가독성 확보
- 공통 적용: 2026년 기준 최신 정보 반영,  최적 배치, 불필요한 링크 및 연관 글 섹션 제거
지금 바로 기획서를 입력해 주세요!