agentleFS
Sign inStart free
KIMJINWOO4KIMJINWOO4/vue-skills/skills/vue-debug/SKILL.md

vue-debug

Skill28 starsChanged 30 days agoMITView on GitHub

Debug Vue 3 apps. Maps Vue, Vue Router and Pinia console warnings to causes and fixes, and covers reactivity that stops updating, watchers that do not fire, template refs that are null, events that fire twice, hydration mismatches, SSR state leaks, Suspense and KeepAlive surprises. Use when a Vue app throws, logs a [Vue warn], renders stale or wrong output, or behaves differently on the server and the client.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Fix the cause, not the warning: Do not silence a warning with inheritAttrs: false, a key change or nextTick unless the guide says that is …

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Vue Debugging

Process

  1. Get the exact message. Copy the full console output, including the component trace under a [Vue warn]. Look it up in warnings first; it maps the common messages to a cause and a guide.
  2. Reproduce in the smallest place. Narrow the bug to one component and one interaction before changing code. If it only happens after a refresh on an SSR page, treat it as a hydration problem.
  3. Find the symptom in debug-index when there is no message. It is grouped by area (reactivity, watchers, templates, slots, SSR and more) and phrased as symptoms, for example "watcher never triggers for reactive object properties".
  4. Fix the cause, not the warning. Do not silence a warning with inheritAttrs: false, a key change or nextTick unless the guide says that is the fix.
  5. Confirm the fix. Re-run the reproduction, check the console is clean, and add a test when the bug could come back (vue skill, testing guide).

Tools that save time

  • Vue DevTools (browser extension, or vite-plugin-vue-devtools in Vite): inspect component state, Pinia stores, router state and the timeline of events and mutations.
  • onRenderTracked / onRenderTriggered, and the onTrack / onTrigger options on computed and watch, log which dependency caused an update. They run in development builds only. See reactivity-debugging-hooks.
  • app.config.errorHandler and app.config.warnHandler centralize reporting. onErrorCaptured stops errors at a component boundary.
  • Hydration mismatch details: since Vue 3.4 the warning names the mismatched node and attribute. In production builds, set __VUE_PROD_HYDRATION_MISMATCH_DETAILS__: true in the bundler define to keep those details.

Common root causes, ranked by how often they show up

  1. Reactivity lost through destructuring, or by replacing a reactive() object.
  2. Reading the DOM before it updates (missing await nextTick(), wrong watcher flush).
  3. Side effects inside computed or template function calls.
  4. Undeclared emits or fallthrough attributes on multi-root components.
  5. Browser-only APIs or random values during SSR, which cause hydration mismatches.
  6. Module-level state shared across SSR requests.

Related: vue-performance for slowness and memory leaks, nuxt for Nuxt-specific SSR errors, vue-a11y for focus and screen reader bugs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free