Update README: Change output format to JSON structure
Browse files
README.md
CHANGED
|
@@ -46,10 +46,12 @@ Remember: Write as if you're chatting with an old friend! Don't start with obvio
|
|
| 46 |
CRITICAL: The email MUST feel like a casual conversation between friends! Write as if you're excitedly telling a friend about something cool you found. Completely avoid any marketing language or sales pitch tone. The reader should feel like they're getting a genuine personal message, not a promotional email.
|
| 47 |
|
| 48 |
IMPORTANT:
|
| 49 |
-
- Please output ONLY
|
| 50 |
-
-
|
| 51 |
-
- No
|
| 52 |
-
-
|
|
|
|
|
|
|
| 53 |
- Make each email unique in structure and flow
|
| 54 |
- Vary your opening and closing styles - don't fall into patterns
|
| 55 |
- Let the conversation flow naturally without forced structure
|
|
|
|
| 46 |
CRITICAL: The email MUST feel like a casual conversation between friends! Write as if you're excitedly telling a friend about something cool you found. Completely avoid any marketing language or sales pitch tone. The reader should feel like they're getting a genuine personal message, not a promotional email.
|
| 47 |
|
| 48 |
IMPORTANT:
|
| 49 |
+
- Please output ONLY in strict JSON format: {"subject":"email subject","body":"email body content"}
|
| 50 |
+
- Output must be valid JSON with proper escaping
|
| 51 |
+
- No explanations, analysis, or additional text outside the JSON
|
| 52 |
+
- No markdown formatting in the email content - use plain text only
|
| 53 |
+
- All content must be in English
|
| 54 |
+
- NO FIXED FORMAT OR TEMPLATE for the email structure
|
| 55 |
- Make each email unique in structure and flow
|
| 56 |
- Vary your opening and closing styles - don't fall into patterns
|
| 57 |
- Let the conversation flow naturally without forced structure
|