vue
PopularUse when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code - provides Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring guidance
Use when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code - provides Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring guidance
Vue 3 Development
Reference for Vue 3 Composition API patterns, component architecture, and testing practices.
Current stable: Vue 3.5+ with enhanced reactivity performance (-56% memory, 10x faster array tracking), new SSR features, and improved developer experience.
Overview
Progressive reference system for Vue 3 projects. Load only files relevant to current task to minimize context usage (~250 tokens base, 500-1500 per sub-file).
When to Use
Use this skill when:
- Writing
.vuecomponents - Creating composables (
use*functions) - Building client-side utilities
- Testing Vue components/composables
Use nuxt skill instead for:
- Server routes, API endpoints
- File-based routing, middleware
- Nuxt-specific patterns
For styled UI components: use nuxt-ui skill
For headless accessible components: use reka-ui skill
For VueUse composables: use vueuse skill
Quick Reference
| Working on... | Load file |
|---|---|
.vue in components/ |
references/components.md |
File in composables/ |
references/composables.md |
File in utils/ |
references/utils-client.md |
.spec.ts or .test.ts |
references/testing.md |
| TypeScript patterns | references/typescript.md |
| Vue Router typing | references/router.md |
| Reactivity (ref, watch) | references/reactivity.md |
| Custom directives | references/directives.md |
| Provide/inject | references/provide-inject.md |
Loading Files
Load one file at a time based on file context:
- Component work → references/components.md
- Composable work → references/composables.md
- Utils work → references/utils-client.md
- Testing → references/testing.md
- TypeScript → references/typescript.md
- Vue Router → references/router.md
- Reactivity → references/reactivity.md
- Custom directives → references/directives.md
- Provide/Inject → references/provide-inject.md
DO NOT load all files at once - wastes context on irrelevant patterns.
Available Guidance
references/components.md - Props with reactive destructuring, emits patterns, defineModel for v-model, slots shorthand
references/composables.md - Composition API structure, VueUse integration, lifecycle hooks, async patterns, reactivity gotchas
references/utils-client.md - Pure functions, formatters, validators, transformers, when NOT to use utils
references/testing.md - Vitest + @vue/test-utils, component testing, composable testing, router mocking
references/typescript.md - InjectionKey for provide/inject, vue-tsc strict templates, tsconfig settings, generic components
references/router.md - Route meta types, typed params with unplugin-vue-router, scroll behavior, navigation guards
references/reactivity.md - ref, reactive, computed, watch, watchEffect, reactivity fundamentals
references/directives.md - Custom directive hooks, v-focus, v-click-outside, v-tooltip patterns
references/provide-inject.md - InjectionKey typing, app-level provide, readonly patterns
Examples
Working examples in resources/examples/:
component-example.vue- Full component with all patternscomposable-example.ts- Reusable composition function
You Might Also Like
Related Skills
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
vercel
component-refactoring
Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.
langgenius
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
anthropicsfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
anthropics
react-modernization
Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to latest React versions.
wshobsontailwind-design-system
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
wshobson