Customize Vera

/customize shows the sources that shape Vera’s behavior. Use it to find a project instruction file, inspect a skill, or open a reusable definition in your editor.

Browse a source

1. Run /customize.
2. Choose Agents, Skills, Instructions, Memory, or Extensions.
3. Type to search names, descriptions, scopes, and paths.
4. Press Enter on a result to preview its saved contents.

Tab moves between Search and the list. Escape returns one level. The preview shows where a source comes from and whether it belongs to the project or home.

A Markdown file opens rendered. Press s to see its source.

Edit a source

Press Ctrl+O in a writable file’s preview to open it in your editor. Vera uses the editor set in VISUAL or EDITOR, and falls back to vi when neither is set.

Vera reloads the preview when the editor closes. A terminal editor such as vi or nano stays open until you quit, so this works on its own. A graphical editor such as VS Code hands the file to its window and returns at once, so Vera reloads before you have made any changes. Add its wait flag, as in EDITOR="code --wait", and it returns only when you close the file’s tab.

Bundled skills and extension-provided definitions are read-only here. Close and reopen Customize to refresh all catalogs after changes.

If an edit is invalid

An invalid definition appears as a catalog notice and is unavailable for use. Correct the file and reopen Customize. If the editor cannot start, the preview stays open and shows the error.

See what was loaded

Available sources are not necessarily loaded into the conversation. Loading labels describe the last measured request. Individual skill loading is not measured.

With the Context extension enabled, /context sources opens the sources from its usage report. See Inspect context usage.

Memory loading and writing are disabled. The Memory category can display existing files, but Vera does not recall them into new requests.