# Trigger & expansion

How Nibit detects when to expand a snippet.

Nibit expands a snippet when you type its **trigger** followed by a space or return.

## How it works

When you press space or return, Nibit checks whether what you just typed matches any snippet trigger. If it does, the trigger is replaced with the expansion and the space or return is consumed. If it doesn't match anything, the space or return is inserted normally.

## Choosing a trigger

There are no rules about what a trigger looks like. It just needs to be something you can type and press space or return after.

A common convention is to start triggers with a comma — `,addr`, `,sig`, `,meet` — because the comma is easy to reach and you'd never type `,addr` by accident. But this is purely optional. You can use plain words (`addr`), letter prefixes (`xaddr`), or anything else.

You can also set triggers to words you intentionally type — common misspellings work well, since you'd type `teh` then space anyway and the expansion fires naturally:

```
trigger: teh       →  expansion: the
trigger: recieve   →  expansion: receive
trigger: dont      →  expansion: don't
```

## Undoing an expansion

Press **backspace** once immediately after an expansion fires to undo it and restore the original trigger.

## App compatibility

Snippet expansion works in any app, with any keyboard — you don't need to switch to Nibit. The accessibility service handles detection in the background.