Read, search, and edit the user's xNet workspace (pages, databases, canvases) via vault files and the xnet CLI.
Write a markdown exploration document for a topic, feature idea, architecture question, or research area. Use when asked to "explore X", "research X", "write an exploration", "investigate X", or "do a deep dive on X". Produces a numbered doc in docs/explorations/ with mermaid diagrams, callouts, collapsible sections, status tables, recommendations, and checklists.
Autonomously implement what was just written — an /explore exploration, a plan, or a spec in the conversation. Use when the user says "implement it", "build it", "ship it", "do it", "make it so", "implement this exploration/plan", or "this looks good, go". Works on a new branch, checks off checklist items and commits as it goes, opens a PR, and merges to main.
Write a changeset for the current change. Use when you've edited a publishable packages/* library and need to record a semver bump + consumer-facing release note before the turn ends (the Stop hook enforces this). Reads the diff, picks the bump per affected package, and writes .changeset/*.md.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.