jake/vOOice
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Improve the fillerword related message in the prompt.

Browse Source
This commit is contained in:
Beingpax 2025-08-20 09:56:48 +05:45
parent a3dc342333
commit 19bc75d36f
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
VoiceInk/Models/PromptTemplates.swift
View File

@ -31,7 +31,7 @@ enum PromptTemplates {
id: UUID(),
title: "System Default",
promptText: """
You are tasked to clean up text in the <TRANSCRIPT> tag. Your job is to clean up the <TRANSCRIPT> text to improve clarity and flow while retaining the speaker's unique personality and style. Correct spelling and grammar. Remove 'ums', 'uhs', and other verbal tics & filler words. Rephrase awkward or convoluted sentences to improve clarity and create a more natural reading experience. Ensure the core message and the speaker's tone are perfectly preserved. Avoid using overly formal or corporate language unless it matches the original style. The final output should sound like a more polished version of the <TRANSCRIPT> text, not like a generic AI.
You are tasked to clean up text in the <TRANSCRIPT> tag. Your job is to clean up the <TRANSCRIPT> text to improve clarity and flow while retaining the speaker's unique personality and style. Correct spelling and grammar. Remove all filler words and verbal tics (e.g., 'um', 'uh', 'like', 'you know', 'yeah'), and any redundant repeated words in the <TRANSCRIPT> text. Rephrase awkward or convoluted sentences to improve clarity and create a more natural reading experience. Ensure the core message and the speaker's tone are perfectly preserved. Avoid using overly formal or corporate language unless it matches the original style. The final output should sound like a more polished version of the <TRANSCRIPT> text, not like a generic AI.
The <CONTEXT_INFORMATION> is provided for reference only to help you understand the context of the <TRANSCRIPT> text. Use it to correct misunderstood technical terms, function names, variable names, and file names.
@ -76,7 +76,7 @@ enum PromptTemplates {
id: UUID(),
title: "Chat",
promptText: """
You are tasked to clean up text in the <TRANSCRIPT> tag for a casual chat conversation. Your job is to clean up the <TRANSCRIPT> text to improve clarity and flow while retaining the speaker's unique personality and style. Correct spelling and grammar. Remove 'ums', 'uhs', 'you know', and other verbal tics & filler words. Rephrase awkward or convoluted sentences to improve clarity and create a more natural reading experience. Ensure the core message and the speaker's tone are perfectly preserved. Avoid using overly formal or corporate language unless it matches the original style or is explicitly requested by the user. The final output should sound like a more polished version of the <TRANSCRIPT> text, not like a generic AI.
You are tasked to clean up text in the <TRANSCRIPT> tag. Your job is to clean up the <TRANSCRIPT> text to improve clarity and flow while retaining the speaker's unique personality and style. Correct spelling and grammar. Remove all filler words and verbal tics (e.g., 'um', 'uh', 'like', 'you know', 'yeah'), and any redundant repeated words in the <TRANSCRIPT> text. Rephrase awkward or convoluted sentences to improve clarity and create a more natural reading experience. Ensure the core message and the speaker's tone are perfectly preserved. Avoid using overly formal or corporate language unless it matches the original style. The final output should sound like a more polished version of the <TRANSCRIPT> text, not like a generic AI.
Primary Rules:
0. The output should always be in the same language as the original <TRANSCRIPT> text.
@ -120,7 +120,7 @@ enum PromptTemplates {
id: UUID(),
title: "Email",
promptText: """
You are tasked to clean up text in the <TRANSCRIPT> text for an email. Your job is to clean up the <TRANSCRIPT> text to improve clarity and flow while retaining the speaker's unique personality and style. Correct spelling and grammar. Remove 'ums', 'uhs', and other verbal tics & filler words. Rephrase awkward or convoluted sentences to improve clarity and create a more natural reading experience. Ensure the core message and the speaker's tone are perfectly preserved. Avoid using overly formal or corporate language unless it matches the original style. The final output should sound like a more polished version of the <TRANSCRIPT> text, not like a generic AI.
You are tasked to clean up text in the <TRANSCRIPT> tag. Your job is to clean up the <TRANSCRIPT> text to improve clarity and flow while retaining the speaker's unique personality and style. Correct spelling and grammar. Remove all filler words and verbal tics (e.g., 'um', 'uh', 'like', 'you know', 'yeah'), and any redundant repeated words in the <TRANSCRIPT> text. Rephrase awkward or convoluted sentences to improve clarity and create a more natural reading experience. Ensure the core message and the speaker's tone are perfectly preserved. Avoid using overly formal or corporate language unless it matches the original style. The final output should sound like a more polished version of the <TRANSCRIPT> text, not like a generic AI.
Primary Rules:
0. The output should always be in the same language as the original <TRANSCRIPT> text.
@ -180,7 +180,7 @@ enum PromptTemplates {
id: UUID(),
title: "Vibe Coding",
promptText: """
Clean up the <TRANSCRIPT> text from a programming session. Your primary goal is to ensure the output is a clean, technically accurate, and readable version of the <TRANSCRIPT> text, while strictly preserving their original intent, and message.
Clean up the <TRANSCRIPT> text from a programming session. Your primary goal is to ensure the output is a clean, technically accurate, and readable version of the <TRANSCRIPT> text, while strictly preserving their original intent, and message. Remove all filler words and verbal tics (e.g., 'um', 'uh', 'like', 'you know', 'yeah'), and any redundant repeated words (e.g., "this this", "function function", "code code").
Primary Rules:
0. The output should always be in the same language as the original <TRANSCRIPT> text.