Commit ·
f7be280
1
Parent(s): 3e08cbf
- Adding emojis per brand for main and subsequent messages
Browse files
Config_files/message_system_config.json
CHANGED
|
@@ -17,8 +17,10 @@
|
|
| 17 |
"topics",
|
| 18 |
"genres"
|
| 19 |
],
|
| 20 |
-
"AI_Jargon": ["elevate", "enhance", "reignite", "passion", "boost", "fuel", "thrill", "revive", "spark", "performing", "fresh", "tone"],
|
| 21 |
"header_limit": 30,
|
| 22 |
"message_limit": 110
|
| 23 |
}
|
| 24 |
|
|
|
|
|
|
|
|
|
| 17 |
"topics",
|
| 18 |
"genres"
|
| 19 |
],
|
| 20 |
+
"AI_Jargon": ["elevate", "enhance", "reignite", "passion", "boost", "fuel", "thrill", "revive", "spark", "performing", "fresh", "tone", "Enthusiasm"],
|
| 21 |
"header_limit": 30,
|
| 22 |
"message_limit": 110
|
| 23 |
}
|
| 24 |
|
| 25 |
+
|
| 26 |
+
|
Messaging_system/CoreConfig.py
CHANGED
|
@@ -214,7 +214,24 @@ class CoreConfig:
|
|
| 214 |
"drumeo": "Drum",
|
| 215 |
"pianote": "Piano",
|
| 216 |
"guitareo": "Guitar",
|
| 217 |
-
"singeo": "Singing (
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 218 |
}
|
| 219 |
|
| 220 |
return switch_dict[self.brand]
|
|
|
|
| 214 |
"drumeo": "Drum",
|
| 215 |
"pianote": "Piano",
|
| 216 |
"guitareo": "Guitar",
|
| 217 |
+
"singeo": "Singing (Voice)"
|
| 218 |
+
}
|
| 219 |
+
|
| 220 |
+
return switch_dict[self.brand]
|
| 221 |
+
|
| 222 |
+
# ==============================================================
|
| 223 |
+
|
| 224 |
+
def get_emoji(self):
|
| 225 |
+
"""
|
| 226 |
+
get the emoji based on the brand
|
| 227 |
+
:return: instrument (str)
|
| 228 |
+
"""
|
| 229 |
+
# map
|
| 230 |
+
switch_dict = {
|
| 231 |
+
"drumeo": "🥁",
|
| 232 |
+
"pianote": "🎹",
|
| 233 |
+
"guitareo": "🎸",
|
| 234 |
+
"singeo": "🎤"
|
| 235 |
}
|
| 236 |
|
| 237 |
return switch_dict[self.brand]
|
Messaging_system/MultiMessage.py
CHANGED
|
@@ -141,7 +141,14 @@ The user has still not re-engaged. Generate the *next* follow up push notificati
|
|
| 141 |
to return and continue their music learning.
|
| 142 |
The user is a {str(self.Core.get_instrument())} student.
|
| 143 |
|
| 144 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 145 |
- "header" must be fewer than {header_limit} characters.
|
| 146 |
- "message" must be fewer than {message_limit} characters.
|
| 147 |
- Output must be valid JSON with exactly two keys: "header" and "message".
|
|
|
|
| 141 |
to return and continue their music learning.
|
| 142 |
The user is a {str(self.Core.get_instrument())} student.
|
| 143 |
|
| 144 |
+
# General instructions:
|
| 145 |
+
|
| 146 |
+
- Make all parts of the message highly **personalized**, **eye-catching**, and **bring curiosity**
|
| 147 |
+
- Only use {self.Core.get_emoji()} emoji if needed.**
|
| 148 |
+
- Every word should contribute to maximizing impact and engagement, so start directly with the message content without greetings or closing phrases.
|
| 149 |
+
- Avoid using same or similar words so close together in "message" and "header", and make sure there is no grammar problem.
|
| 150 |
+
|
| 151 |
+
# Constraints:
|
| 152 |
- "header" must be fewer than {header_limit} characters.
|
| 153 |
- "message" must be fewer than {message_limit} characters.
|
| 154 |
- Output must be valid JSON with exactly two keys: "header" and "message".
|
Messaging_system/PromptGenerator.py
CHANGED
|
@@ -289,8 +289,7 @@ class PromptGenerator:
|
|
| 289 |
- The message is a **mobile push notification**.
|
| 290 |
- Make all parts of the message highly **personalized**, **eye-catching**, and **bring curiosity**
|
| 291 |
- ** Keep the First sentence as "header": short and less than 30 character **.
|
| 292 |
-
- ** For the "header", Use a space following with a proper emoji at the end
|
| 293 |
-
- Use drum emoji or general music emojis (e.g. 🥁, 🎶, 🎵), and Other emojis that relate to motivation, progress, inspiration, and create curiosity can also be used (like 🔥, 🚀, 💪, 🎉, 👀)
|
| 294 |
- **Keep the "message" concise and under 100 characters**.
|
| 295 |
- Every word should contribute to maximizing impact and engagement, so start directly with the message content without greetings or closing phrases.
|
| 296 |
- Avoid using same or similar words so close together in "message" and "header", and make sure there is no grammar problem.
|
|
|
|
| 289 |
- The message is a **mobile push notification**.
|
| 290 |
- Make all parts of the message highly **personalized**, **eye-catching**, and **bring curiosity**
|
| 291 |
- ** Keep the First sentence as "header": short and less than 30 character **.
|
| 292 |
+
- ** For the "header", Use a space following with a proper emoji at the end, only use {self.Core.get_emoji()} emoji **
|
|
|
|
| 293 |
- **Keep the "message" concise and under 100 characters**.
|
| 294 |
- Every word should contribute to maximizing impact and engagement, so start directly with the message content without greetings or closing phrases.
|
| 295 |
- Avoid using same or similar words so close together in "message" and "header", and make sure there is no grammar problem.
|
Messaging_system/protection_layer.py
CHANGED
|
@@ -52,7 +52,7 @@ class ProtectionLayer:
|
|
| 52 |
"""
|
| 53 |
return f"""
|
| 54 |
1. No two consecutive sentences should end with exclamation points, change one of them to dot.
|
| 55 |
-
2. ONLY Capitalize the first word of the 'header' as well as names or any proper nouns. Other words in the 'header' must be lowercase. (e.g. Jump back in, David!
|
| 56 |
3. If there is any grammar error in the message, you must fix it.
|
| 57 |
4. Always use "the" before proper nouns, including any titles of the recommended content, if the title was in the message.
|
| 58 |
5. Do not include any words that explicitly or implicitly reference a time-related concept (e.g., “new,” “recent,” “latest,” “upcoming,” etc.).
|
|
|
|
| 52 |
"""
|
| 53 |
return f"""
|
| 54 |
1. No two consecutive sentences should end with exclamation points, change one of them to dot.
|
| 55 |
+
2. ONLY Capitalize the first word of the 'header' as well as names or any proper nouns. Other words in the 'header' must be lowercase. (e.g. Jump back in, David!)
|
| 56 |
3. If there is any grammar error in the message, you must fix it.
|
| 57 |
4. Always use "the" before proper nouns, including any titles of the recommended content, if the title was in the message.
|
| 58 |
5. Do not include any words that explicitly or implicitly reference a time-related concept (e.g., “new,” “recent,” “latest,” “upcoming,” etc.).
|