Sarctiann

Use when auditing agent models, reviewing provider offerings, optimizing model assignments by cost and speed, or updating agent descriptions with cost/speed indicators. Trigger keywords: "audit agents", "audit models", "update agent models", "review models", "optimize agents".

Use when navigating code symbols, finding definitions or references, renaming symbols, reading diagnostics, or any operation that benefits from the active LSP client in Neovim.

Use when the neovim MCP is available, or when the user mentions neovim, opening/closing/reading files in an editor, buffer navigation, text editing via editor, or any interaction with a text editor integrated session.

Use when doing project-wide search, collecting LSP references or diagnostics, navigating multi-file results, or any workflow that benefits from the Neovim quickfix or location list.

Use when navigating code symbols, finding definitions or references, renaming symbols, reading diagnostics, or any operation that benefits from the active LSP client in Neovim.

Use when the neovim MCP is available, or when the user mentions neovim, opening/closing/reading files in an editor, buffer navigation, text editing via editor, or any interaction with a text editor integrated session.

Use when doing project-wide search, collecting LSP references or diagnostics, navigating multi-file results, or any workflow that benefits from the Neovim quickfix or location list.

Use when synchronizing Neovim MCP permissions with agent definitions in opencode.jsonc. Trigger keywords: "sync agents", "sync neovim agents", "update agent definitions", "propagate agent changes", "sync agent configs".

Use when writing community update posts about mojo.nvim for Discord, Reddit, or other channels. Triggered by "write a post", "share an update", "draft a message".

Audit documentation files for accuracy, consistency, and freshness. Covers README, AGENTS, CONTRIBUTING, LICENSE, TODO, specs, plans, posts, and config files. Optionally suggests conceptual improvements.

Use when executing any task from docs/TODO.md. Covers the full lifecycle: identify → spec → plan → implement → docs → PR.

Use when updating docs/TODO.md after investigating Mojo language changes, VS Code releases, Neovim plugin API changes, completing a task, or auditing new tooling.

Use when navigating code symbols, finding definitions or references, renaming symbols, reading diagnostics, or any operation that benefits from the active LSP client in Neovim.

Use when the neovim MCP is available, or when the user mentions neovim, opening/closing/reading files in an editor, buffer navigation, text editing via editor, or any interaction with a text editor integrated session.

Use when doing project-wide search, collecting LSP references or diagnostics, navigating multi-file results, or any workflow that benefits from the Neovim quickfix or location list.