vue-data
Skill28 starsChanged 30 days agoMITView on GitHub
Server state and data fetching in Vue 3. Pinia Colada queries and mutations, caching, invalidation, optimistic updates, Vue Router data loaders, race conditions, abort, SSR payloads, and choosing between fetch layers. Use when fetching API data, caching server responses, handling loading and error states, or wiring mutations in a Vue app.
In this repository16 other files it gives its agents.
- antfuSkill
- build-toolingSkill
- designSkill
- find-skillsSkill
- nuxtSkill
- vitepressSkill
- vue-a11ySkill
- vue-ciSkill
- vue-clean-componentsSkill
- vue-debugSkill
- vue-formsSkill
- vue-performanceSkill
- vue-reviewSkill
- vueSkill
- vue-uiSkill
- vue-upgradeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Every query key includes every input the request depends on.
≈ “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
Vue Data Fetching
Versions checked on 2026-10-15: @pinia/colada 1.4.8 (stable, works with Pinia 4), Vue Router 5.4 data loaders (still experimental), @tanstack/vue-query 5. Nuxt apps start with useFetch and useAsyncData (nuxt skill).
Core rule
Server state is not client state. API data does not belong in hand-written Pinia stores with loading and error flags. A query layer owns caching, deduplication, invalidation and the request lifecycle. Pinia stores keep state the client owns: session, preferences, drafts.
Decision table
| Situation | Use |
| Vue SPA fetching REST or GraphQL | Pinia Colada useQuery and useMutation |
| Data must be ready before the route renders | Data loaders (defineColadaLoader, defineBasicLoader) from vue-router/experimental |
| Nuxt app | useFetch or useAsyncData (SSR payload, Nitro aware) |
| Project already uses TanStack Query | Keep TanStack Vue Query |
| One-off call with no cache impact, such as a form submit | $fetch or ofetch in the event handler |
| Static lookup fetched once at startup | A composable with a module-level cache (not on SSR) |
Checks before you finish
- Every query key includes every input the request depends on.
- Mutations invalidate or update the queries they affect.
- Loading, error and empty states each render something deliberate.
- Requests started by a watcher are cancelled or ignored when their inputs change.
- On SSR, nothing user-specific is cached at module level.
References
| Topic | Path |
| Pinia Colada: keys, invalidation, optimistic updates, SSR | pinia-colada |
| Data loaders with Vue Router 5 | data-loaders |
| Race conditions, AbortSignal, error handling, layering | patterns |
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.