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.
Best use case
pinia is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. 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.
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.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "pinia" skill to help with this workflow task. Context: 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.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/pinia/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How pinia Compares
| Feature / Agent | pinia | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this 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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## 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: - Introduction: https://pinia.vuejs.org/introduction.html - Core Concepts: https://pinia.vuejs.org/core-concepts/ - API Reference: https://pinia.vuejs.org/api/ ## 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 - **Official Documentation**: https://pinia.vuejs.org/ - **Introduction**: https://pinia.vuejs.org/introduction.html - **Core Concepts**: https://pinia.vuejs.org/core-concepts/ - **API Reference**: https://pinia.vuejs.org/api/ - **GitHub Repository**: https://github.com/vuejs/pinia ## 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, 插件, 服务端渲染, 类型支持
Related Skills
vant-vue3
Provides structured guidance for Vant of Vue 3.0. Use when the user needs Vant with Vue 3, asks about mobile UI components such as Button, Cell, Form, Dialog, Toast, Popup, ConfigProvider, theme customization, project setup, or wants to implement mobile-first interfaces with vant or van- components.
layui-vue3
Provides comprehensive guidance for Layui Vue component library including components, layer dialogs, and utilities. Use when the user asks about Layui Vue, needs to use Layui components in Vue 3, or implement UI components.
element-plus-vue3
Provides comprehensive guidance for Element Plus Vue 3 component library including installation, components, themes, internationalization, and API reference. Use when the user asks about Element Plus for Vue 3, needs to build Vue 3 applications with Element Plus, or customize component styles.
bootstrap-vue3
Provides comprehensive guidance for Bootstrap Vue 3 component library including Bootstrap components, grid system, utilities, and Vue 3 integration. Use when the user asks about Bootstrap Vue 3, needs to use Bootstrap components in Vue 3, or implement responsive layouts.
vuex-vue2
Provides comprehensive guidance for Vuex 2.x state management in Vue 2 applications including state, mutations, actions, getters, modules, and plugins. Use when the user asks about Vuex for Vue 2, needs to manage state in Vue 2 applications, or implement Vuex patterns.
vue3
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.
vue2
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.
vue-router
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.
vue-router-v4
Provides comprehensive guidance for Vue Router v4 including route configuration, navigation, nested routes, route guards, and Vue 3 integration. Use when the user asks about Vue Router v4, needs to set up routing for Vue 3 applications, implement navigation guards, or work with Vue Router v4 features.
vue-router-v3
Guidance for Vue Router v3 using the official Installation, Guide, and API docs. Use when users need routing setup, navigation patterns, or API details for Vue 2 projects.
vscode-project-init
Scaffold a new VS Code extension project using TypeScript via Yeoman generator (yo code), creating src/extension.ts entry point and package.json manifest. Use when the user wants to start a new VS Code extension project from scratch.
vscode-feature-webview
Add a Webview panel to a VS Code extension for displaying custom HTML content (forms, charts, complex layouts) using vscode.window.createWebviewPanel. Use when the user needs custom UI that cannot be achieved with standard VS Code UI elements, such as dashboards, settings forms, or rich previews.