Organize snippets by website and workflow

Global snippets are useful for messages you use everywhere, but not every template belongs everywhere. A LinkedIn outreach message does not need to appear in Gmail. A GitHub issue response does not need to appear in a billing tool. A refund reply might belong in your help desk but not in a social media comment box.

Domain-specific snippets keep your library focused. Snipman can show snippets based on the website where you are writing, so each workflow has the templates that belong there.

Use global snippets for universal text

Global snippets are best for signatures, short acknowledgements, calendar links, common intros, and phrases you use across many sites. Keep this list small so it stays useful.

Use domain snippets for specialized work

Create domain-specific snippets for workflows tied to a site: Gmail follow-ups, LinkedIn recruiting messages, GitHub issue templates, Reddit moderation replies, Intercom support answers, Zendesk macros, HubSpot sales notes, and YouTube creator responses.

Name shortcuts by intent

Shortcuts should describe what the snippet does, not just where it is used. Use //follow_up, //bug_confirm, //refund_policy, or //intro_candidate. The domain already provides context, so the shortcut can stay focused on the action.

Review your busiest domains

If you write frequently on a site, that domain deserves a small set of well-maintained snippets. Start with the top five messages you repeat there. Add more only when the dropdown still feels easy to scan.

Use Vault as a starting point

Snipman Vault can provide curated domain-specific templates for supported sites. Pro users can copy Vault snippets into their own library and edit them, which is faster than starting from a blank page.

The goal is not to create the biggest snippet library. The goal is to create the most useful library for the page you are on.