MCPInstall

pinia

Provides comprehensive guidance for Pinia state management including stores, state, getters, actions, plugins, and TypeScript support. Use when the user asks about Pinia, needs to manage application state, create stores, implement state persistence, or migrate from Vuex.

Installs
264
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/full-stack-skills/vue-skills --skill pinia
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads pinia automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

When to use this skill

Use this skill whenever the user wants to:

  • Set up Pinia state management in Vue 3 applications
  • Create stores with defineStore()
  • Work with state, getters, and actions
  • Use Pinia with Composition API
  • Use Pinia with Options API
  • Implement SSR (Server-Side Rendering) with Pinia
  • Create and use Pinia plugins
  • Access stores in components
  • Share state between components
  • Persist state with plugins
  • Test Pinia stores
  • Migrate from Vuex to Pinia

How to use this skill

This skill is organized to match the Pinia official documentation structure (https://pinia.vuejs.org/introduction.html, https://pinia.vuejs.org/core-concepts/, https://pinia.vuejs.org/api/). When working with Pinia:

  1. Identify the topic from the user's request:

    • Introduction/介绍 → examples/introduction/
    • Core Concepts/核心概念 → examples/core-concepts/
    • Cookbook/食谱 → examples/cookbook/
    • SSR/服务端渲染 → examples/ssr/
    • API Reference/API 参考 → api/
  2. Load the appropriate example file from the examples/ directory:

    Introduction (介绍) - examples/introduction/:

    • examples/introduction/introduction.md

    Core Concepts (核心概念) - examples/core-concepts/:

    • examples/core-concepts/actions.md
    • examples/core-concepts/defining-a-store.md
    • examples/core-concepts/getters.md
    • examples/core-concepts/index.md
    • examples/core-concepts/outside-component-usage.md
    • examples/core-concepts/plugins.md
    • examples/core-concepts/state.md

    Cookbook (食谱) - examples/cookbook/:

    • examples/cookbook/composables.md
    • examples/cookbook/composing-stores.md
    • examples/cookbook/hot-module-replacement.md
    • examples/cookbook/index.md
    • examples/cookbook/migration-v1-v2.md
    • examples/cookbook/migration-v2-v3.md
    • examples/cookbook/migration-vuex.md
    • examples/cookbook/options-api.md
    • examples/cookbook/testing.md
    • examples/cookbook/vscode-snippets.md

    SSR (服务端渲染) - examples/ssr/:

    • examples/ssr/index.md
    • examples/ssr/nuxt.md
  3. Reference API documentation in the api/ directory when needed:

    Pinia Core API - api/pinia/:

    • api/pinia/enumerations/MutationType.md
    • api/pinia/functions/acceptHMRUpdate.md
    • api/pinia/functions/createPinia.md
    • api/pinia/functions/defineStore.md
    • api/pinia/functions/disposePinia.md
    • api/pinia/functions/getActivePinia.md
    • api/pinia/functions/mapActions.md
    • api/pinia/functions/mapState.md
    • api/pinia/functions/mapStores.md
    • api/pinia/functions/mapWritableState.md
    • api/pinia/functions/setMapStoreSuffix.md
    • api/pinia/index.md
    • api/pinia/interfaces/Store.md
    • api/pinia/interfaces/StoreActions.md
    • api/pinia/interfaces/StoreDefinition.md
    • api/pinia/interfaces/StoreGetters.md
    • api/pinia/interfaces/StoreProperties.md
    • api/pinia/interfaces/StoreState.md

    @pinia/nuxt - api/@pinia/nuxt/:

    • api/@pinia/nuxt/index.md
    • api/@pinia/nuxt/interfaces/ModuleOptions.md
    • api/@pinia/nuxt/variables/default.md

    @pinia/testing - api/@pinia/testing/:

    • api/@pinia/testing/functions/createTestingPinia.md
    • api/@pinia/testing/index.md
    • api/@pinia/testing/interfaces/TestingOptions.md
    • api/@pinia/testing/interfaces/TestingPinia.md
  4. Follow the specific instructions in that example file for syntax, structure, and best practices

    Important Notes:

    • All examples follow Pinia best practices
    • Examples include both JavaScript and TypeScript versions where applicable
    • Each example file includes parameters, returns, common errors, best practices, and scenarios
    • Always check the example file for best practices and common patterns
  5. Reference the official documentation when needed:

Best Practices

  1. Use defineStore(): Always use defineStore() to create stores
  2. Store naming: Use descriptive store IDs
  3. State structure: Keep state flat and normalized when possible
  4. Getters: Use getters for computed values derived from state
  5. Actions: Use actions for async operations and mutations
  6. TypeScript: Use TypeScript for type safety
  7. Store composition: Split large stores into smaller, focused stores
  8. SSR: Use proper SSR setup for server-side rendering
  9. Plugins: Use plugins for cross-cutting concerns
  10. Testing: Write tests for stores and actions

Resources

Keywords

Pinia, state management, store, Vue 3, Composition API, Options API, defineStore, state, getters, actions, plugins, SSR, server-side rendering, TypeScript, Vuex migration, 状态管理, 存储, 组合式 API, 选项式 API, 插件, 服务端渲染, 类型支持

FAQ

What does the pinia skill do?

Provides comprehensive guidance for Pinia state management including stores, state, getters, actions, plugins, and TypeScript support. Use when the user asks about Pinia, needs to manage application state, create stores, implement state persistence, or migrate from Vuex.

How do I install pinia?

Run npx skills add https://github.com/full-stack-skills/vue-skills --skill pinia in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pinia/ (personal) or .claude/skills/pinia/ (project).

Which AI agents can use pinia?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is pinia safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains pinia?

It is published by full-stack-skills in full-stack-skills/vue-skills. It has 264 recorded installs.

More from full-stack-skills/vue-skills

View all →

vue3

full-stack-skills/vue-skills

Guidance for Vue 3 using the official guide and API reference. Use when the user needs Vue 3 concepts, patterns, or API details to build components, apps, and tooling.

Frontend & Design328 installs

vue-router-v4

full-stack-skills/vue-skills

Open the skill to read its SKILL.md instructions.

Frontend & Design238 installs

vue2

full-stack-skills/vue-skills

Provides comprehensive guidance for Vue 2.x development including Options API, components, directives, lifecycle hooks, computed properties, watchers, Vuex state management, and Vue Router. Use when the user asks about Vue 2, needs to create Vue 2 components, implement reactive data binding, handle component communication, or work with Vue 2 ecosystem tools.

Frontend & Design223 installs

vue-router

full-stack-skills/vue-skills

Provides comprehensive guidance for Vue Router including route configuration, navigation, dynamic routes, nested routes, route guards, programmatic navigation, and route meta. Use when the user asks about Vue Router, needs to set up routing, implement navigation guards, handle route parameters, or manage route transitions.

Frontend & Design216 installs

vuex-vue2

full-stack-skills/vue-skills

Open the skill to read its SKILL.md instructions.

Frontend & Design206 installs

vue-router-v3

full-stack-skills/vue-skills

Open the skill to read its SKILL.md instructions.

Frontend & Design204 installs

Popular frontend & design skills

View category →

setup-matt-pocock-skills

mattpocock/skills

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Frontend & Design1.1M installs

frontend-design

anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

OfficialFrontend & Design1M installs

hyperframes-animation

heygen-com/hyperframes

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

prototype

mattpocock/skills

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Frontend & Design999.2K installs

hyperframes-core

heygen-com/hyperframes

The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.

Frontend & Design930.5K installs

vercel-react-best-practices

vercel-labs/agent-skills

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

OfficialFrontend & Design843.1K installs