Skip to content
SkillModel-led220 tokens in use

vue-pinia-best-practices

Pinia guidance for agents: store setup errors, reactivity loss when destructuring a store, and where state should live.

3,364 stars on the repository MIT Licensevuejs-ai/skills · skills/vue-pinia-best-practices
npx skills add vuejs-ai/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing vue-pinia-best-practices costs

24tokens idle
220tokens in use
9,148tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Fair
  • Frontmatter11/15
  • Structure8/25
  • Examples3/15
  • Output5/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Fair
  • Development activity68
  • Maintenance40
  • Community52
  • Maturity32
  • Momentum40

This skill collects Pinia gotchas and state management patterns for Vue 3. Its SKILL.md has three groups, Store Setup, Reactivity and State Patterns, each linking to a short reference.

The entries cover the getActivePinia was called error at startup, setup stores that leave state out of DevTools or SSR, store destructuring that stops updating the UI, store methods that lose context in templates, filters that belong in the URL, and why larger apps should use Pinia.

What You Get

  • A guide to the no active Pinia error at startup
  • A rule to return all state from setup stores so DevTools and SSR see it
  • Guides on destructuring stores and calling store methods from templates
  • Two state pattern notes: URL state for ephemeral filters and Pinia for large apps

Common Use Cases

  • Fixing a Pinia error that appears when the app starts
  • Restoring reactivity after destructuring a store
  • Deciding whether a filter belongs in a store or in the URL

What Makes It Unique

It is limited to Pinia and its few most common mistakes. It sits beside the main Vue skill and the testing skill, which has its own note on Pinia setup in tests.

Under The Hood

The agent loads a short Markdown index and reads the reference that matches the issue. There are no scripts. The skill does not tell the agent to fetch web pages, call APIs or run commands; the agent edits your store and component files when you ask for a fix.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers