Pinia gotchas: best practices and error patterns for Vue stores
Avoid common Pinia mistakes — getActivePinia errors, broken reactivity, state patterns
- What
- Avoid common Pinia mistakes — getActivePinia errors, broken reactivity, state patterns
- Cost
- Free
- Needs
- a Vue 3 project using Pinia
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a concise Pinia gotchas guide from the vuejs-ai project: symptom entries covering store setup (the "getActivePinia was called" startup error, setup stores missing state in DevTools or SSR), reactivity (store destructuring breaking UI updates, store methods losing context in template calls), and state patterns (ephemeral filters that reset on refresh → keep state in the URL, using Pinia conventions for large apps) — each pointing to a focused reference file. By @vuejs-ai, listed here with credit to its creator. Honest caveats: community-maintained by the vuejs-ai project, not the official Vue.js or Pinia team; a compact gotchas guide, not a full documentation reference — pair it with the comprehensive Pinia reference (antfu-skills-pinia) also listed here for depth. Discovered via skills.sh. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Pinia Gotchas is a free Muse skill that helps avoid common Pinia mistakes, including getActivePinia errors, broken reactivity and state patterns. Its concise guide offers symptom entries covering store setup, startup errors, setup stores missing state in DevTools or SSR, reactivity from store destructuring breaking updates, and methods losing context in template calls.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit c9d355fStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Vue 3 project using Pinia Install "Pinia gotchas: best practices and error patterns for Vue stores" for me. Give my agent the Pinia gotchas guide — store setup errors, reactivity pitfalls and state patterns — with the per-symptom reference files Repository: https://raw.githubusercontent.com/vuejs-ai/skills/c9d355ff23f654309dd02006be671859df0a134c/skills/vue-pinia-best-practices/SKILL.md Pinned version: install the code at commit c9d355ff23f654309dd02006be671859df0a134c exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and its reference files) for the vuejs-ai-skills-vue-pinia-best-practices skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "vuejs-ai-skills-vue-pinia-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. nothing — open it whenever a Pinia store misbehaves). 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- c9d355f · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.