Blueprint gallery

A blueprint is real source that lands in your repo: automations, emails, segments and scenarios, yours to edit from the moment they arrive. Each one is a whole program, sized for a product rather than a demonstration. Its emails are sent under purposes, which cow init and cow add declare in your cow.json for you.

Start a new repo from one:

cow init --blueprint ecommerce

Or add one to a repo that already has a cow.json:

cow add blueprint mobile-game

Neither overwrites a file you already have unless you pass --force.

Programs

Blueprint	What it covers	Automations
ecommerce	The lifecycle of an online store	6
mobile-game	The lifecycle of a mobile game	6
saas-trial	A B2B free trial, end to end	6

The event names are placeholders. order.placed and the traits beside it are names a blueprint app sends; Cowliss defines none of them, and the only events it writes itself are the reserved system. ones. The three programs use the dot-namespaced style we suggest for a new app, because you are going to replace them either way. A copied blueprint does nothing until you rename its trigger, its waits and its traits to the names your own app already tracks. Each blueprint page lists the events it waits for, and cow events prints the same list for your own repo, as instructions a coding agent can follow; the traits a blueprint reads are in the files themselves.

The emails are Liquid HTML, one standalone file each with its look inlined, so changing the store name, the address line or the copy is an edit to emails/<key>.html. See Email templates.