evokeFind the first thing you want evoke to do.
Six examples, each on a page of its own. One runs today on a Mac. Five are patterns for an application, shown with the code that ran. Every page says what it needs before you run it or adapt it.
Examples
01 to 06Pick one, and follow it to the end.
Each page has the same shape: the request and the result, the operations behind it, one boundary where evoke asked first, and what you need. Then the run, or the pattern to adapt.
$ evoke "set the volume to 40 percent"
01Everyday Mac tasksThirteen reflexes for everyday things on a Mac:
lock, volume, a timer, a draft.Runs today on a Mac with the collection.
$ evoke "look up dana's address and email them"
02Look up a contact, prepare a draftTwo reflexes connect. What one
finds, the next one takes.A recorded session, and a pattern for your app.
$ evoke "scale checkout to 6 in staging"
03Operate services in team languageYour names for services fill a
command's arguments. A scale runs at once, and a rollback always asks.A pattern for your app. Needs kubectl and its access.
$ node queue.ts < inbox.txt
04Process an inbox of requestsRequests from a file. Clear ones run.
Unclear ones wait for a person.A pattern for your app, in eleven lines.
$ node runbook.ts "drain the primary"
05Continue an operational procedureEach step's program names the next.
Only the destructive one asks.A pattern for your app. The database bodies are stand-ins.
$ node checker.ts
06Prepare an action for approvalOne person types a payment. The decision
waits until another confirms it.A pattern for your app. Authorization stays yours.
None of these is yours?
A reflex is one file beside a program you already have. The developers page starts from an operation of your own, and the format page is the whole standard.