mirror of
https://github.com/aljazceru/vibeline.git
synced 2025-12-18 23:14:29 +01:00
refactor: update plugin prompts to match original .md versions and remove .md files
This commit is contained in:
@@ -1,25 +0,0 @@
|
||||
You are a task extraction specialist. Your job is to identify and format actionable items from the transcript.
|
||||
|
||||
Transcript:
|
||||
{transcript}
|
||||
|
||||
Summary:
|
||||
{summary}
|
||||
|
||||
Please extract all actionable items from the transcript and format them as a markdown list. Each item should:
|
||||
1. Be clear and specific
|
||||
2. Start with a verb
|
||||
3. Be self-contained (understandable without context)
|
||||
4. Include any relevant deadlines or priorities if mentioned
|
||||
|
||||
Format the output as:
|
||||
# Action Items
|
||||
|
||||
- [ ] First action item
|
||||
- [ ] Second action item
|
||||
- [ ] Third action item
|
||||
|
||||
If no action items are found, output:
|
||||
# Action Items
|
||||
|
||||
No action items found in this transcript.
|
||||
@@ -4,9 +4,28 @@ model: llama2 # Optional, falls back to OLLAMA_MODEL from .env
|
||||
type: or # and, or
|
||||
run: matching # always, matching
|
||||
prompt: |
|
||||
Extract action items and todos from the following transcript.
|
||||
Format each item as a markdown checkbox.
|
||||
If there are no action items or todos, output "No action items or todos found."
|
||||
You are a task extraction specialist. Your job is to identify and format actionable items from the transcript.
|
||||
|
||||
Transcript:
|
||||
{transcript}
|
||||
{transcript}
|
||||
|
||||
Summary:
|
||||
{summary}
|
||||
|
||||
Please extract all actionable items from the transcript and format them as a markdown list. Each item should:
|
||||
1. Be clear and specific
|
||||
2. Start with a verb
|
||||
3. Be self-contained (understandable without context)
|
||||
4. Include any relevant deadlines or priorities if mentioned
|
||||
|
||||
Format the output as:
|
||||
# Action Items
|
||||
|
||||
- [ ] First action item
|
||||
- [ ] Second action item
|
||||
- [ ] Third action item
|
||||
|
||||
If no action items are found, output:
|
||||
# Action Items
|
||||
|
||||
No action items found in this transcript.
|
||||
@@ -1,16 +0,0 @@
|
||||
Based on the following transcript and its summary, create a detailed app idea specification. The specification should include:
|
||||
1. App name and tagline
|
||||
2. Problem statement
|
||||
3. Target audience
|
||||
4. Key features
|
||||
5. Technical considerations
|
||||
6. User flow
|
||||
7. Potential challenges
|
||||
|
||||
Transcript:
|
||||
{transcript}
|
||||
|
||||
Summary:
|
||||
{summary}
|
||||
|
||||
App Idea Specification:
|
||||
22
plugins/app_idea.yaml
Normal file
22
plugins/app_idea.yaml
Normal file
@@ -0,0 +1,22 @@
|
||||
name: app_idea
|
||||
description: Generate detailed app idea specifications from transcripts
|
||||
model: llama2 # Optional, falls back to OLLAMA_MODEL from .env
|
||||
type: or # and, or
|
||||
run: matching # always, matching
|
||||
prompt: |
|
||||
Based on the following transcript and its summary, create a detailed app idea specification. The specification should include:
|
||||
1. App name and tagline
|
||||
2. Problem statement
|
||||
3. Target audience
|
||||
4. Key features
|
||||
5. Technical considerations
|
||||
6. User flow
|
||||
7. Potential challenges
|
||||
|
||||
Transcript:
|
||||
{transcript}
|
||||
|
||||
Summary:
|
||||
{summary}
|
||||
|
||||
App Idea Specification:
|
||||
@@ -1,14 +0,0 @@
|
||||
Based on the following transcript and its summary, create a draft blog post. The draft should include:
|
||||
1. A compelling title
|
||||
2. An introduction that hooks the reader
|
||||
3. Main sections with clear headings
|
||||
4. Key points from the transcript
|
||||
5. A conclusion
|
||||
|
||||
Transcript:
|
||||
{transcript}
|
||||
|
||||
Summary:
|
||||
{summary}
|
||||
|
||||
Blog Post Draft:
|
||||
20
plugins/blog_post.yaml
Normal file
20
plugins/blog_post.yaml
Normal file
@@ -0,0 +1,20 @@
|
||||
name: blog_post
|
||||
description: Generate draft blog posts from transcripts
|
||||
model: llama2 # Optional, falls back to OLLAMA_MODEL from .env
|
||||
type: or # and, or
|
||||
run: matching # always, matching
|
||||
prompt: |
|
||||
Based on the following transcript and its summary, create a draft blog post. The draft should include:
|
||||
1. A compelling title
|
||||
2. An introduction that hooks the reader
|
||||
3. Main sections with clear headings
|
||||
4. Key points from the transcript
|
||||
5. A conclusion
|
||||
|
||||
Transcript:
|
||||
{transcript}
|
||||
|
||||
Summary:
|
||||
{summary}
|
||||
|
||||
Blog Post Draft:
|
||||
@@ -1,4 +0,0 @@
|
||||
Please provide a short, 2-3 sentence summary of the following transcript. The summary should never be longer than a single paragraph.
|
||||
|
||||
Transcript:
|
||||
{transcript}
|
||||
@@ -4,8 +4,7 @@ model: llama2 # Optional, falls back to OLLAMA_MODEL from .env
|
||||
type: or # and, or
|
||||
run: always # always, matching
|
||||
prompt: |
|
||||
Please provide a concise summary of the following transcript.
|
||||
Focus on the main points and key takeaways.
|
||||
Please provide a short, 2-3 sentence summary of the following transcript. The summary should never be longer than a single paragraph.
|
||||
|
||||
Transcript:
|
||||
{transcript}
|
||||
Reference in New Issue
Block a user