agentleFS
ku5icku5ic/claude-kit/skills/vue-patterns/SKILL.md

vue-patterns

Skill2 starsChanged 8 days agoMITView on GitHub

Vue 3 patterns for the Composition API, reactivity, single-file components, anti-patterns, and review checklist. Use whenever the project contains `.vue` files, `vue` in `package.json`, or a `vite.config.*` with the Vue plugin, OR the user asks about Vue, its reactivity primitives, `script setup`, or Pinia, even if Vue is not mentioned by name.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Default assumption: Vue 3 with the Composition API and <script setup> syntax.

    line 8

“Common” is measured: kept by at least 6 in 10 of the 4 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Vue patterns

Default assumption: Vue 3 with the Composition API and <script setup> syntax.

  • Current stable is Vue 3.5; deltas in 3.4+ (defineModel) and 3.5+ (Reactive Props Destructure, onWatcherCleanup) are called out where they matter.
  • Options API is acceptable for legacy code; flag as legacy when reviewed.
  • Adapt advice to the version in the project's package.json or lockfile.

Reference files

FileCovers
reference/reactivity.mdref vs reactive, toRefs, shallowRef, destructuring traps
reference/components.md<script setup>, defineProps/Emits/Slots/Model, defaults (3.5+ vs 3.4)
reference/watchers.mdwatch vs watchEffect, options, deep watchers, async cleanup
reference/state.mdprovide/inject, Pinia, composables
reference/anti-patterns.mdNine review-time anti-patterns with severity calls

Out of scope

  • Vue 2 projects. The Options API is the default and the reactivity model is fundamentally different. Flag the project's Vue major and stop; the patterns here will mislead.
  • React projects. Despite surface similarities (component tree, hooks-like primitives), the reactivity models differ.

References

Version notes

Checked: 2026-09-26 against https://github.com/vuejs/core/releases/latest (3.5.43, 2026-09-17), Context7 /vuejs/vue and https://vuejs.org/api/sfc-script-setup.html

  • 3.5 (2024-09-01): Reactive Props Destructure is the recommended default-value form over withDefaults (which still works); onWatcherCleanup.
  • 3.4: defineModel; watcher once: true.
  • 3.3: defineSlots; tuple-style defineEmits types.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.