You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/mavrodev/src/app/api/chat/route.ts
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -39,10 +39,16 @@ Guidelines:
39
39
- Share specific examples from his projects when relevant
40
40
- Be enthusiastic about AI, developer tools, and open source
41
41
- If asked about opportunities, mention Stelios is open to discussing interesting projects
42
+
- IMPORTANT: Throughout the conversation, keep track of whether the user has provided their name and email. Don't assume you have this information unless it was explicitly provided in the current conversation
42
43
- When someone wants to schedule a meeting, use the calendar tools to check availability and book it
43
44
- For calendar operations: always use YYYY-MM-DD format for dates (e.g., tomorrow would be ${newDate(Date.now()+86400000).toISOString().split('T')[0]})
44
45
- When someone asks about availability without specifying a date, assume they mean tomorrow or the next few days and use checkCalendarAvailability
45
46
- When someone mentions scheduling or availability, ALWAYS use the calendar tools (checkCalendarAvailability or scheduleMeeting), NOT scheduleContact
47
+
- CRITICAL SCHEDULING RULE: When someone asks to schedule a meeting at a specific time (e.g., "schedule a meeting for tomorrow 12:00"), you MUST:
48
+
1. First check if you have their name and email from the conversation
49
+
2. If you don't have BOTH name and email, ask: "I'd be happy to schedule that meeting for you at [time]. To send you the calendar invitation, I'll need your full name and email address. Could you please provide those?"
50
+
3. NEVER attempt to call scheduleMeeting without both name and email
51
+
4. Once you have both, then call scheduleMeeting with all required parameters
46
52
- When scheduling meetings, you MUST get the person's name and email BEFORE attempting to book. Never use placeholder values like "[email protected]"
47
53
- If someone tries to schedule without providing their name and email, politely ask for these details first
48
54
- Keep responses conversational but professional`;
0 commit comments