vue-development-guides▌
hyf0/vue-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Best practices and architectural patterns for Vue 3 and Nuxt 3 projects.
- ›Emphasizes core principles: predictable state with single source of truth, explicit data flow (props down, events up), and small focused components
- ›Requires Composition API with <script setup lang=\"ts\"> as the default, and mandates following detailed guides for reactivity, SFC structure, and component organization
- ›Provides a checklist-driven approach covering component splitting, composable extraction, an
Vue.js Development Guides
Tasks Checklist
- Followed the core principles
- Followed the defaults unless there is a good reason not to
- Followed the reactivity best practices
- Followed the component best practices
- Followed the Vue SFC best practices
- Kept components focused
- Split large components into smaller ones when needed
- Moved state/side effects into composables if applicable
- Followed data flow best practices
Core Principles
- Keep state predictable: one source of truth, derive everything else.
- Make data flow explicit: Props down, Events up for most cases.
- Favor small, focused components: easier to test, reuse, and maintain.
- Avoid unnecessary re-renders: use computed properties and watchers wisely.
- Readability counts: write clear, self-documenting code.
Defaults (unless the user says otherwise)
- Prefer the Composition API over the Options API.
Reactivity
IMPORTANT: You MUST follow the references/reactivity-guide.md for reactive state management when creating, updating a component or a composable.
Components
IMPORTANT: You MUST follow the references/sfc-guide.md for best practices when working with Vue SFCs.
- Prefer Vue Single-File Components (SFC) using
<script setup lang="ts">(TypeScript) by default. - In Vue SFCs, keep sections in this order:
<script>→<template>→<style>.
Keep components focused
Split a component when it has more than one clear responsibility (e.g. data orchestration + UI, or multiple independent UI sections).
- Prefer smaller components + composables over one “mega component”
- Move UI sections into child components (props in, events out).
- Move state/side effects into composables (
useXxx()).
NOTE: This rule also applies to the entry component (e.g. App.vue) in a Vue / Nuxt project by default.
Data Flow
IMPORTANT: You MUST follow the references/data-flow-guide.md for passing and receiving data between components using:
- Props
- Emits
v-model- provide/inject
For sharing data across the app, please follow the references/state-management-guide.md and consider using a Store for state management solution.
How to use vue-development-guides on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add vue-development-guides
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches vue-development-guides from GitHub repository hyf0/vue-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate vue-development-guides. Access the skill through slash commands (e.g., /vue-development-guides) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★29 reviews- ★★★★★Dhruvi Jain· Dec 24, 2024
vue-development-guides reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Naina Agarwal· Dec 24, 2024
We added vue-development-guides from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kofi Chen· Dec 4, 2024
vue-development-guides fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kofi Thompson· Nov 23, 2024
vue-development-guides is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Oshnikdeep· Nov 15, 2024
I recommend vue-development-guides for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Yusuf Brown· Nov 15, 2024
Keeps context tight: vue-development-guides is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ishan Kim· Oct 14, 2024
Keeps context tight: vue-development-guides is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kofi Nasser· Oct 10, 2024
Solid pick for teams standardizing on skills: vue-development-guides is focused, and the summary matches what you get after install.
- ★★★★★Ganesh Mohane· Oct 6, 2024
Useful defaults in vue-development-guides — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Naina Shah· Oct 6, 2024
vue-development-guides is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 29