style: improve summary prompt & visual

This commit is contained in:
Owen Gretzinger
2025-07-12 00:51:55 -04:00
parent 5e5105e8f8
commit cf87654fa7
3 changed files with 31 additions and 14 deletions
+25 -9
View File
@@ -3,18 +3,32 @@ Your job is to generate enhanced meeting notes for the following meeting:
Title: {{meeting_title}}
Date & Time: {{meeting_date}}
Here are important instructions:
<important>
You will be provided with:
- a transcript of the meeting
- information the user provided as additional context
- any additional notes the user manually noted down
Your enhanced meeting notes should include:
Your enhanced meeting notes should include the following sections:
- the key discussion points
- action items
- decisions made
- any deadlines or follow-up required
Create the meeting notes in markdown formatting, and only include these sections. The title, attendees, date, and other metadata must not be included as this information is already displayed elsewhere in the UI. Your job is the notes themselves only.
Include only these section headers, unless the user requests otherwise (see formatting_requests section).
The title, attendees, date, and other metadata must not be included as this information is already displayed elsewhere in the UI. Your job is the notes themselves only.
You have the following formatting options:
- Headings (markdown-like headings). Use 2 hashtags for headings (“## [heading]”)
- Bullet points & indented bullet points. Use 4 spaces to create an indented bullet point.
Note that you cannot use asterisks to bold text or use any other types of formatting.
Keep each bullet point concise (5-10 words), and avoid having too many with unimportant info. Prioritize clarity and readability.
</important>
Here are explanations of how to handle the different information you will be given:
@@ -23,7 +37,9 @@ Transcripts use specific labels to identify speakers:
- "Me": The user using this meeting notes application. Technically speaking, these utterances were picked up by the user's microphone.
- "Them": The other person or other people in the meeting. Technically speaking, these utterances were picked up through system audio.
Audio transcription often mislabels speakers. Use context clues to infer the correct speaker.
If there is duplicated transcripts between "Me" and "Them", it means that it was actually "Them" who said it (most likely the user is playing the audio out loud on speakers).
Keep in mind that transcripts are not always precise, so use context cues and intelligence to parse utterances.
The transcript of the meeting is provided in <transcript> tags below.
</transcript_explanation>
@@ -45,15 +61,15 @@ Here are some examples of things the user may note down, how to recognize them,
<key_details>
The user may note down key details they want to include in the meeting notes.
How to recognize: the user writes things down that are related to content you can see in the transcript.
How to recognize: there are notes that correspond to content you can see in the transcript.
How to handle: ensure they are included and prioritized in the enhanced meeting notes.
How to handle: ensure these details are included and prioritized in the enhanced meeting notes.
</key_details>
<user_thoughts>
The user may note down thoughts that they don't say out loud (ex. thoughts on a candidate they're interviewing).
How to recognize: the user writes things down that are not related to content you can see in the transcript.
How to recognize: there are notes that do not correspond to content in the transcript.
How to handle: include in its own section, or tagged onto other points throughout where relevant.
</user_thoughts>
@@ -61,14 +77,14 @@ How to handle: include in its own section, or tagged onto other points throughou
<formatting_requests>
The user may note down formatting requests they want to include in the meeting notes.
How to recognize: the user provides a meeting notes structure without filling in the content (ex. they use hashtags to create markdown headers but don't fill in the content).
How to recognize: the user provides a meeting notes structure without filling in the content (ex. they use hashtags to create section headers but don't fill in the content).
How to handle: structure the enhanced meeting notes according to the user's notes.
</formatting_requests>
In general, the user's notes are very important. These are things that the user has specifically manually written down.
In general, the user's notes are very important. These are things that the user has specifically manually written down. These notes should be given the most attention when crafting the summary.
These notes are provided in <user_notes> tags below.
The user's notes are provided in <user_notes> tags below.
</user_notes_explanation>
<transcript>