Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This library of eight skills gives an agent a shared set of Vue 3 conventions: how to build adaptable composables, split components with clear responsibility boundaries, debug reactivity and hydration bugs, write tests with Vitest and Playwright, and manage state with Pinia and routing with Vue Router. It helps Vue developers, QA engineers, and project leads keep code predictable and testable without repeating the same guidance.
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
A Vue 3 project directory to substitute for <PROJECT_PATH>
Any required todo fields or behaviors
Use the vue-best-practices skill to create a small Vue 3 todo app in <PROJECT_PATH>. Before coding, provide a brief component map with each component's responsibility and its props/emits contract, then implement it with Composition API and <script setup lang="ts">. Replace <PROJECT_PATH> with the target project directory.
A Vue 3 or Nuxt 3 project directory to substitute for <PROJECT_PATH>
The desired hidden-state behavior and whether two-way updates are needed
Use the create-adaptable-composable skill to create a reusable composable for controlling whether an element is hidden in <PROJECT_PATH>. First state the proposed API and inputs/outputs, then implement maybe-reactive inputs using MaybeRef or MaybeRefOrGetter as appropriate and normalize them inside reactive effects. Replace <PROJECT_PATH> with a Vue 3 or Nuxt 3 project directory.
The component or composable path to substitute for <COMPONENT_PATH>
The relevant watcher code
Expected behavior and observed stale result
Use the vue-debug-guides skill to diagnose an async Vue watcher in <COMPONENT_PATH> whose older operation can overwrite a newer result. Explain the cause and propose the smallest focused correction. Replace <COMPONENT_PATH> with the affected component or composable path and include the relevant code and observed behavior.
Claude