Quick Start Guide for SlashSnip

SlashSnip is currently in a pre-store public phase.

That means the website, pricing page, welcome flow, and legal pages exist, but the Chrome Web Store listing is still not the authoritative install source yet. Until that changes, the most honest install routes are:

• a local repo build for development;
• the connected /welcome page after install;
• the docs and pricing pages for product boundaries.

What is the first working shortcut?

The shipped starter snippet is:

//hello

Type //hello in a supported text field to test direct expansion.

If you want to browse snippets before inserting, type:

///

That opens the snippet menu.

Optional alias triggers

Slash triggers are the default, but SlashSnip also supports alias triggers when they are enabled in settings:

• @@shortcut for direct insertion
• @@@ for the menu

Use aliases only when a site makes slash-based typing inconvenient.

What to validate before relying on it

Do not mark a workflow as "supported" after only one happy-path test.

Check these four things separately:

1. Direct insert with //shortcut
2. Menu open/select with ///
3. Multiline snippets
4. Variables like {cursor} or {{clipboard}}

For the full surface-by-surface checklist, open the compatibility playbook.

If one editor needs different trigger behavior, use site-specific settings instead of changing the defaults for every website.