07
SNIPPET
LIBRARY
Ready-to-use text expansion templates. Copy any snippet below, paste it into Wordy, and start typing less.
Express route handler — type ;apiget/users then space to expand
FIELDDROPDOWNREGEXCURSOR
/**
* {{uppercase:{{method}}}} {{path}}
* {{field:Endpoint description}}
*/
router.{{method}}('{{path}}', async (req, res) => {
try {
{{cursor}}
res.status({{dropdown:Success Status:200,201,204}}).json({
success: true,
data: {{field:response data}},
})
} catch (error) {
res.status({{dropdown:Error Status:400,404,500}}).json({
success: false,
error: error.message,
})
}
})
Acknowledge a bug and request diagnostic details
FIELDDROPDOWNVARIABLES
Hi {{field:Customer Name}},
Thank you for reporting this. I'm sorry you're running into trouble — let me help.
To investigate this further, could you provide:
- Your operating system and version: {{field:e.g. macOS 15.2}}
- App version: {{field:e.g. 1.4.2}}
- Steps to reproduce the issue
- Any error messages you're seeing (screenshots help!)
Priority: {{dropdown:Priority:Low — cosmetic issue,Medium — feature partially broken,High — feature completely broken,Critical — data loss or crash}}
I've flagged this with our engineering team and we'll keep you updated on progress.
Thanks for your patience,
{{#Name}}
{{#Company}} Support
Patient discharge summary with medications and follow-up care
FIELDDROPDOWNDATE
DISCHARGE INSTRUCTIONS
Patient: {{field:Patient Name}}
Date of Discharge: {{date:long}}
Diagnosis: {{field:Discharge diagnosis}}
Medications:
1. {{field:Medication 1 — dose, frequency, duration}}
2. {{field:Medication 2 — dose, frequency, duration}}
3. {{field:Medication 3 if applicable}}
Activity Restrictions:
{{dropdown:Activity:No restrictions,Light activity only,Bed rest,No lifting over 10 lbs}}
Wound / Site Care:
{{field:Wound care instructions or N/A}}
Diet:
{{dropdown:Diet:Regular diet,Clear liquids for 24 hours then advance as tolerated,Low sodium diet,Diabetic diet}}
Follow-Up Appointment:
Provider: {{field:Provider name}}
Date: {{field:Follow-up date}}
Location: {{field:Clinic address or phone}}
Return to the emergency department if you experience:
- {{field:Warning sign 1}}
- {{field:Warning sign 2}}
- {{field:Warning sign 3}}
Questions? Call: {{field:Contact number}}
console.group block — type ;dbgMyVar then space to expand with variable name
REGEXCURSOR
console.group('🔍 {{name}}')
console.log('input:', {{name}})
console.time('{{name}}')
{{cursor}}
console.timeEnd('{{name}}')
console.groupEnd()
Internal escalation template with context for the next tier
FIELDDROPDOWNDATEVARIABLES
ESCALATION — {{date:long}}
Customer: {{field:Customer Name}}
Account: {{field:Account ID or email}}
Tier: {{dropdown:Tier:Tier 2 — Technical,Tier 3 — Engineering,Manager — Retention}}
Summary: {{field:Brief description of the issue}}
What's been tried:
- {{field:Step 1 attempted}}
- {{field:Step 2 attempted}}
Customer sentiment: {{dropdown:Sentiment:Calm and patient,Frustrated but cooperative,Upset — handle with care,Churn risk — high priority}}
Ticket history: {{field:Link to ticket or conversation}}
Please pick this up at your earliest convenience. The customer has been informed that a specialist will follow up.
— {{#Name}}
Acknowledge feature request and set expectations
FIELDVARIABLES
Hi {{field:Customer Name}},
Thank you for suggesting {{field:Feature description}}! We really appreciate you taking the time to share this.
I've added your request to our product backlog and flagged it for the team. While I can't guarantee a timeline, customer feedback directly influences our roadmap.
Here's what happens next:
- Our product team reviews all requests during sprint planning
- Popular requests get prioritized faster
- We'll notify you if this ships in a future update
In the meantime, {{field:Workaround or related feature suggestion}}.
Thanks for helping us make {{#Company}} better!
{{#Name}}
{{#Company}} Support
Polite follow-up after a meeting or unanswered email
FIELDDROPDOWNVARIABLES
Hi {{field:Recipient Name}},
I wanted to follow up on {{dropdown:Context:our conversation from last week,my previous email,the proposal I sent over,our recent meeting}}.
{{field:Key point or action item to reference}}
Would love to keep this moving forward. Let me know if you have any questions or if there's anything else you need from my end.
Happy to jump on a quick call if that's easier.
Best,
{{#Name}}
Structured git commit message following the Conventional Commits spec
FIELDDROPDOWN
{{dropdown:Type:feat,fix,refactor,docs,test,chore,perf,ci}}({{field:scope}}): {{field:short description}}
{{field:Detailed explanation of what changed and why}}
{{dropdown:Footer:Closes #issue,Refs #issue,BREAKING CHANGE:,None}}
Introduce yourself or make a warm introduction between two contacts
FIELDTEXTAREADROPDOWNVARIABLES
Hi {{field:Recipient Name}},
{{dropdown:Opening:I wanted to introduce myself,I'd like to connect you with someone}} — {{field:brief context or reason for introduction}}.
A little background:
{{textarea:2-3 sentences of relevant context}}
I think there's a great opportunity to {{field:collaborate / discuss / explore}} here. {{dropdown:Closing:Would you be open to a quick chat?,I'll let you two take it from here.,Let me know if you'd like me to set up a call.}}
Best,
{{#Name}}
JSDoc block — type ;docMyFunc then space to expand with function name captured
FIELDREGEXCURSOR
/**
* {{field:Brief description}}
*
* @param {{{field:type}}} {{field:paramName}} - {{field:param description}}
* @returns {{{field:returnType}}} {{field:return description}}
* @throws {{{field:ErrorType}}} {{field:when does it throw}}
*
* @example
* {{fn}}({{field:example args}})
*/
{{cursor}}
Auto-reply template with return date and emergency contact
FIELDVARIABLES
Thank you for your email. I'm currently out of the office and will return on {{field:Return date}}.
During this time I'll have limited access to email. I'll respond to your message when I'm back.
If your matter is urgent, please contact {{field:Backup contact name}} at {{field:Backup email or phone}}.
Best,
{{#Name}}
Professional meeting request with proposed times
FIELDDATEVARIABLES
Hi {{field:Recipient Name}},
I'd like to schedule a meeting to discuss {{field:Topic}}.
Would any of these times work for you?
- {{date:+1d:EEEE, MMMM d}} at {{field:Time 1}}
- {{date:+2d:EEEE, MMMM d}} at {{field:Time 2}}
- {{date:+3d:EEEE, MMMM d}} at {{field:Time 3}}
Duration: {{field:30 minutes}}
Location: {{field:Zoom / Office / Google Meet link}}
If none of these work, let me know your availability and I'll adjust.
Best,
{{#Name}}
Step-by-step password reset guide with security reminder
FIELDVARIABLES
Hi {{field:Customer Name}},
No worries — let's get you back into your account.
To reset your password:
1. Go to {{field:Reset URL}}
2. Enter the email address associated with your account
3. Check your inbox for a reset link (expires in 30 minutes)
4. Choose a new password
If you don't receive the email within a few minutes, check your spam folder.
For security, we recommend:
- Using a unique password you haven't used elsewhere
- Enabling two-factor authentication in your account settings
Still having trouble? Just reply here and we'll sort it out.
Best,
{{#Name}}
{{#Company}} Support
Insurance prior authorization with medical necessity justification
FIELDTEXTAREADATEDROPDOWNVARIABLES
PRIOR AUTHORIZATION REQUEST
Date: {{date:long}}
To: {{field:Insurance Company}}
Member ID: {{field:Member/Policy ID}}
Group: {{field:Group number}}
Patient: {{field:Patient Name}}
DOB: {{field:Date of birth}}
Diagnosis: {{field:ICD-10 code and description}}
Requested Service:
{{field:Procedure, medication, or service with CPT/HCPCS code}}
Medical Necessity Justification:
{{textarea:Clinical rationale — why this service is required}}
Previous Treatments Tried:
1. {{field:Prior treatment 1 — result}}
2. {{field:Prior treatment 2 — result}}
Urgency: {{dropdown:Urgency:Standard,Expedited — clinical urgency}}
Supporting documentation is attached. Please contact our office with any questions.
{{#ProviderName}}, {{#ProviderCredentials}}
NPI: {{field:NPI number}}
Phone: {{#PracticePhone}}
Fax: {{#PracticeFax}}
Follow-up visit documentation for ongoing patient care
FIELDDROPDOWNDATE
PROGRESS NOTE — {{date:long}}
Patient: {{field:Patient Name}}
Visit Type: {{dropdown:Visit Type:Follow-up,Post-op,Medication check,Annual wellness,Telehealth}}
Interval History:
Patient reports {{dropdown:Change:improvement,no change,worsening}} since last visit on {{field:last visit date}}.
{{field:Relevant interval changes}}
Current Medications (changes noted):
{{field:Medication list with any changes}}
Exam:
{{field:Focused physical exam findings}}
Assessment:
1. {{field:Diagnosis}} — {{dropdown:Status:Stable,Improving,Worsening,Resolved}}
Plan:
- {{field:Treatment adjustments}}
- {{field:Orders: labs, imaging, referrals}}
- Follow-up in {{dropdown:Follow-up:1 week,2 weeks,1 month,3 months,6 months,PRN}}
Gentle nudge about a pending deadline or action item
FIELDVARIABLES
Hi {{field:Recipient Name}},
Just a friendly reminder that {{field:Task or deliverable}} is due on {{field:Due date}}.
Here's a quick summary of what's needed:
- {{field:Action item 1}}
- {{field:Action item 2}}
If you've already taken care of this, please disregard. Otherwise, let me know if you need more time or have any questions.
Thanks,
{{#Name}}
Specialist referral with clinical summary and reason for consultation
FIELDTEXTAREADATEDROPDOWNVARIABLES
Date: {{date:long}}
RE: Referral for {{field:Patient Name}}
DOB: {{field:Date of birth}}
Insurance: {{field:Insurance provider and ID}}
Dear Dr. {{field:Specialist Name}},
I am referring {{field:Patient Name}} to your care for evaluation of {{field:Condition or reason for referral}}.
Clinical Summary:
{{textarea:Brief history and relevant findings}}
Current Medications:
{{field:List of relevant medications}}
Relevant Studies:
{{field:Lab results, imaging, or other diagnostics}}
Urgency: {{dropdown:Urgency:Routine,Urgent — within 1 week,Emergent — immediate}}
Please send consultation notes to our office at your earliest convenience. Thank you for seeing this patient.
Sincerely,
{{#ProviderName}}, {{#ProviderCredentials}}
{{#PracticeName}}
Phone: {{#PracticePhone}}
Fax: {{#PracticeFax}}
Standard clinical documentation format for patient encounters
FIELDDROPDOWNCURSOR
SUBJECTIVE:
Chief Complaint: {{field:Chief complaint}}
HPI: {{field:History of present illness}}
ROS: {{dropdown:ROS:Negative except as noted in HPI,See detailed ROS below}}
Current Medications: {{field:List current medications}}
Allergies: {{field:NKDA or list allergies}}
OBJECTIVE:
Vitals: BP {{field:120/80}} | HR {{field:72}} | Temp {{field:98.6}}°F | RR {{field:16}} | SpO2 {{field:99}}%
General: {{field:Alert, oriented, no acute distress}}
{{field:Relevant physical exam findings}}
ASSESSMENT:
1. {{field:Primary diagnosis}} — {{dropdown:Course:New,Established,Worsening,Improving}}
2. {{field:Secondary diagnosis if applicable}}
PLAN:
1. {{field:Treatment plan for diagnosis 1}}
2. {{field:Additional orders, referrals, or follow-up}}
Follow-up: {{field:Timeframe}}
{{cursor}}
Weekly or milestone project status report
FIELDDROPDOWNDATEVARIABLES
Project Status Update — {{date:long}}
Project: {{field:Project Name}}
Status: {{dropdown:Status:On Track,At Risk,Blocked,Completed}}
Completed this period:
- {{field:Accomplishment 1}}
- {{field:Accomplishment 2}}
In progress:
- {{field:Current task 1}}
- {{field:Current task 2}}
Blockers / Risks:
- {{field:Blocker or "None"}}
Next milestone: {{field:Next milestone}} — target {{field:Target date}}
Let me know if you have any questions.
{{#Name}}
Confirm refund processing with timeline and next steps
FIELDDROPDOWNVARIABLES
Hi {{field:Customer Name}},
Your refund of {{field:Amount}} has been processed.
Refund details:
- Amount: {{field:Amount}}
- Method: {{dropdown:Method:Original payment method,Store credit,Bank transfer}}
- Expected timeline: 5–10 business days depending on your bank
Reason noted: {{field:Refund reason}}
Your account will remain active until the end of your current billing period. You're welcome to come back anytime — we'd love to have you.
Is there anything else I can help with?
Best,
{{#Name}}
{{#Company}} Support
Jest/Vitest describe + it block — type ;testAuth then space to expand
FIELDDROPDOWNREGEXCURSOR
describe('{{subject}}', () => {
{{dropdown:Setup:beforeEach,beforeAll}}(() => {
{{field:setup code}}
})
it('should {{field:expected behavior}}', {{dropdown:Arrow:() =>,async () =>}} {
// Arrange
{{field:setup}}
// Act
{{field:action}}
// Assert
expect({{field:actual}}).{{dropdown:Matcher:toBe,toEqual,toHaveBeenCalledWith,toThrow}}({{field:expected}})
})
it('should {{field:edge case or error behavior}}', () => {
{{cursor}}
})
})
Immunization documentation with lot tracking and consent
FIELDDROPDOWNDATE
VACCINE ADMINISTRATION RECORD
Date: {{date:long}}
Patient: {{field:Patient Name}}
DOB: {{field:Date of birth}}
Vaccine: {{dropdown:Vaccine:Influenza (IIV4),COVID-19 (Updated),Tdap,Pneumococcal (PCV20),Shingrix (RZV),Hepatitis B,HPV (Gardasil 9),MMR}}
Manufacturer: {{field:Manufacturer name}}
Lot #: {{field:Lot number}}
Expiration: {{field:Expiration date}}
Dose: {{field:0.5 mL}}
Route: {{dropdown:Route:Intramuscular (IM),Subcutaneous (SC),Intradermal (ID)}}
Site: {{dropdown:Site:Left deltoid,Right deltoid,Left anterolateral thigh,Right anterolateral thigh}}
VIS provided: {{date:long}}
Consent obtained: {{dropdown:Consent:Yes — verbal,Yes — written,Guardian consent (minor)}}
Administered by: {{field:Name and credentials}}
Patient monitored for 15 minutes post-administration. No immediate adverse reaction observed.
Next dose due: {{field:Date or N/A}}
Structured code annotation — type ;TODO(fix auth) to expand with tag and description
REGEXDATEVARIABLES
// {{tag}}({{#GitUsername}}): {{desc}} — {{date:yyyy-MM-dd}}
Warm onboarding message for new customers with next steps
FIELDVARIABLES
Hi {{field:Customer Name}},
Welcome to {{#Company}}! We're thrilled to have you on board.
Your account has been set up and you're ready to go. Here are a few things to get you started:
1. Check out our Getting Started guide: {{field:Link to docs}}
2. Join our community: {{field:Community link}}
3. Reach out anytime — we're here to help.
If you have any questions, just reply to this email.
Cheers,
{{#Name}}
{{#Company}} Support