High-Conversion SEO Blog Writer for 'The Dream Pedia'. Persona-based writing (Shaman, Expert, Comfort, Story), specific layouts (QA, Encyclopedia, etc.), strict formatting rules.
* `Original Draft`: Contains an API error message (429 Quota Exceeded). No actual dream content.
* `SEO Feedback`: Contains an API error message (500 Internal error). No actual feedback.
* `User Instruction`: "Rewrite and Finalize. Markdown only."
* The user provided a prompt with a system instruction (Persona, Layout, Rules) but the *input data* (the actual dream content to write about) is missing. Instead, the input contains error messages from a previous AI generation attempt.
* I cannot "rewrite and finalize" a draft that doesn't exist. There is no `brief`, no `seo_metadata.title`, no `Style Type`, and no `Post Type`.
* I need to inform the user that the input provided was an error message and not the actual content/brief needed to generate the blog post.
* However, as an AI agent, if I just say "Error," it's not helpful. I should explain *why* I can't proceed and ask for the correct `brief` (Title, Style, Type, and Dream Content).
* *Wait*, looking at the prompt again, it seems like a template was filled with error messages. The user might be testing the system or might have accidentally pasted the wrong thing.
* *Crucial realization:* I cannot fulfill the request to write a "High-Conversion SEO Blog" without the specific dream topic.
* Since the user asked to "Rewrite and Finalize," but provided error logs, I must politely point out that the `Original Draft` and `SEO Feedback` sections contain technical errors rather than the actual content to be rewritten.
* *Self-Correction:* If I simply refuse, I'm not being a "High-Conversion SEO Blog Writer." But I literally have no topic. "Dreaming about... what?"
* *Scenario A:* The user wants me to act as the persona and wait for the correct input.
* *Scenario B:* The user thinks I can "recover" the failed generation (I can't, I don't have access to the other session's state).
* *Action:* I will respond by asking for the `brief` (Title, Style, Type, Content) because the input provided was an API error log.
* *Alternative approach:* Did the user *intend* for me to write a dream interpretation *about* API errors? (Unlikely, but possible in a meta-joke way). No, the prompt says "All contents must not deviate from the category of 'dream interpretation'". API errors are not dreams.
* *Professional Response:*
"I am ready to write as 'The Dream Pedia' expert writer. However, the `Original Draft` and `SEO Feedback` provided in your input are system error messages (429 Quota Exceeded and 500 Internal Error) rather than a dream analysis brief.
Please provide the following so I can begin:
1. `seo_metadata.title`
2. `Style Type` (SHAMAN, EXPERT, COMFORT, STORY)
3. `Post Type` (QA, ENCYCLOPEDIA, etc.)
4. The dream content/draft to be analyzed."
* *But wait*, looking at the user's prompt structure, they are using a "Skill" definition. They probably want me to acknowledge the skill and then they will provide the data, OR they pasted the wrong thing.
* *Wait*, looking at the prompt again: `USER INPUT: Original Draft: [Error] SEO Feedback: [Error] Rewrite and Finalize.`
* This looks like an automated pipeline failed, and the user is now manually trying to get the AI to fix it, but they passed the error logs *as* the content.
* *Decision:* I will explain the situation clearly and ask for the actual dream content.
* *Let's try to be proactive:* Since I cannot generate a post without a topic, I will respond in a way that maintains the persona but asks for the missing data.
* *Wait*, what if I simulate a "Dream about System Errors" just to show I can do it? No, that violates the "High-Conversion SEO" goal.
* *Refined Response:*
I cannot fulfill the request because the `Original Draft` and `SEO Feedback` contain API error logs instead of a dream interpretation brief. To produce a high-conversion SEO post, I need the actual dream topic and the specified Style/Type.
* *Wait*, I'll write this in a way that shows I've internalized the rules.
"안녕하세요. 'The Dream Pedia' 전속 작가입니다.
현재 입력해주신 `Original Draft`와 `SEO Feedback` 내용이 실제 꿈 해몽 데이터가 아닌, **시스템 API 오류 메시지(429 Quota Exceeded / 500 Internal Error)**로 확인됩니다.
완벽한 SEO 포스팅 작성을 위해 아래 정보를 다시 제공해 주시면, 즉시 설정된 페르소나와 레이아웃에 맞춰 집필을 시작하겠습니다.
**필요 정보:**
1. **기획서(Brief):** `seo_metadata.title` (제목)
2. **Style Type:** (SHAMAN / EXPERT / COMFORT / STORY 중 선택)
3. **Post Type:** (QA / ENCYCLOPEDIA 등 선택)
4. **해몽 대상:** 분석할 구체적인 꿈 내용 또는 초안"
*Wait*, the prompt says "Markdown only." I should keep it concise.
Actually, if this is a test of the prompt, I should just tell the user the input is invalid.
*One more check:* Is it possible the user *is* the system and is testing if I can handle errors?
Regardless, I can't "Rewrite and Finalize" an error message into a dream blog.
*Final Plan:*
1. Acknowledge the persona.
2. Point out that the input is an error log.
3. Request the actual brief.
안녕하세요. 'The Dream Pedia' 전속 작가입니다.
현재 제공해주신 Original Draft와 SEO Feedback의 내용이 실제 꿈 해몽 데이터가 아닌, 시스템 API 오류 메시지(429 Quota Exceeded 및 500 Internal Error)로 확인됩니다.
분석할 꿈의 내용과 기획서(brief)가 없기 때문에 현재로서는 본문 작성이 불가능합니다. 고품질의 SEO 포스팅을 위해 아래 정보를 다시 제공해 주시면, 즉시 설정된 페르소나와 레이아웃에 맞춰 완벽한 결과물을 만들어 내겠습니다.
제공이 필요한 정보:
1. seo_metadata.title: (포스팅에 사용할 정확한 제목)
2. Style Type: (SHAMAN / EXPERT / COMFORT / STORY 중 선택)
3. Post Type: (QA / ENCYCLOPEDIA / 일반 분석 등 선택)
4. 꿈 내용/초안: (해몽이 필요한 구체적인 꿈의 상황이나 기존 초안)
데이터를 입력해 주시면 바로 집필을 시작하겠습니다.