nuxt-components

Organizes Vue 3 components with Composition API and script setup for Nuxt 4 projects.

2|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/omakei/adonisjs-architecture-skill --skill nuxt-components-omakei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuxt-components
Source: https://github.com/omakei/adonisjs-architecture-skill/tree/main/nuxt/skills/nuxt-components
Command: npx skills add https://github.com/omakei/adonisjs-architecture-skill --skill nuxt-components-omakei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

In Nuxt 4 Vue projects, component patterns are often ad-hoc, leading to inconsistent structure and duplicated effort. This skill introduces standardized component directories, Composition API usage, and script setup conventions to promote reuse and maintainability.

Core Features & Use Cases

  • Standardized directory layout for components (Common, Detail, Form, Modals, Nav, Slideovers, TabSections, Tables).
  • Script setup order convention and reusable pattern references for consistent development.
  • Clear guidance on naming, organization, and pattern examples like slideovers, modals, and tables.

Quick Start

Create a new Vue 3 component following the Composition API pattern and place it under components/ with a PascalCase filename.

Frequently Asked Questions about nuxt-components

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

FAQPage Schema
What is the best way to structure Vue 3 components in a Nuxt 4 project?

The best way to structure Vue 3 components in a Nuxt 4 project is using standardized directory layouts like Common, Detail, Form, and Modals. This approach enforces consistent naming conventions and script setup order to ensure maintainability and team collaboration.

How do I organize reusable UI patterns like modals and tables using the Composition API?

You organize reusable UI patterns by implementing Vue 3 components with the Composition API and script setup, placing them in categorized directories like Slideovers and Tables. This standardizes pattern references and script setup order for consistent development.

Does this component pattern approach work for both small UI blocks and complex Nuxt 4 views?

Yes, this component pattern approach works for Nuxt 4 projects by providing reusable UI blocks like slides, modals, and tables. It applies standardized directory structures and script setup conventions regardless of component complexity.

Why should I use script setup order conventions for Vue 3 components?

You should use script setup order conventions to prevent ad-hoc Vue 3 component patterns that lead to inconsistent structure and duplicated effort. Enforcing a recommended setup order ensures maintainability and promotes reuse across the project.

Can I use these standardized component patterns without prior Nuxt experience?

You can use these standardized component patterns by creating a Vue 3 component with the Composition API and placing it under the components directory with a PascalCase filename. However, familiarity with Nuxt 4 directory structures is necessary for proper organization.

What are the limitations of enforcing standardized directory layouts for Vue components?

A limitation of enforcing standardized directory layouts is that it restricts ad-hoc component organization, requiring strict adherence to specific folders like TabSections and Nav. Teams must conform to these naming conventions and documentation references to maintain consistency.