Vue — 111 Operations for AI Agents
This page is the canonical reference an AI coding agent uses to refactor, query, and analyze Vue code through the act MCP server. 111 operations available: 37 refactor, 18 query, 42 analysis, 14 verification. Each operation is callable from Claude Code, Cursor, Codex, OpenCode, or any MCP-compatible agent host. Click any operation for a stable anchor link suitable for citation.
Worked Vue examples
act101 parses Vue single-file components with a dedicated grammar and edits template attributes and script declarations as syntax nodes. It can add a :key binding to a v-for loop that lacks one. It can consolidate an explicit :modelValue/@update:modelValue pair on a child component into a single v-model binding. And it can generate or extend a component's emits: array with a given event name, creating the option if the component does not already have one. Each example below is the verbatim output of the command shown, run against the file shown.
Add a key binding to a v-for loop
list.vue renders a list of items with v-for="item in items" but no :key, so Vue cannot track list items across re-renders.
$ act refactor-lang add_key_to_v_for --file list.vue --params '{"line":3,"column":1}'
Before
<template>
<ul>
<li v-for="item in items">{{ item.name }}</li>
</ul>
</template>
<script>
export default {
data() { return { items: [] } }
}
</script>
After
<template>
<ul>
<li v-for="item in items" :key="item.id">{{ item.name }}</li>
</ul>
</template>
<script>
export default {
data() { return { items: [] } }
}
</script>
The <li> element gains :key="item.id", giving Vue a stable identity for each rendered item.
Consolidate a modelValue pair into v-model
form-input.vue binds a child FormInput with the explicit :modelValue prop and a matching @update:modelValue listener that writes back to formData.email.
$ act refactor-lang convert_two_way_binding_to_v_model --file form-input.vue --params '{"prop_name":"modelValue","line":1,"column":1}'
Before
<template>
<FormInput :modelValue="formData.email" @update:modelValue="formData.email = $event" />
</template>
<script>
export default {
data() {
return { formData: { email: '' } }
}
}
</script>
After
<template>
<FormInput v-model="formData.email" />
</template>
<script>
export default {
data() {
return { formData: { email: '' } }
}
}
</script>
The two attributes collapse into a single v-model="formData.email" binding on FormInput.
Add an event to the emits declaration
form.vue's component calls this.$emit('submit') from handleSubmit, but its emits option is still an empty array.
$ act refactor-lang generate_emits_definition --file form.vue --params '{"event_name":"submit"}'
Before
<template>
<form @submit.prevent="handleSubmit">
<button type="submit">Submit</button>
</form>
</template>
<script>
export default {
emits: [],
methods: {
handleSubmit() {
this.$emit('submit')
}
}
}
</script>
After
<template>
<form @submit.prevent="handleSubmit">
<button type="submit">Submit</button>
</form>
</template>
<script>
export default {
emits: ['submit'],
methods: {
handleSubmit() {
this.$emit('submit')
}
}
}
</script>
emits: [] becomes emits: ['submit'], declaring the event the component already fires.
Query
18 query tools, the same on every supported language. Descriptions live in the shared reference: /docs/query-tools.
callers control_flow data_flow definition diagnostics effect_closure effect_summary fix_auto get_type graph import_organize interface mutations references repo_outline skeleton symbols symbols_batch
Refactor
| Operation | Description |
|---|---|
add-key-to-v-for |
Add :key binding to v-for loops for stability |
add-type-annotation-to-prop |
Add a TypeScript type annotation to an untyped prop |
add-v-model-binding |
Convert :prop/@update:prop pattern to v-model binding |
convert-arrow-to-method |
Convert an arrow function data property to a proper method |
convert-method-to-arrow |
Convert a method to an arrow function |
convert-prop-validator-to-type |
Convert a runtime prop validator to a TypeScript PropType annotation |
convert-string-interpolation |
Convert template string interpolation to expression binding |
convert-string-to-dynamic-binding |
Convert a hardcoded string to a dynamic :bind expression |
convert-to-composition-api |
Convert an Options API component to Composition API |
convert-two-way-binding-to-v-model |
Consolidate :prop and @update:prop bindings into v-model |
extract-component |
Extract selected template markup into a new component |
extract-computed-property |
Extract an expression from template into a computed property |
extract-event-handler |
Extract an inline event handler from template into a method |
extract-template-helper |
Extract a complex expression into a template helper function |
extract_function |
Extract a code selection into a new function — automatically infers parameters, return types, and inserts the call site. Use instead of manually cutting/pasting code. Works without LSP; LSP improves type inference. Params: file (string), new_name (string), start_line (u32), start_column (u32), end_line (u32), end_column (u32) [, preview (bool), receipt (bool)] |
extract_variable |
Extract an expression into a named variable — inserts the declaration and replaces the expression with the variable name. Works without LSP. Params: file (string), new_name (string), start_line (u32), start_column (u32), end_line (u32), end_column (u32) [, preview (bool)] |
generate-component-scaffold |
Generate a new Vue component with Options API structure |
generate-composition-api-component |
Generate a new Vue component with Composition API script setup |
generate-computed-property |
Generate a computed property with getter expression |
generate-emits-definition |
Generate or extend the emits declaration with event names |
generate-lifecycle-hook |
Generate a lifecycle hook in a Vue component |
generate-list-binding |
Generate a v-for loop with key and data structure |
generate-prop-definition |
Generate a prop definition with type annotation and default value |
generate-v-model-prop |
Generate a prop and emit for v-model two-way binding |
inline |
Inline a variable, function, or method — replace every usage with its definition body, then remove the original. The inverse of extract. Works without LSP (single-file); LSP enables cross-file inlining. Params: file (string), symbol (string) [, line (u32), preview (bool), receipt (bool)] |
inline-computed |
Inline a computed property into template |
insert_body |
Replace a function's implementation body with new code. AST-validated — rejects if the result has parse errors, so you can't accidentally break syntax. Use instead of manual text editing for function rewrites. Params: file (string), symbol (string), code (string) [, commit (bool)] |
move_symbol |
Move a function, class, or type to a different file and automatically update all imports across the codebase. Use instead of manually cut/paste + fixing imports. Works without LSP (single-file); LSP enables cross-file import updates. Params: file (string), symbol (string), destination (string) [, preview (bool), receipt (bool)] |
recipe_run |
Run a codemod recipe: declarative match → transform → optional verify across modeled grammars. Preview lists matches; apply writes with optional E7 receipts and all-or-nothing rollback. Returns a per-site report. |
remove-unused-method |
Remove an unused method from the component |
remove-unused-prop |
Remove an unused prop definition |
rename |
Rename a symbol and automatically update ALL references across the codebase. Safer and faster than find-and-replace — AST-aware, won't rename strings or comments. Works without LSP (single-file); LSP enables cross-file renames. Params: file (string), old_name (string), new_name (string) [, line (u32), column (u32), preview (bool), receipt (bool)] |
rename-computed-property |
Rename a computed property across definition and template references |
rename-data-property |
Rename a data property across definition, template, and methods |
rename-emitted-event |
Rename an emitted event across emit calls and parent listeners |
rename-method |
Rename a component method across definition and call sites |
rename-prop |
Rename a Vue component prop across definition and all usages |
Analysis
42 analysis tools, the same on every supported language. Descriptions live in the shared reference: /docs/analysis-tools.
analyze_api_diff analyze_chokepoints analyze_clones analyze_clusters analyze_cohesion analyze_conformance analyze_coupling analyze_cycle_risk analyze_cycles analyze_dead_code analyze_depth analyze_entry_points analyze_export analyze_extraction analyze_fan_balance analyze_features analyze_hotspots analyze_impact analyze_inconsistencies analyze_inheritance analyze_interface_bloat analyze_interfaces analyze_layers analyze_orphan_types analyze_patterns analyze_platform_deps analyze_readiness analyze_roles analyze_seams analyze_stability analyze_surface analyze_test_gaps analyze_thickness analyze_type_completeness churn_hotspots co_change_clusters coverage_overlay ownership_map profile_overlay simulate split_module trace_overlay
Verify
14 verify tools, the same on every supported language. Descriptions live in the shared reference: /docs/verification.
bisect_regression gate generate_test_harness scan secret_surface summarize_pr taint_flow unsafe_surface verify_behavioral_equivalence verify_contract_preserved verify_diff_semantics verify_port_parity verify_side_effects verify_test_impact