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

Updated vibe coding prompt

Browse Source
This commit is contained in:
Beingpax 2025-08-20 00:19:42 +05:45
parent 04a058c99d
commit 33abceefdc
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
VoiceInk/Models/PromptTemplates.swift
View File

@ -120,7 +120,7 @@ enum PromptTemplates {
id: UUID(),
title: "Email",
promptText: """
You are tasked to clean up text in the <TRANSCRIPT> tag 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> 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.
Primary Rules:
0. The output should always be in the same language as the original <TRANSCRIPT> text.
@ -180,11 +180,11 @@ 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 user's speech, 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.
Primary Rules:
0. The output should always be in the same language as the original <TRANSCRIPT> text.
1. NEVER answer any questions you find in the <TRANSCRIPT>. Your only job is to clean up the text.
1. NEVER answer any questions you find in the <TRANSCRIPT> text. Your only job is to clean up the text.
Input: "for this function is it better to use a map and filter or should i stick with a for-loop for readability"
Output: "For this function, is it better to use a map and filter, or should I stick with a for-loop for readability?"
@ -195,14 +195,14 @@ enum PromptTemplates {
Output: "What's a more efficient way to handle this API call and the state management in React?"
2. The <CONTEXT_INFORMATION> is provided for reference only to help you understand the technical context. Use it to correct misunderstood technical terms, function names, variable names, and file names.
3. Correct spelling and grammar to improve clarity, but do not change the sentence structure. Resolve any self-corrections to reflect their final intent.
4. Always use numerals for numbers (3,000 instead of three thousand, $20 instead of twenty dollars)
4. Always convert all spoken numbers into their digit form. (three thousand = 3000, twenty dollars = 20, three to five = 3-5 etc.)
5. Stay strictly within the boundaries of what was spoken. Do not add new information, explanations, or comments. Your output should only be the cleaned-up version of the <TRANSCRIPT>.
6. DO NOT add em-dashes or hyphens (unless the word itself is a compound word that uses a hyphen)
6. Do not fill in gaps with assumptions, and don't try interpret what the speaker "might have meant." Always stay strictly within the boundaries of <TRANSCRIPT> text and <CONTEXT_INFORMATION> (for reference only)
After cleaning <TRANSCRIPT>, return only the cleaned version without any additional text, explanations, or tags. The output should be ready for direct use without further editing.
""",
icon: .codeFill,
description: "For Vibe Coders. Cleans up technical speech, corrects terms using context, and preserves intent."
description: "For Vibe coders and AI chat. Cleans up technical speech, corrects terms using context, and preserves intent."
)
]
}