pinia

Pinia Store Patterns

Use this skill when the task depends on shared state architecture in Vue or Nuxt. Keep stores explicit, cohesive, and easy to reason about under concurrent UI updates. Prefer composables for reusable local logic and Pinia only for state that truly deserves shared ownership.

Delivery Workflow

Use the checklist below and track progress:

Pinia progress:
- [ ] Step 1: Discover existing store boundaries and naming conventions
- [ ] Step 2: Define ownership of shared vs local state
- [ ] Step 3: Implement state, getters, and actions explicitly
- [ ] Step 4: Handle async flows, persistence, and invalidation safely
- [ ] Step 5: Verify store behavior and component integration

Store Design Rules

• Create a store only when state genuinely needs shared ownership or cross-route lifetime.
• Keep stores organized around a coherent business capability, not around random convenience helpers.
• Keep local component state out of Pinia unless sharing it materially improves the design.
• Prefer setup-style stores when that matches the repository's Composition API conventions.
• Expose intention-revealing state, getters, and actions.
• Avoid turning a store into a dumping ground for every side effect in a feature.

State, Getters, and Actions

• Store source-of-truth state, not duplicated derivations.
• Use getters for derived values that are meaningfully reused.
• Keep actions focused on one business interaction or one tightly related mutation flow.
• Make async actions explicit about loading, success, error, and invalidation behavior.
• Prefer clear action names over generic verbs.

Async and Persistence Boundaries

• Keep API calls and cache invalidation logic visible in the action that owns them.
• Make hydration, persistence, and reset behavior explicit.
• Avoid silent background mutations that make UI updates hard to reason about.
• Prevent duplicate concurrent requests when the feature should behave idempotently.
• Keep composables and stores in clear roles: composables for reusable feature logic, stores for shared long-lived state.