Reference / Voice prompt cookbook · 6 min

Time to ship · about 6 minutes

Voice prompt cookbook.

Eight prompts that work, grouped by use case. Each one is a real sentence you can say out loud — no keywords, no syntax, no special phrasing required.

Aura does not require magic words. She routes on intent, not on literal phrases. These prompts are starting points — the kind of sentence that lands cleanly and produces a predictable worker state or dispatch. Adapt them to your project.

01.

Debugging.

Name the symptom and the location. Aura turns that into an approved worker task so Claude Code can inspect the test and draft a fix. State after: dispatched, then awaiting.

“hey aura, look at the failing test in auth/token and try a fix.”
02.

Refactoring.

Name the file and the problem. Aura should first discuss the split or restructure; dispatch happens only if you approve edit-capable work. Worker: Claude Code. State after: live context answer, then optional dispatch.

“the orchestrator file is too long, suggest a split.”
03.

Docs.

Scope to a diff, a release, or a file. Aura uses available live context or the feeder lane to produce a spoken summary. Worker: Claude Code. State after: live context answer, no dispatch unless you ask her to write it out.

“summarize what changed since the last release.”
04.

Exploration.

Ask for a tour of an unfamiliar crate, module, or service. She pulls from the ambient context digest and answers without dispatching a worker. State after: live context answer.

“give me a one-paragraph tour of the audio crate.”
05.

Review.

Ask her to skim the current diff and flag anything that looks off. Aura uses the context feeder/source lane where possible and gives a spoken verdict. State after: live context answer.

“skim the diff and tell me if anything looks off.”
06.

Planning.

Use before starting a large change. She reasons about the scope and surfaces the risks worth thinking about first. State after: live context answer, no dispatch.

“i'm about to start the auth refactor — what should i think about first.”
07.

Hotfix.

Name the symptom, not the file. Aura dispatches the worker with the symptom and callback expectation; the worker investigates and returns the patch result for review. Worker: Claude Code. State after: dispatched, then callback with patch.

“find the regression that broke startup and stage a fix.”
08.

Hand-off.

Delegate a long-running task to Codex with a callback condition. Aura dispatches the worker task with that callback preference and goes to awaiting. Worker: Codex. State after: dispatched, callback when a result is observed.

“spawn codex on the linux build, callback when green.”