vue-ecosystem-skills

ALWAYS use when writing code importing "@formkit/core". Consult for debugging, best practices, or modifying formkit.

ALWAYS use when writing code importing "motion-v". Consult for debugging, best practices, or modifying motion-v, motion vue.

ALWAYS use when writing code importing "pinia". Consult for debugging, best practices, or modifying pinia.

ALWAYS use when writing code importing "@pinia/colada". Consult for debugging, best practices, or modifying pinia colada.

ALWAYS use when writing code importing "primevue". Consult for debugging, best practices, or modifying primevue.

ALWAYS use when writing code importing "quasar". Consult for debugging, best practices, or modifying quasar.

ALWAYS use when writing code importing "reka-ui". Consult for debugging, best practices, or modifying reka-ui.

ALWAYS use when writing code importing "shadcn-vue". Consult for debugging, best practices, or modifying shadcn-vue.

ALWAYS use when writing code importing "@tanstack/ai-vue". Consult for debugging, best practices, or modifying tanstack ai vue.

ALWAYS use when writing code importing "@tanstack/vue-form". Consult for debugging, best practices, or modifying tanstack vue form.

ALWAYS use when writing code importing "@tanstack/vue-query". Consult for debugging, best practices, or modifying tanstack vue query.

ALWAYS use when writing code importing "@tanstack/vue-router". Consult for debugging, best practices, or modifying tanstack vue router.

ALWAYS use when writing code importing "@tanstack/vue-store". Consult for debugging, best practices, or modifying tanstack vue store.

ALWAYS use when writing code importing "@tanstack/vue-table". Consult for debugging, best practices, or modifying tanstack vue table.

ALWAYS use when writing code importing "@tanstack/vue-virtual". Consult for debugging, best practices, or modifying tanstack vue virtual.

ALWAYS use when writing code importing "@tresjs/core". Consult for debugging, best practices, or modifying tresjs, tres.

ALWAYS use when editing or working with *.vue files or code importing "vue". Consult for debugging, best practices, or modifying vue.

ALWAYS use when writing code importing "vee-validate". Consult for debugging, best practices, or modifying vee-validate.

ALWAYS use when writing code importing "vitepress". Consult for debugging, best practices, or modifying vitepress.

ALWAYS use when writing code importing "vue-i18n". Consult for debugging, best practices, or modifying vue-i18n.

ALWAYS use when writing code importing "vue-router". Consult for debugging, best practices, or modifying vue-router.

ALWAYS use when writing code importing "@vue/test-utils". Consult for debugging, best practices, or modifying vue test utils.

ALWAYS use when writing code importing "vuetify". Consult for debugging, best practices, or modifying vuetify.

ALWAYS use when writing code importing "@vueuse/components". Consult for debugging, best practices, or modifying vueuse components.

ALWAYS use when writing code importing "@vueuse/core". Consult for debugging, best practices, or modifying vueuse core.

ALWAYS use when writing code importing "@vueuse/integrations". Consult for debugging, best practices, or modifying vueuse integrations.

ALWAYS use when writing code importing "@vueuse/math". Consult for debugging, best practices, or modifying vueuse math.

ALWAYS use when writing code importing "@vueuse/motion". Consult for debugging, best practices, or modifying vueuse motion.

ALWAYS use when writing code importing "vue-data-ui". Consult for debugging, best practices, or modifying vue-data-ui charts and data visualizations.

ALWAYS use when writing code importing "@unovis/vue" or "@unovis/ts". Consult for debugging, best practices, or modifying unovis charts and visualizations.

ALWAYS use when writing code importing "@floating-ui/vue". Consult for debugging, best practices, or modifying floating-ui positioning.

ALWAYS use when writing code importing "@vueuse/shared". Consult for debugging, best practices, or modifying vueuse shared.