Text Expander

---
name: text-expander
description: Build a text expansion system: snippets for repeated text, fill-ins, date math, and cross-app consistency. Use when you type the same things repeatedly and want them instant and error-free.
category: productivity
---

# Text Expander

## Overview

Text expansion turns abbreviations into full text as you type: `;addr` becomes your address, `!mtg` becomes a meeting template.

Anyone who types repeated text — support replies, addresses, code boilerplate, meeting notes — saves hours monthly.

The system: a snippet library with consistent prefixes, fill-in fields for variables, and date math for dynamic content.

Works across nearly all apps, since it operates at the keyboard level.

## When to use

- Eliminating repeated typing (addresses, intros, replies, signatures)
- Standardizing team responses in support, sales, or recruiting
- Speeding up code boilerplate and documentation
- Creating meeting-note and email templates that expand anywhere
- Reducing typos in frequently typed complex text (URLs, commands)

## Core concepts

- **Trigger prefixes.**
  Distinctive prefixes (`;`, `!`, `,,`) prevent accidental expansion inside normal words. Pick one convention and stick to it.
- **Plain snippets.**
  Static text: addresses, signatures, common replies, links. The 80% of value with 20% of effort.
- **Fill-in fields.**
  Variables with tab stops: name, date, ticket number. One snippet adapts to many situations.
- **Date and time math.**
  Dynamic dates: today's date, next Friday, timestamps in your format. Meeting notes and filenames love these.
- **Formatted snippets.**
  Rich text or HTML where needed: formatted emails, markdown templates, code blocks with placeholders.
- **Snippet organization.**
  Groups by domain (personal, work, code, support). Searchable library; naming convention so you can find them.
- **Cross-device sync.**
  Snippets on every machine and ideally mobile. A snippet you can't reach is a snippet you stop using.
- **Team sharing.**
  Shared snippet groups for support/sales: consistent voice, faster onboarding, one place to update messaging.

## Practical workflow

1. **Inventory your repeats.**
   One week: note everything you type more than twice. That's your snippet backlog, prioritized by frequency.
2. **Set the prefix convention.**
   Choose `;` or `!` style prefixes; avoid prefixes that collide with real words you type.
3. **Create the top 20.**
   Addresses, intros, common replies, meeting template, date stamps. Twenty snippets cover most people's repetition.
4. **Add fill-ins.**
   Upgrade the top 5 with tab-stop fields for names, dates, ticket numbers. One flexible snippet beats five rigid ones.
5. **Build date snippets.**
   Today, tomorrow, next-week dates in your formats. Filenames, notes, and emails consume these constantly.
6. **Organize into groups.**
   Personal, work, code, support. Archive stale snippets quarterly — outdated snippets are worse than none.
7. **Sync everywhere.**
   Enable sync across your machines; set up mobile keyboard expansion if your tool supports it.
8. **Share team snippets.**
   For teams: one shared group for customer-facing text, with an owner who keeps it current.

## Common pitfalls

- **Prefix collisions.**
  Abbreviations that expand mid-word. Test every snippet in real typing; distinctive prefixes prevent disasters.
- **Stale snippets.**
  Old address, old pricing, old boilerplate expanding confidently. Review the library quarterly.
- **Over-snippeting.**
  A snippet for everything creates a memory burden. If you can't remember the trigger, search the library — or it's not worth having.
- **No fill-ins.**
  Twenty near-identical snippets differing by one word. Fill-in fields collapse them into one.
- **App conflicts.**
  Some secure fields (passwords, banking) block expansion — by design. Don't fight it; it's protecting you.
- **Single-device library.**
  Snippets only on one machine. You'll type the long way on the other and the habit dies. Sync everything.
- **Forgetting the library.**
  Building 50 snippets then typing manually from habit. Keep a cheat sheet visible for the first month.
- **Sharing without ownership.**
  Team snippets nobody maintains rot. One owner per shared group, review cadence, changelog.