Prompts and resources

Besides abilities, the VX connection offers two things you use directly in your AI client.

Prompts

Prompts are ready-made procedures you start yourself, usually as a slash command (in Cursor and Claude Code) or from MCP: Browse Resources and Prompts in VS Code. They guide the assistant through a task that's easy to get wrong ad hoc.

Prompt	What it does
vx-explore-site	Reads the site's model and summarizes its structure
vx-check-readiness	Reports which field types are registered on the site, environment warnings and configuration conflicts
vx-plan-change	Turns a goal into an ordered plan, checks it without saving, and stops for your approval
vx-edit-fields	Edits a fieldset's fields without disturbing the ones you didn't mention
vx-audit-config	Checks for differences between your config files and the database, and recommends what to do
vx-audit-content	Looks for missing or inconsistent content, without changing anything
vx-migrate-values	Changes a value across many entries: samples first, tests one, then works in reviewable batches
vx-review-changes	Walks through the changes assistants have made and how to reverse each

Resources

Resources are documents the client can attach to a conversation, often by typing @, so the assistant has the facts without having to look them up.

Resource	Contains
vx://docs/…	Each article of this documentation, matching your installed version
vx://site/blueprint	Your whole data model
vx://model/post-type/<key>, vx://model/taxonomy/<key>, vx://model/user	The fields of one post type, taxonomy, or of users: each key, its value format, and whether it can be written or filtered
vx://guide	The operating manual VX gives every assistant when it connects

Attaching the field reference for a post type before asking for content changes ("fill in the tagline on every Book") helps the assistant use the right keys from the start.

You don't need to explain how to use VX to your assistant. When it connects, VX sends an operating manual (vx://guide) covering how to look before changing, how to check changes before saving, and how to keep track of undo information.

Technical details for LLMs

• Prompts and resources follow the ability exposure: each is published only while the ability that serves its data is exposed (e.g. vx://docs/… needs vx-framework/get-doc; vx-review-changes needs vx-framework/list-changes; vx://model/… needs the content reads). vx://guide is always published.
• Indexes: vx://docs (articles) and vx://model (field references with counts).
• The manual's critical rules are also returned as guidance by vx-framework/get-site-blueprint, and every write ability's description ends with the dry-run / no-parallel-writes / keep-the-undo constraint, for clients that skip the handshake instructions.