vue-ecosystem-skills

Thirty-plus skills for Vue, Pinia, Vue Router, Reka UI and VueUse, tied to package versions and rebuilt with each release.

  • 184 ★ on the repository
  • Last commit
  • MIT
Skill

Minimal access

Why this level

  • Skills add instructions and reference files for the agent and run nothing or call out on their own.
All reasons and checks

skilld-dev/vue-ecosystem-skills

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/vue-ecosystem-skills

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Minimal accessThe tool runs nothing and makes no network calls.

  • Skills add instructions and reference files for the agent and run nothing or call out on their own.

This is third-party code. Review the repository files before installing.

What it does

vue-ecosystem-skills is a set of 35 skills, one per Vue ecosystem package: Vue, Pinia, Vue Router, Reka UI, VueUse, TanStack Vue Query, Vuetify, FormKit, vee-validate and more. Each skill is built from current documentation, issues, discussions and changelogs. Skills are rebuilt when a package ships a new version, so an agent writes code for Vue 3.5 and the latest major releases of Pinia and Vue Router. Outdated patterns from training data stay out of the context. Install the whole set or a single skill with `--skill`.

Who it is for. Frontend teams on Vue 3 using Pinia, Vue Router or Reka UI who keep fixing outdated APIs in agent output.

Good fit when

  • An agent suggests the Options API or old Pinia helpers while the project already runs Vue 3.5.
  • A project moves to Vue Router 5 or Pinia 3 and the agent needs migration notes at hand.
  • The stack includes Reka UI, shadcn-vue or PrimeVue and components must follow current documentation.
  • A team wants skills only for the packages actually listed in package.json.

Not a fit when

  • The project runs Vue 2: the skills target Vue 3.
  • You want opinionated team conventions: the skills restate documentation without personal preferences.
  • The work happens in Nuxt and needs Nuxt module skills: the README points to separate repositories for those.

Example request

Rewrite the cart store with Pinia in setup syntax and check the pinia skill so no outdated APIs slip in.

Limitations

The skilld tool builds the skills from published packages and documentation. There is no hand-written author layer, so source mistakes carry over. Some packages are pinned to betas, for example Vue 3.6.0-beta.6 and Vuetify 4.0.0-beta.2. In the Claude Code marketplace skills install one at a time, with a separate command for each. For agents to use them on their own, the README suggests adding a rule to `CLAUDE.md` or `.cursorrules` to check every installed skill for relevance before changing code.

How to disable. Delete the installed skill folders from the agent skills directory or run `/plugin uninstall` for Claude Code plugins. Remove the skill-check rule from `CLAUDE.md` by hand.

FAQ

How do I install the Vue skills in Claude Code?

Add the marketplace with `/plugin marketplace add skilld-dev/vue-ecosystem-skills`, then install skills one by one, for example `/plugin install pinia@vue-ecosystem-skills`.

Can I install a single package skill?

Yes. Pass the `--skill` flag with a name to `npx skilld add`, for example `--skill vue-router`. Without the flag the whole set is installed.

Where does the skill text come from?

From package documentation, GitHub issues, discussions and changelogs. A skill is rebuilt when its package ships a new version.

How is this different from skills that package authors ship inside the package?

Author-shipped skills live inside the package and are picked up by skills-npm. This repository provides ready skills for Vue libraries that do not ship their own yet.

Should I add a rule to CLAUDE.md?

The README advises adding a request to `CLAUDE.md` or `.cursorrules` to judge every installed skill for relevance before editing code and to invoke all relevant ones.

Discussion

No questions or reviews yet.

Skills

A set of skills for Vue 3 development: Composition API practices, router, Pinia, testing, JSX, Options API and debugging

SkillMinimal access3.3KRepository stars
Official

A skill that points the agent to ready VueUse composables for Vue 3 and Nuxt, with a usage and type reference for each function

SkillMinimal access406Repository stars
Editors’ pick

A skill set for the Vue, Vite and Nuxt stack: the author's conventions plus digests of official tool documentation

SkillMinimal access6KRepository stars
Official

The shadcn-vue skill reads your project settings and teaches an agent to add components, forms and themes of the Vue port of shadcn/ui by its rules

SkillExtended access10.8KRepository stars

A collection of 31 skills for Claude Code and other agents: interfaces, React, Postgres, code review, SEO and browser automation

SkillExtended access214Repository stars

Skills for uni-app development: framework docs, a uni-helper reference and related skills for Vue, Vite, Pinia and UnoCSS.

SkillMinimal access111Repository stars

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialRepository starsMain difference
vue-ecosystem-skills (this card)no184
vue-skillsno3,259hand-crafted Vue 3 best-practice skills; this set is generated per ecosystem package and tied to versions
VueUse Skillsyes406skills for VueUse only; here VueUse is one part of a set that also covers Pinia, Vue Router and UI libraries

README in short

The repository fills the gap for Vue libraries without skills of their own. Sets are grouped by topic: core, data and state, UI, forms, animation, VueUse and tooling. Related projects by other authors for Vue and Nuxt are listed alongside.

README badge

Original SKILL.md

---
name: pinia-skilld
description: "Use when writing, debugging, or refactoring code that imports \"pinia\", the Vue 3 store library. Covers pinia 4.x: option and setup stores, state, getters, actions, subscriptions, plugins, SSR hydration, testing, Options API map helpers, and v4 nostics diagnostics. Provides version-correct API usage and migration notes from v2 and v3."
license: MIT
---

# pinia@4.0.3

Source citations use package-relative paths from the prepared pinia 4.0.3 source: `package.json`, `README.md`, `dist/pinia.js` (runtime), `dist/pinia.d.ts` (types). Other citations are official documentation URLs.

## Requirements

- Vue `^3.5.11` peer [package.json:62]. Vue 2 is unsupported since v3.
- `@vue/devtools-api` `^8.1.5` is a required, non-optional peer [package.json:60-68]. Install it alongside pinia: `npm install pinia @vue/devtools-api` [README.md:108-111], v4.0.0 release notes.
- TypeScript `>=5.6.0` optional peer [package.json:69-71].
- ESM-only package: `"type": "module"`, single export `.` to `dist/pinia.js` [package.json:42,47-50]. v4 removed CJS resolution; a require() fallback breaks.
- `@pinia/nuxt` 1.x and `@pinia/testing` 2.x are the companion versions for pinia 4 (https://github.com/vuejs/pinia/releases).

## Install and setup

```ts
import { createApp } from 'vue'
import { createPinia } from 'pinia'
import App from './App.vue'

const pinia = createPinia()
const app = createApp(App)
app.use(pinia)
app.mount('#app')
```

From [README.md:119-130]. In dev on the client, `createPinia()` registers the devtools plugin itself [dist/pinia.js:832,847].

## Define a store

Two syntaxes. The id is a unique string, first argument in both [dist/pinia.d.ts:645,653].

```ts
import { defineStore } from 'pinia'

// Option store: state/getters/actions
export const useCounterStore = defineStore('counter', {
  state: () => ({ count: 0 }),
  getters: {
    doubleCount: (state) => state.count * 2,

Report a problem

Foxx AIvue-ecosystem-skills
Foxx AI

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.