Vue testing best practices by Anthony Fu — Vue 3.5 skill
Vue 3.5 Composition API guidance — script setup, reactivity, macros, built-in components and testing patterns from the Vue docs
- What
- Vue 3.5 Composition API guidance — script setup, reactivity, macros, built-in components and testing patterns from the Vue docs
- Cost
- Free
- Needs
- a Vue 3 project (the skill guides the agent's Vue code and testing patterns) — the skill is guidance the agent follows, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — Anthony Fu's official Vue skill (17,400+ installs, the most-installed new skill in our mega-sweep): a complete Vue 3.5 reference generated from the official Vue.js documentation. Covers the Composition API with `<script setup lang="ts">` (defineProps, defineEmits, defineModel, defineExpose, generics), the reactivity system (ref vs shallowRef, computed, watch/watchEffect, effectScope, composables), lifecycle hooks, built-in components (Transition, Teleport, Suspense, KeepAlive, v-memo), custom directives, and testing best practices. Ships with detailed reference files (script-setup-macros, core-new-apis, advanced-patterns) plus a quick-reference component template and key-imports cheat sheet. Strong opinions baked in: TypeScript over JavaScript, Composition API over Options API, shallowRef when deep reactivity isn't needed. Honest caveats: guidance for the agent, not a test runner — you still need Vitest/Vue Test Utils in your project; generated from vuejs/docs, so verify against the Vue version you target. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Vue 3 project (the skill guides the agent's Vue code and testing patterns) — the skill is guidance the agent follows, not software Install "Vue testing best practices by Anthony Fu — Vue 3.5 skill" for me. It gives my agent Anthony Fu's official Vue 3.5 reference, generated from the Vue.js docs: Composition API with <script setup lang="ts"> (defineProps, defineEmits, defineModel, defineExpose, generics), reactivity (ref vs shallowRef, computed, watch/watchEffect, effectScope, composables, lifecycle hooks), built-in components (Transition, Teleport, Suspense, KeepAlive, v-memo), custom directives, testing best practices, reference files (script-setup-macros, core-new-apis, advanced-patterns), plus a component template and key-imports cheat sheet. Strong opinions: TypeScript over JavaScript, Composition API over Options API. MIT licensed. Repository: https://github.com/antfu/skills/blob/main/skills/vue/SKILL.md 1. Fetch the SKILL.md file (and the references/ folder) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and references for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and the references/ folder into the agent's skills directory, in a folder named "vue-testing-best-practices". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. make sure Vitest/Vue Test Utils are set up in my project if I want the testing patterns applied; nothing else — it's a guide). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.