All skills
onmax avatar

/vue-debug-guides

@de09c7b official
by Maxonmax/nuxt-skills715 stars
38

Vue 3 debugging and error handling for runtime errors, warnings, async failures, and SSR/hydration issues. Use when diagnosing or fixing Vue issues.

Use this Skill: https://skilld.dev/gh/onmax/nuxt-skills/vue-debug-guides

This session only. Nothing lands on disk.

referenceslot-named-scoped-explicit-default.md

≈800 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Use Explicit Default Template When Mixing Named and Scoped Slots

Impact: HIGH - When a component uses both the default scoped slot and named slots, you must use an explicit <template #default> for the default slot. Using v-slot directly on the component while having nested named slot templates causes scope ambiguity and compilation errors.

Task Checklist

  • When using named slots alongside a default slot with props, always use explicit <template #default>
  • Never mix v-slot on the component element with <template #name> inside
  • Keep slot scope clear and unambiguous

Incorrect:

<script setup>
import MyComponent from './MyComponent.vue'
</script>

<template>
  <!-- BAD: v-slot on component + named template inside causes ambiguity -->
  <MyComponent v-slot="{ message }">
    <p>{{ message }}</p>

    <template #footer>
      <!-- Ambiguous: Is 'message' available here? Vue can't determine -->
      <p>Footer: {{ message }}</p>
    </template>
  </MyComponent>
</template>

This causes a compilation error because Vue cannot determine:

  1. Whether message from the default slot should be available in the footer slot
  2. Which scope applies to the non-template content

Correct:

<script setup>
import MyComponent from './MyComponent.vue'
</script>

<template>
  <!-- GOOD: Explicit template for each slot with clear scope -->
  <MyComponent>
    <template #default="{ message }">
      <p>{{ message }}</p>
    </template>

    <template #footer>
      <!-- Clear: footer slot has its own scope, no access to default's 'message' -->
      <p>Footer content here</p>
    </template>
  </MyComponent>
</template>

Correct - When Footer Also Has Props:

<script setup>
import MyComponent from './MyComponent.vue'
</script>

<template>
  <MyComponent>
    <template #default="{ message }">
      <p>{{ message }}</p>
    </template>

    <template #footer="{ year }">
      <!-- Each slot receives its own props -->
      <p>Copyright {{ year }}</p>
    </template>
  </MyComponent>
</template>

The Rule

When you have any named slots (<template #name>), always use explicit templates for all slots, including the default slot. This makes scope boundaries clear and prevents compilation errors.

Pattern Valid? Notes
v-slot on component only Yes Single default scoped slot
Named templates only Yes Multiple named slots
v-slot on component + named templates No Ambiguous scope
All explicit templates Yes Clear scope for each slot

Reference

Source: SKILL.md on GitHub

No alerts9d3 checks · Risk SAFE
  • Gen Agent Trust Hub9d

    The skill is a comprehensive collection of Vue 3 debugging guides and best practices. It contains no malicious code, exfiltration attempts, or prompt injections.

  • Socket9d

    No alerts

  • Snyk9d

    Risk: LOW · No issues

Signed by skilld at de09c7b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated last week

README badge

README badge for onmax/nuxt-skills/vue-debug-guides