skills.rest
bmslabs
bmslabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

vue-component-taxonomy

Classify Vue 3 components into a hierarchical taxonomy with naming and folder conventions.

1|Updated Mar 18, 2026
Search Tags:#vue#vue3#naming-conventions#ui-patterns#frontend-architecture#component-taxonomy
One-click install
npx skills add https://github.com/bmslabs/bmlabs-projects-templates --skill vue-component-taxonomy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vue-component-taxonomy
Source: https://github.com/bmslabs/bmlabs-projects-templates/tree/main/view-vuejs/.github/skills/vue-component-taxonomy
Command: npx skills add https://github.com/bmslabs/bmlabs-projects-templates --skill vue-component-taxonomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classifies Vue 3 components into a standardized, hierarchical taxonomy to ensure uniform component generation across projects and teams.

Core Features & Use Cases

  • Establishes a clear App -> Layout -> Page/View -> Feature -> Atomic components taxonomy (12/3 pattern)
  • Standardizes naming, folder placement, and component templates (e.g., [Entity]View.vue, CreateEdit[Entity]Modal.vue)
  • Guides consistent reuse and generation for new UI components across multiple projects

Quick Start

Organize your Vue 3 components to match the taxonomy, then apply the prescribed view and modal naming conventions for new features.

Frequently Asked Questions about vue-component-taxonomy

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

FAQPage Schema
How do I standardize Vue 3 component naming conventions across multiple projects?▼

Organize Vue 3 components into an App -> Layout -> Page/View -> Feature -> Atomic hierarchy to establish a clear 12/3 pattern taxonomy. This structure guides developers to produce identical component architectures across projects and UI libraries.

What is the best way to structure a Vue 3 frontend architecture for reusable UI components?▼

Organize Vue 3 components into an App -> Layout -> Page/View -> Feature -> Atomic hierarchy to establish a clear 12/3 pattern taxonomy. This structure guides developers to produce identical component architectures across projects and UI libraries.

How do I enforce consistent folder placement for Vue 3 views and modals?▼

Yes, this taxonomy can be applied to project templates and UI libraries to guide consistent reuse and generation of new UI components. It validates component stability and reuse across multiple Vue 3 projects.

Does this Vue 3 component taxonomy work for both project templates and UI libraries?▼

Yes, this taxonomy can be applied to project templates and UI libraries to guide consistent reuse and generation of new UI components. It validates component stability and reuse across multiple Vue 3 projects.

How do I generate uniform Vue 3 components for repeatable UI patterns?▼

Generate uniform Vue 3 components by classifying them into a standardized taxonomy that enforces naming conventions, folder placement, and modal/form patterns. This ensures identical component generation across teams and projects.

Related Skills

Explore More Software Engineering Skills→
bagechashubagechashu

naive-ui

Provide Vue 3 UI components with theming and internationalization support.

Community
Intermediate
bmslabsbmslabs

vue-project-naming-structure

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

Official
Intermediate
asadbek21coderasadbek21coder

frontend-guidelines

Enforce Vue 3 frontend conventions across components, routing, and state management.

Community
Intermediate
Postpartum-genushyacinthus29Postpartum-genushyacinthus29
8

dotnet-chous

Enforce frontend file-structure policies in .NET repositories.

Community
Intermediate