Guide

Triggery is a declarative orchestration layer for the parts of an app that aren’t UI and aren’t state — the “when X and Y, do Z” logic that usually ends up scattered across useEffect, sagas, listener middleware and ad-hoc event buses.

This guide takes you from zero to fluent. If you’ve used useEffect for side effects before, you’ll find familiar shapes here; what’s new is the structure that makes them readable, testable and tool-aware.

Getting started Install the runtime, write your first trigger, fire your first event — in under five minutes.

Why Triggery The problem with useEffect-driven side effects, and how the event → conditions → actions split addresses it.

Essentials Read this section in order: trigger anatomy, events, conditions, actions, handlers, runtime.

Testing Trigger handlers are nearly pure functions. Mock conditions, mock actions, fire events.