nuxt-foundation

Define a Nuxt 3 TypeScript baseline with folder structure, naming conventions, and scripts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Jozaguts/futzo --skill nuxt-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuxt-foundation
Source: https://github.com/Jozaguts/futzo/tree/main/.codex/skills/nuxt-foundation
Command: npx skills add https://github.com/Jozaguts/futzo --skill nuxt-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a baseline Nuxt 3 (TypeScript) setup with project structure and conventions to streamline migration projects and ensure consistency across Nuxt-based apps.

Core Features & Use Cases

  • Standard folder structure for Nuxt 3 projects with a migration-friendly layout.
  • Clear naming conventions for components, routes, and files.
  • Base scripts for development, building, linting, and validation.
  • Guidance for migrating toward Nuxt 4 using the app directory approach.

Quick Start

Initialize the Nuxt foundation baseline in your repository and align folder structure and scripts.

Frequently Asked Questions about nuxt-foundation

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

FAQPage Schema
How do I set up a standard Nuxt 3 TypeScript project structure for migration?

To set up a standard Nuxt 3 TypeScript project structure for migration, apply a baseline configuration that defines an app directory approach, configures srcDir, and establishes naming conventions for components, routes, and files. This standardizes project setup to ensure consistency across Nuxt-based apps.

What is the best way to migrate a Nuxt 3 app toward Nuxt 4 directory structure?

The best way to migrate a Nuxt 3 app toward Nuxt 4 directory structure is by adopting the app directory approach. This migration-friendly layout aligns folder structure and base scripts to transition project architecture smoothly while maintaining TypeScript conventions.

What naming conventions should I use for Nuxt 3 components and routes?

For Nuxt 3 components and routes, you should use clear naming conventions defined by a baseline setup. Standardizing file and route names within a migration-friendly app directory layout ensures consistency across Nuxt-based apps and streamlines team collaboration.

Do I need TypeScript to use this Nuxt 3 project baseline?

Yes, TypeScript is required as this is a Nuxt 3 TypeScript baseline. It is designed to standardize project structure, scripts, and conventions specifically for Nuxt-based apps using TypeScript to ensure a consistent and migration-friendly architecture.

What scripts are recommended for a standard Nuxt 3 development workflow?

Recommended scripts for a standard Nuxt 3 development workflow include base commands for development, building, linting, and validation. Establishing these base scripts standardizes the development lifecycle and ensures consistent project operations across Nuxt apps.

When should I not use a standard baseline for my Nuxt project setup?

You should avoid using a standard Nuxt project setup baseline if your architecture does not rely on the app directory approach or if your project does not use TypeScript. The baseline specifically standardizes srcDir, naming conventions, and scripts for Nuxt 3 apps migrating toward Nuxt 4.