vue-best-practices
Skill0 starsChanged 25 days agoNo licenceView on GitHub
MUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.
31 other projects use a version of this, 8 of them edited; 5 of 8 edited versions we compared changed its rules; 1 new project in the last 4 weeks, against 0 the 4 before.
How people change it
5 of 8 edited versions changed its rules, and some changes recur.
Of the 8 edited versions we compared: 3 keep every rule, 5 made changes of their own.
Rules people drop
- Create a brief component map before implementation for any non-trivial feature.dropped by 5 of 5
- Keep entry/root and route-level view components as composition surfaces by default.dropped by 5 of 5
- Prefer a feature folder layout (
components/<feature>/...,composables/use<Feature>.ts) when adding more than one component.dropped by 5 of 5 - Keep SFC responsibilities focused; split large components.dropped by 5 of 5
- Prefer smaller components + composables over one “mega component”dropped by 5 of 5
- Keep entry/root and route view components thin: app shell/layout, provider wiring, and feature composition.dropped by 5 of 5
- Do not place full feature implementations in entry/root/view components when those features contain independent parts.dropped by 5 of 5
- Use provide/inject only for deep-tree dependencies or shared context.dropped by 5 of 5
Rules people add
- Decompose by responsibility: keep each implementation focused and the contracts between implementations explicit.added by 5 of 5
- Follow the project's layout and scale the design to the affected behavior. A local fix does not require a project-wide component map or new architectural layers.added by 5 of 5
- Keep SFC responsibilities cohesive; use the boundary criteria below when splitting.added by 5 of 5
- Treat file length, UI section count, and API size as review signals, not extraction thresholds. Keep a small cohesive production feature in one SFC when extra boundaries would not hide meaningful complexity.added by 5 of 5
- Use typed, scoped provide/inject for shared descendant dependencies when intermediate components only relay them; reassess component boundaries first. See the data-flow reference for scope and ownership.added by 5 of 5
- Keep DOM interaction and cleanup with its owning UI or composable. Preserve the explicit coordination other features need, such as committing a pending draft before saving.added by 5 of 5
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- ragna-ai/ragna-studioedited, first seen Nov 16, 2026
- Contentrain/studioword for word, first seen Nov 8, 2026
- onmax/nuxt-skillsedited, first seen Nov 1, 2026
- vuejs-ai/skillsedited, first seen Oct 25, 2026
- JunfengRan/dev-envword for word, first seen Oct 20, 2026
- joker-ye/skillsword for word, first seen Oct 13, 2026
Used with
Projects with it also use create-adaptable-composable, vue-debug-guides and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
hyf0Skillcreate-adaptable-composable
Create a library-grade Vue composable that accepts maybe-reactive inputs (MaybeRef / MaybeRefOrGetter) so callers can pass a plain value, ref, or getter. Normalize inputs with toValue()/toRef() inside reactive effects (watch/watchEffect) to keep behavior predictable and reactive. Use this skill when user asks for creating adaptable or reusable composables.
Also in 5 projects that use this
hyf0Skillvue-debug-guides
Vue 3 debugging and error handling for runtime errors, warnings, async failures, and SSR/hydration issues. Use when diagnosing or fixing Vue issues.
Also in 6 projects that use this
SentrySkillnitro
Build and deploy universal JavaScript servers with Nitro v3. Use when working with nitro.config.ts, defineNitroConfig, defineHandler, defineConfig, server.ts entry, filesystem routing, route rules, useStorage, defineCachedHandler, useDatabase, definePlugin, runtime hooks, Vercel/Cloudflare deployment, or migrating from Nitro v2/nitropack.
Also in 3 projects that use this
OpenAISkillusing-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Also in 3 projects that use this
OpenAISkillfinishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Also in 3 projects that use this
CloudflareSkillreceiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Also in 3 projects that use this
- +3 more from hyf0
- +3 more from openai
Other versions31 projects use a version of this.
Word for word · 11
- moeru-ai/airi★ 51k100% same
- Contentrain/studio★ 4100% same
- DingGao1124/skills★ 2100% same
- huangzida/skills★ 2100% same
- ElyzeSolutions/skills★ 1100% same
- hangineer/Hannah-Claude-Code-Toolkit★ 1100% same
- joker-ye/skills★ 1100% same
- JunfengRan/dev-env★ 1100% same
- wumyuan/skills★ 1100% same
- filipefalcaofs/repo-padrao★ 0100% same
1 more not listed
Edited · 8
- hyf0/vue-skills★ 3.2k54% same
- vuejs-ai/skills★ 3.1k54% same
- onmax/nuxt-skills★ 72454% same
- JetBrains/skills★ 38698% same
- konnga/skill-buddy★ 132100% same
- liangmiQwQ/skills★ 154% same
- ragna-ai/ragna-studio★ 154% same
- rockcookies/skills★ 1100% same
Wrote their own version · 12
- oyjt/uniapp-vue3-template★ 628same name
- jasonjgardner/blockbench-mcp-plugin★ 595same name
- uni-helper/skills★ 107same name
- skills-club/skills-live★ 13same name
- FrontToEnd/agent-skills★ 9same name
- belos-street/skill-kit★ 8same name
- HK-hub/AgentSkills★ 6same name
- GPTtang/skill-atlas★ 4same name
- heamlk/Python-Skill★ 1same name
- kirklin/skills★ 1same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- frontend-designSkill
- skill-creator-extraSkill
- slidev-build-slidedeckSkill
- slidevSkill
- viteSkill
- vueSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
32 rules. 12 are common, 7 are distinctive, and 13 are very specific to this project.
12
Common
Most of the 9 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

