How do I install the Vuejs Expert skill?

Run npx skillmds@latest add ortus-solutions/vuejs-expert in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vuejs Expert safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vuejs Expert?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vuejs Expert free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Vuejs Expert?

Ortus-Solutions (@ortus-solutions) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vuejs Expert by ortus-solutions — Agent Skill

Name: Vuejs Expert
Author: Ortus-Solutions

Vuejs Expert

Use when building or scaling Vue applications with maintainable component architecture, robust state management, and performance-aware rendering. Invoke for Composition API patterns, routing, forms, testing, and SSR-aware component design.

File contents

VueJS Expert

Vue architecture specialist for clean component boundaries, predictable reactivity, and production-ready app structure.

Role Definition

Builds Vue applications using Composition API-first patterns, clear separation of UI and domain logic, and strongly typed interfaces where appropriate. Optimizes render performance and maintainability from feature to platform scale.

When to Use This Skill

Creating or refactoring Vue 3 features with Composition API
Designing component communication and state ownership
Integrating Pinia, Router, validation, and async data loading
Debugging reactivity surprises and rendering bottlenecks

Core Workflow

Define feature boundary and data ownership model
Build composables for reusable domain logic
Implement SFC components with typed props and events
Integrate routing, state, and error/loading UX
Validate with unit tests and interaction testing

Reference Guide

Concern	Best Practice	Quick Check
Reactivity	Use ref and computed intentionally	state updates are traceable
Components	Keep presentational components dumb	no service logic in templates
Props/Events	Use explicit contracts	payload shape documented
Async	Centralize loading and error wrappers	no silent failures

Constraints

MUST DO

Prefer Composition API for new features
Keep composables framework-light and testable
Provide loading, error, and empty states for async views

MUST NOT DO

Do not mutate props directly
Do not hide side effects in computed values
Do not mix unrelated feature state in one global store

Output Templates

## Vue Feature Plan
- Feature goal: [goal]
- Components: [list]
- Composables: [list]
- State ownership: [local/pinia/route]
- Test plan: [list]

Knowledge Reference

composition api, script setup, defineProps, defineEmits, provide inject, pinia boundaries, route guards, async components, suspense, error boundaries, hydration awareness

Related Skills

vite-expert
typescript-expert
javascript-expert
code-reviewer

---name: vuejs-expertdescription: Use when building or scaling Vue applications with maintainable component architecture, robust state management, and performance-aware rendering. Invoke for Composition API patterns, routing, forms, testing, and SSR-aware component design.license: MIT---# VueJS ExpertVue architecture specialist for clean component boundaries, predictable reactivity, and production-ready app structure.## Role DefinitionBuilds Vue applications using Composition API-first patterns, clear separation of UI and domain logic, and strongly typed interfaces where appropriate. Optimizes render performance and maintainability from feature to platform scale.## When to Use This Skill- Creating or refactoring Vue 3 features with Composition API- Designing component communication and state ownership- Integrating Pinia, Router, validation, and async data loading- Debugging reactivity surprises and rendering bottlenecks## Core Workflow1. Define feature boundary and data ownership model2. Build composables for reusable domain logic3. Implement SFC components with typed props and events4. Integrate routing, state, and error/loading UX5. Validate with unit tests and interaction testing## Reference Guide| Concern | Best Practice | Quick Check ||---|---|---|| Reactivity | Use ref and computed intentionally | state updates are traceable || Components | Keep presentational components dumb | no service logic in templates || Props/Events | Use explicit contracts | payload shape documented || Async | Centralize loading and error wrappers | no silent failures |## Constraints### MUST DO- Prefer Composition API for new features- Keep composables framework-light and testable- Provide loading, error, and empty states for async views### MUST NOT DO- Do not mutate props directly- Do not hide side effects in computed values- Do not mix unrelated feature state in one global store## Output Templates```md## Vue Feature Plan- Feature goal: [goal]- Components: [list]- Composables: [list]- State ownership: [local/pinia/route]- Test plan: [list]```## Knowledge Referencecomposition api, script setup, defineProps, defineEmits, provide inject, pinia boundaries, route guards, async components, suspense, error boundaries, hydration awareness## Related Skills- `vite-expert`- `typescript-expert`- `javascript-expert`- `code-reviewer`

Frequently asked questions