xianxu

Use when 🤖{} or 🤖[] or 🤖~~ markers appear in markdown documents

use to learn from existing coding sessions, or record hints

Use when the user is requesting an artifact (capture, save, record, create) AND the substance to preserve is conversational context they've already produced. Skip when the user is stating facts, asking questions, or asking the agent to generate substance from scratch. Also trigger when editing markdown with known frontmatter type:

Use when editing issues in workshop/issues/.

Use to process interview feedback

apply a voice style

Generate a writing style guide

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Resolve brain-sync conflict files via AI-prose merge with prototype-aware structural reasoning. Invoke as /nous-resolve <brain-root>.

Use when invoking a nous-provided tool (cmd/<name> — e.g. cmd/gmail for Gmail access) OR when writing a new tool whose Go code calls OAuth-protected APIs. Tool users invoke `cmd/<name>` directly; tool authors need the embedded proxy protocol via `nous instructions`.

Provision the Google refresh token that grounds the OAuth shim's fake against real Google, and run the certification. Use when the conformance test skips ("no Google conformance refresh token"), on ~monthly re-cert, or when porting this to a new OAuth provider (nous#48 Microsoft).

Use proactively for any single-shot LLM call that doesn't need tool use or multi-turn conversation — classification, labelling, summarization, structured extraction, simple rewrites. Routes the work to a LOCAL Ollama model instead of a remote API call. Right answer when the task is bulk/cheap (1k+ items) or doesn't justify a remote-model invocation.

Search Gmail and read threads via Charon proxy. Use when the user asks to search email, check Gmail, find threads, or enrich data from email correspondence.

Use proactively — without being asked — in two situations: (1) when performing a document review, write findings as 🤖{} markers inline in the file rather than a separate report; (2) when a file contains 🤖 inline markers to process, apply them. Invoked as /fix <path-to-file> for processing markers.