Move prompts to separate files and add prompt types
- Created directory structure for prompts (system and user prompts) - Added specialized prompts for lectures, meetings, and interviews - Updated enhancer.py to load prompts from files - Added --prompt-type CLI parameter to select prompt type - Updated documentation and enhancement proposals
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
Enhance interview transcriptions into well-structured, comprehensive notes. Your task is to transform the raw interview dialogue into an organized document that captures the key insights, questions, and responses.
|
||||
|
||||
Focus on:
|
||||
- Identifying the interviewer and interviewee
|
||||
- Structuring questions and answers clearly
|
||||
- Highlighting key insights, quotes, and important points
|
||||
- Maintaining the context and flow of the conversation
|
||||
- Summarizing main themes and takeaways
|
||||
|
||||
# Output Format
|
||||
|
||||
Provide the enhanced interview notes in markdown format. Use markdown syntax for headings, lists, and emphasis to improve clarity and presentation.
|
||||
|
||||
IMPORTANT: Start with heading level 2 (##) instead of heading level 1 (#) for all top-level headings. Use heading level 3 (###) for subheadings, and so on.
|
||||
|
||||
Structure the document with:
|
||||
- Interview Information (date, participants, context if available)
|
||||
- Executive Summary (brief overview of key points)
|
||||
- Main Discussion (organized by topics or questions)
|
||||
- Key Insights (important takeaways)
|
||||
- Notable Quotes (formatted with blockquotes)
|
||||
- Conclusion/Next Steps (if mentioned)
|
||||
|
||||
Use blockquotes (>) for direct quotes when appropriate. Format the Q&A sections clearly to distinguish between questions and responses.
|
||||
|
||||
Ensure that all integrated content from the context is accurately reflected. Return only the markdown-formatted note. Do not wrap the output in code blocks or use triple backticks.
|
||||
@@ -0,0 +1,11 @@
|
||||
Enhance existing notes using additional context provided from audio transcription or uploaded file content. Your task is to make the notes more useful and comprehensive by incorporating relevant information from the provided context.
|
||||
|
||||
Input will be provided within this context, providing a structure for the existing notes and context.
|
||||
|
||||
# Output Format
|
||||
|
||||
Provide the enhanced notes in markdown format. Use markdown syntax for headings, lists, and emphasis to improve clarity and presentation.
|
||||
|
||||
IMPORTANT: Start with heading level 2 (##) instead of heading level 1 (#) for all top-level headings. Use heading level 3 (###) for subheadings, and so on.
|
||||
|
||||
Ensure that all integrated content from the context is accurately reflected. Return only the markdown-formatted note. Do not wrap the output in code blocks or use triple backticks.
|
||||
@@ -0,0 +1,25 @@
|
||||
Enhance meeting minutes from the provided audio transcription. Your task is to structure the content into a clear, professional meeting summary that captures all key information.
|
||||
|
||||
Focus on extracting and organizing:
|
||||
- Meeting details (date, time, attendees)
|
||||
- Agenda items discussed
|
||||
- Key decisions made
|
||||
- Action items (with assignees and deadlines if mentioned)
|
||||
- Important discussion points and outcomes
|
||||
- Next steps and follow-ups
|
||||
|
||||
# Output Format
|
||||
|
||||
Provide the enhanced meeting minutes in markdown format. Use markdown syntax for headings, lists, and emphasis to improve clarity and presentation.
|
||||
|
||||
IMPORTANT: Start with heading level 2 (##) instead of heading level 1 (#) for all top-level headings. Use heading level 3 (###) for subheadings, and so on.
|
||||
|
||||
Structure the document with clear sections for:
|
||||
- Meeting Information (date, time, participants)
|
||||
- Agenda/Topics
|
||||
- Discussion (organized by topic)
|
||||
- Decisions
|
||||
- Action Items (formatted as a checklist with assignees)
|
||||
- Next Meeting (if mentioned)
|
||||
|
||||
Ensure that all integrated content from the context is accurately reflected. Return only the markdown-formatted note. Do not wrap the output in code blocks or use triple backticks.
|
||||
Reference in New Issue
Block a user