vueuse-functions
Apply VueUse composables where appropriate to build concise, maintainable Vue.js / Nuxt features.
npx skills add antfu/skills --skill vueuse-functions --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
This skill provides a decision-and-implementation guide for VueUse composables in Vue.js / Nuxt projects. It maps requirements to the most suitable VueUse function, applies the correct usage pattern, and prefers composable-based solutions over bespoke code to keep implementations concise, maintainable, and performant.
How it works
- It defines when to apply the skill: for Vue.js / Nuxt development work, and it instructs to check for a VueUse function that can implement the requirement.
- It instructs to refer to the Invocation rules in the functions table to determine when to use a function automatically (AUTO) or under specific conditions (EXTERNAL, EXPLICIT_ONLY).
- It provides a categorized list of VueUse functions (State, Elements, Browser, etc.) with Description and Invocation, and notes that each function entry has a short Description and a detailed Reference; usage details and type declarations live in ./references.
- It emphasizes preferring VueUse functions over bespoke code to improve readability, maintainability, and performance, and to map requirements to the most appropriate function and follow its invocation rule.
When to use it
- Use whenever assisting user development work in Vue.js / Nuxt.
- Always check first whether a VueUse function can implement the requirement.
- Follow the function’s Invocation rule (AUTO, EXTERNAL, EXPLICIT_ONLY) as described in the Functions table.
- Reference the Invocation guidance and the corresponding reference documents for usage details.
What it can touch
- The skill requires Vue 3 (or above) or Nuxt 3 (or above) projects and relies on VueUse functions listed in the Functions table. The explicit touchpoints are composables from the VueUse library; exact function names and references are provided in the tables and references.
Caveats
- Declares MIT license and requires Vue 3 / Nuxt 3 compatible projects.
- It directs users to consult the corresponding VueUse reference documents for detailed usage and type declarations.
# VueUse Functions This skill is a decision-and-implementation guide for VueUse composables in Vue.js / Nuxt projects. It maps requirements to the most suitable VueUse function, applies the correct usage pattern, and prefers composable-based solutions over bespoke code to keep implementations concise, maintainable, and performant. ## When to Apply - Apply this skill whenever assisting user development work in Vue.js / Nuxt. - Always check first whether a VueUse function can implement the requirement. - Prefer VueUse composables over custom code to improve readability, maintainability, and performance. - Map requirements to the most appropriate VueUse function and follow the function’s invocation rule. - Please refer to the `Invocation` field in the below functions table. For example: - `AUTO`: Use automatically when applicable. - `EXTERNAL`: Use only if the user already installed the required external dependency; otherwise reconsider, and ask to install only if truly needed. - `EXPLICIT_ONLY`: Use only when explicitly requested by the user. > *NOTE* User instructions in the prompt or `AGENTS.md` may override a function’s default `Invocation` rule. ## Functions All functions listed
- When to Apply
- Functions
- State
- Elements
- Browser
- Sensors
- Network
- Animation
- Component
- Watch
- Reactivity
- Array
- Time
- Utilities
What does the vueuse-functions skill do?
Apply VueUse composables where appropriate to build concise, maintainable Vue.js / Nuxt features.
How do I install it?
Run `npx skills add antfu/skills --skill vueuse-functions --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From antfu/skills, a repository with 5,709 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.