new-store
Skill0 starsChanged 8 months agoMITView on GitHub
Scaffold a new Pinia store. Use when the user asks to create a store, state management, or shared reactive state for a domain (e.g. users, posts, cart).
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- design-componentSkill
- new-componentSkill
- new-composableSkill
- new-gql-operationSkill
- new-migrationSkill
- new-quill-fieldSkill
- new-resolverSkill
- new-server-routeSkill
- new-settings-storeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Always use setup store syntax — never options syntax
- Very specific: line 14
If using GQL, import types from ~/types/gql — never redefine them
- Very specific: line 15
Place in stores/ directory
- Distinctive: line 73
Ask: what domain is this store for?
- Very specific: line 76
Always include isLoading, error, and reset()
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: New Store
Rules
- Always use setup store syntax — never options syntax
- Store ID matches filename in kebab-case:
defineStore('my-domain', ...) - State:
ref()for primitives and arrays,reactive()only for nested objects - Getters:
computed() - Actions:
async functionwith try/catch - If using GQL, import types from
~/types/gql— never redefine them - Place in
stores/directory
Template
// stores/[domain].ts
import { defineStore } from 'pinia'
// import type { MyType } from '~/types/gql'
export const use[Domain]Store = defineStore('[domain]', () => {
// ─── State ────────────────────────────────────────────────
const items = ref<MyType[]>([])
const selected = ref<MyType | null>(null)
const isLoading = ref(false)
const error = ref<string | null>(null)
// ─── Getters ──────────────────────────────────────────────
const count = computed(() => items.value.length)
const hasItems = computed(() => items.value.length > 0)
// ─── Actions ──────────────────────────────────────────────
async function fetchItems() {
isLoading.value = true
error.value = null
try {
// const { data } = await useAsyncQuery(...)
// items.value = data.value?.items ?? []
} catch (e) {
error.value = e instanceof Error ? e.message : 'Unknown error'
} finally {
isLoading.value = false
}
}
function reset() {
items.value = []
selected.value = null
error.value = null
}
return {
// State
items,
selected,
isLoading,
error,
// Getters
count,
hasItems,
// Actions
fetchItems,
reset,
}
})Steps
- Ask: what domain is this store for? What data does it hold?
- Determine if it needs GQL integration (import types from
~/types/gql) - Generate the store following the template above
- Always include
isLoading,error, andreset()
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

