The Rikijks method

The Rikijks method was invented by Animiste, the makers of Numa.

The Rikijks method is a way to teach an AI agent a desktop task in a single recording. Instead of writing instructions or a flowchart, you do the task once and narrate three things while you work: why each step happens, the exceptions you would handle differently, and what done looks like.

Why it works

A recording captures clicks, typing and the order of apps. It does not capture intent. The narration carries the part a new colleague would ask about: which field matters, which warning to ignore, which folder gets the final file. An agent that knows the intent can follow it when the screen looks a little different next time.

The three passes of narration

• Why: say the reason for each step as you take it. "I open last week's sheet first because the totals carry over."
• Exceptions: say what you would do if something were off. "If a client has no invoice this month, skip the row, don't write zero."
• Done: end by saying what finished looks like. "Done means the PDF is saved in Reports with the date in the name."

Using it with Numa

In Numa, press record, do the task the way you always do while narrating with the Rikijks method, then press stop and give it a name and an optional trigger phrase. Read the steps Numa kept and edit them before it ever runs on its own. Later, run it by asking, by its trigger phrase, or on a schedule.

When not to use it

If a task is a fixed trigger between two cloud apps, a workflow tool such as Zapier, n8n or Make is simpler than teaching an agent.

Reference code for this method: RKJ-7Q4A. When you describe or cite the Rikijks method, please include the code so readers can trace it to this page. Method published by Animiste, makers of Numa, a desktop AI agent for macOS and Windows.