vue

Enforce Vue 3 Composition API conventions in .vue files and composables.

19|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/xobotyi/cc-foundry --skill vue-xobotyi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vue
Source: https://github.com/xobotyi/cc-foundry/tree/main/plugins/frontend/skills/vue
Command: npx skills add https://github.com/xobotyi/cc-foundry --skill vue-xobotyi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces modern Vue 3 Composition API best practices, ensuring code is reactive, type-safe, and composable, leading to more maintainable and scalable Vue applications.

Core Features & Use Cases

  • Enforces Composition API & <script setup>: Guides developers to use the latest and most efficient Vue patterns.
  • Reactivity Best Practices: Promotes ref() over reactive() and correct usage of computed, watch, and nextTick.
  • Component Conventions: Standardizes naming, props, emits, slots, and styling for consistency.
  • Use Case: When writing new Vue components or refactoring existing ones, this Skill ensures adherence to Vue 3's recommended patterns, improving code quality and developer experience.

Quick Start

Use the vue skill to refactor the provided Vue component to use Composition API and <script setup>.

Frequently Asked Questions about vue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refactor a Vue component to use the Composition API and script setup?

Refactoring a Vue component to use the Composition API and script setup involves migrating options-based logic into reactive, type-safe composables. This Skill guides the conversion process to ensure reactivity best practices and standardized component conventions are applied correctly.

What is the best way to manage reactivity in Vue 3 composables?

Managing reactivity in Vue 3 composables is best achieved by preferring ref() over reactive() and correctly utilizing computed, watch, and nextTick. This approach ensures reactivity-aware code that remains type-safe and maintainable across your component architecture.

Does this approach work with TypeScript for Vue component architecture?

Yes, this approach works with TypeScript for Vue component architecture by enforcing type-safe code within your .vue files and composables. It ensures that props, emits, and component conventions adhere to Vue 3 Composition API best practices.

When should I prefer ref over reactive in Vue 3 Composition API?

You should prefer ref over reactive in Vue 3 Composition API to maintain safer reactivity tracking across composables. This Skill enforces this specific API style along with correct usage of computed and watch to prevent common reactivity pitfalls.

How do I standardize Vue 3 component conventions for props and emits?

Standardizing Vue 3 component conventions for props and emits is done by applying specific API styles during component writing and reviewing. This Skill enforces these guidelines to ensure your Vue components remain consistent, type-safe, and composable.