Name: everhaven-state-pinia
Author: youmu10086

Imported from youmu10086/everhaven-fe-toc (.github/skills/everhaven-state-pinia/SKILL.md). Install upstream with npx skills add youmu10086/everhaven-fe-toc --skill everhaven-state-pinia. Copyright stays with the author.

Everhaven State (Pinia) Skill

Purpose

This skill standardizes how Pinia stores are defined and used in this project.

Where Things Live

Stores: src/stores/**

Store Rules

Use setup-style defineStore (composition API) like existing stores.
Export stores as useXStore with a clear, feature-based name.
Keep state serializable and minimal.
Use computed for derived values and functions for actions.
Avoid side effects at the top-level of store files; keep them inside actions.

Checklist

Store file placed under src/stores.
defineStore name is stable and unique.
State, getters (computed), and actions are clearly separated.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install everhaven-state-pinia and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "youmu10086-everhaven-fe-toc-everhaven-state-pinia", "kind": "skill", "name": "everhaven-state-pinia", "description": "Use when creating or updating Pinia stores. Covers store structure, naming, and state rules. Trigger keywords: Pinia, store, 状态管理, defineStore.", "publisher": "youmu10086", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use when creating or updating Pinia stores. Covers store structure, naming, and state rules. Trigger keywords: Pinia, store, 状态管理, defineStore." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/youmu10086/everhaven-fe-toc", "path": ".github/skills/everhaven-state-pinia/SKILL.md", "ref": "892dc3699f766fccb700a590d9e6af7054382df8", "url": "https://github.com/youmu10086/everhaven-fe-toc/blob/892dc3699f766fccb700a590d9e6af7054382df8/.github/skills/everhaven-state-pinia/SKILL.md", "key": "youmu10086/everhaven-fe-toc/.github/skills/everhaven-state-pinia/SKILL.md" } }, "instructions": "# Everhaven State (Pinia) Skill\n\n## Purpose\n\nThis skill standardizes how Pinia stores are defined and used in this project.\n\n## Where Things Live\n\n- Stores: src/stores/**\n\n## Store Rules\n\n1. Use setup-style defineStore (composition API) like existing stores.\n2. Export stores as useXStore with a clear, feature-based name.\n3. Keep state serializable and minimal.\n4. Use computed for derived values and functions for actions.\n5. Avoid side effects at the top-level of store files; keep them inside actions.\n\n## Checklist\n\n- Store file placed under src/stores.\n- defineStore name is stable and unique.\n", "cost": { "context_tokens": 165 } }

everhaven-state-pinia

About