vue-project-naming-structure

Generate Vue 3 project scaffolds with standardized src/ folder and naming conventions.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/bmslabs/bmlabs-projects-templates --skill vue-project-naming-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vue-project-naming-structure
Source: https://github.com/bmslabs/bmlabs-projects-templates/tree/main/view-vuejs/.github/skills/vue-project-naming-structure
Command: npx skills add https://github.com/bmslabs/bmlabs-projects-templates --skill vue-project-naming-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains a predictable Vue project structure by standardizing file locations and naming conventions across templates, reducing setup time and onboarding friction.

Core Features & Use Cases

  • Standardized src layout with modules, views, and components
  • Enforced naming rules for components (PascalCase), views (Suffix View), and files
  • Guidance for English identifiers in code while allowing Spanish in UI labels and messages

Quick Start

Create a new Vue project skeleton that follows BM naming and folder structure

Frequently Asked Questions about vue-project-naming-structure

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

FAQPage Schema
What is the best way to structure a Vue 3 project with consistent naming conventions?

The best way to structure a Vue 3 project is by applying standardized folder schemes and naming conventions, enforcing PascalCase for components and suffixing views, to reduce onboarding friction and ensure predictable file locations.

How do I organize modules, views, and components in a Vue project?

You organize modules, views, and components in a Vue project by auto-generating a clean src/ layout. This standardized structure separates assets and logic predictably, accelerating setup time for new templates and team onboarding.

Does this Vue project structure standardize UI text and code identifiers differently?

Yes, this Vue project structure standardizes code identifiers and UI text differently. It enforces English identifiers in code while allowing Spanish text in UI labels and messages to satisfy specific BM guidelines.

Can I use this naming structure for existing Vue templates or only new scaffolds?

You can use this naming structure for both new template scaffolds and standard Vue 3 projects. It applies standardized file placement and folder schemes to ensure consistent architecture across any Vue codebase.

Why does consistent Vue project naming reduce team onboarding time?

Consistent Vue project naming reduces team onboarding time by maintaining a predictable project structure. Standardizing file locations and naming rules across templates eliminates structural guesswork for new developers.

What are the limitations of applying standardized Vue folder schemes to legacy codebases?

A limitation of applying standardized Vue folder schemes to legacy codebases is the manual refactoring required to map existing files into the new modules, views, and components layout without breaking current imports.