pinia

Manage JARVIS system state with type-safe Pinia stores.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/ConnectiveTCS/Gradient_Generator --skill pinia-connectivetcs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pinia
Source: https://github.com/ConnectiveTCS/Gradient_Generator/tree/main/.agents/skills/pinia
Command: npx skills add https://github.com/ConnectiveTCS/Gradient_Generator --skill pinia-connectivetcs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Pinia-based state management for JARVIS consolidates and isolates application state across SSR boundaries, enabling reliable metrics, preferences, and HUD configurations.

Core Features & Use Cases

  • Centralized, type-safe stores using Pinia setup stores.
  • SSR-safe per-request state isolation and persistence controls.
  • Patterns for testing (TDD), performance optimization, and secure data handling across metrics, preferences, and command queues.

Quick Start

Create a per-request Pinia store under stores/ with type-safe actions and tests to validate behavior.

Frequently Asked Questions about pinia

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Vue state safely during server-side rendering?

SSR-safe state management with Pinia enforces per-request isolation, preventing cross-request state leakage by resetting store instances for each server request cycle.

What is the best way to structure type-safe Pinia stores?

Type-safe Pinia stores use the setup store syntax to define typed state, getters, and actions, ensuring compile-time validation for metrics, preferences, and HUD configurations.

How do I test Pinia stores using a TDD workflow?

TDD-driven Pinia workflows involve writing behavior-validating tests before implementation, creating stores under the stores/ directory with type-safe actions and controlled test environments.

Does Pinia support secure data persistence for sensitive user preferences?

Pinia persistence controls allow safe storage only for non-sensitive data, ensuring sensitive metrics and command queues are excluded from client-side persistence mechanisms.

Why does my Pinia store state leak between server-side rendered requests?

State leakage occurs without per-request isolation; Pinia requires SSR-safe patterns to instantiate isolated store instances per request, preventing shared mutable state across boundaries.