Choose reliable snippet triggers

A good trigger is faster than retyping but unusual enough that it will not expand during normal writing.

A practical trigger pattern

Use a consistent prefix plus a short mnemonic. Prefixes such as a colon or semicolon separate deliberate expansion commands from ordinary words.

Trigger guidelines

• Keep it memorable. A trigger only saves time when you can recall it.
• Avoid normal words. Do not use an abbreviation that appears frequently in your writing.
• Use one naming system. For example, reserve :git for developer commands and :mail for email content.
• Prefer meaning over minimum length. A slightly longer trigger can prevent mistakes.
• Test in your real apps. Verify the trigger in email, chat, editors, and terminals where appropriate.

When you forget a trigger

You do not need to memorize the entire library. Open global search to find snippets by name, description, or tag, then navigate from the keyboard.

Troubleshoot expansion

If a known trigger does not expand, first test it in TextEdit. Confirm that SnippetCraft is running, the trigger was saved, and Accessibility permission remains enabled. If the trigger works in TextEdit but not in one application, the issue is likely limited to that app or text field.