nuxt-architecture

Creates domain-driven, type-safe Nuxt 4 project architectures with standardized layouts and flows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Inconsistent Nuxt 4 project architectures can slow teams; this Skill provides a domain-driven, type-safe blueprint to standardize structure and decision-making.

Core Features & Use Cases

  • Domain-driven, type-safe architecture guiding the organization of folders like models, repositories, features, and pages.
  • Clear separation of concerns and a Pattern Flow: Component → Action → Mutation → Repository → API to manage data and UI orchestration.
  • Standard layout and layer guidance for Nuxt 4 apps, including composables, enums, values, and repositories for scalable growth.

Quick Start

Set up a new Nuxt 4 project and organize code according to the standard layout to begin implementing domain-driven features.

Frequently Asked Questions about nuxt-architecture

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

FAQPage Schema
How do I structure a Nuxt 4 project for scalability and domain-driven design?

Structure a Nuxt 4 project using a domain-driven, type-safe blueprint that organizes folders into models, repositories, features, and pages. This standard layout enforces separation of concerns and predictable data flow for scalable application growth.

What is the standard data flow pattern for Vue 3 composition API components in Nuxt?

The standard data flow pattern for Vue 3 composition API components is Component → Action → Mutation → Repository → API. This sequence manages UI orchestration and data fetching to enforce reusability and predictable state management across Nuxt features.

Can I apply this Nuxt architecture to an existing project, or is it only for new apps?

This Nuxt architecture primarily targets new projects and architectural decisions. Applying it to existing apps requires refactoring code into standard layouts like composables, repositories, and features to align with the domain-driven, type-safe blueprint.

What's the best way to organize composables and repositories in a Vue 3 app?

Organize composables and repositories in a Vue 3 app by grouping them into domain-specific feature layers. This domain-driven approach standardizes layouts and separates data orchestration from UI components to ensure type safety and reusability.

Why does my Nuxt 4 project architecture feel inconsistent across multiple features?

Nuxt 4 project architecture feels inconsistent without a standardized blueprint defining required layers and pattern flows. Adopting a domain-driven, type-safe structure for components, actions, and repositories solves this by enforcing predictable data flow and separation of concerns.