Vue Component Debugger skill for Claude and Codex
Pins down why a Vue component renders wrong, stops updating, or skips a lifecycle hook, with reproduction steps, a checklist ordered by likelihood, and…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when a Vue component renders wrong, its data stops updating, a lifecycle hook never fires, or an event never reaches the parent. Do not use for performance profiling, debugging a Svelte or React component, or restructuring a component that works. Related topics: coding, vue.
What it will ask you for
- Component name (free text, e.g. "OrderTable")
- File path (free text, e.g. "src/components/OrderTable.vue")
- Vue version (choose one: Vue 3 script setup, Vue 3 Options API, Vue 2.7, Vue 2.6 or older)
- What goes wrong (longer free text)
- Error type (choose one: Render error, Data not updating, Lifecycle hook not firing, Event handling issue, Prop or emit mismatch)
- Component code (longer free text)
- Props or state snapshot (longer free text)
- Related libraries (choose any: Vuex, Pinia, Vue Router, Vuetify, Element Plus, None)
- Inspect the store (choose one: Yes, No)
How it works
- Map the reported symptom to the version-specific suspects (reactivity loss, hook names, emit casing, async timing) and list them.
- Check the pasted code and snapshot against each suspect and mark which ones the evidence supports or rules out.
- Write reproduction steps that start from a clean page and end at the observed behaviour.
- Order the checklist by likelihood for this symptom with what each check reveals, then give the fix as changed lines.
- State whether the fix also applies to the other Vue version and to the listed store or UI library.
What you get
A markdown document with Summary, Reproduction Steps, Debugging Checklist ordered by likelihood, and Suggested Fixes as code blocks, in that order.
What it watches out for
- Suggesting Vue 3 fixes such as reactive() for a Vue 2.6 codebase where Vue.set is the actual remedy.
- Blaming the store when the component destructures it and loses reactivity at the component boundary.
- Giving a checklist with no expected result per item, so the developer cannot tell when a check has cleared a suspect.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.