@tank/vue-nuxt

Standardize Vue 3 and Nuxt 3 production application patterns.

1|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/tankpkg/packages --skill tank-vue-nuxt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: @tank/vue-nuxt
Source: https://github.com/tankpkg/packages/tree/main/skills/vue-nuxt
Command: npx skills add https://github.com/tankpkg/packages --skill tank-vue-nuxt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes guesswork from building modern Vue 3 and Nuxt 3 applications by turning scattered framework guidance into a consistent production workflow.

Core Features & Use Cases

  • Component Architecture: Use composition-first patterns with script setup, reactive primitives, and reusable composables to build maintainable UI code.
  • TypeScript and State Management: Apply typed props, emits, models, provide/inject, and Pinia setup stores for safer application state and component contracts.
  • Nuxt Data and App Lifecycle: Handle SSR-safe fetching, server routes, middleware, plugins, runtime config, and route-level rendering rules in one place.
  • Production Delivery: Add SEO metadata, Nitro deployment presets, performance optimizations, and testing practices for reliable shipping.
  • Use Case: A team starting a new Nuxt app can use this Skill to standardize how pages fetch data, how stores are structured, how routes render, and how the app is tested before release.

Quick Start

Ask for a production Vue 3 or Nuxt 3 implementation plan for your feature, and include the component, state, data fetching, rendering, deployment, and testing requirements you want covered.

Frequently Asked Questions about @tank/vue-nuxt

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

FAQPage Schema
How do I structure a production Nuxt 3 application with SSR and Pinia?

To structure a production Nuxt 3 application, use Composition API conventions, Pinia setup stores, SSR-safe data fetching, and route-level rendering rules. This approach standardizes component authoring, state management, and server-side rendering workflows into a consistent pattern.

What is the best way to handle data fetching and state management in Vue 3?

The best way to handle data fetching and state in Vue 3 is combining Pinia setup stores with typed composables. This method uses reactive primitives for safer application state and strict TypeScript contracts for component communication.

Does this Vue and Nuxt workflow require TypeScript and Composition API?

Yes, this Vue and Nuxt workflow requires TypeScript typing and Composition API conventions. It mandates script setup for component authoring and typed props, emits, and provide/inject to ensure safer application state and maintainable UI code.

How do I configure Nuxt route rules and Nitro deployment presets?

You configure Nuxt route rules and Nitro presets by defining route-level rendering strategies and deployment targets within your Nuxt configuration. This enables specific server-side rendering behaviors and performance optimizations for production delivery.

Can I use VueUse and Nuxt testing practices together in a Vue 3 app?

Yes, you can integrate VueUse and Nuxt testing practices together. This combination allows you to apply reactive composables while standardizing testing workflows, ensuring reliable shipping and application stability before release.

When do I need SSR-safe fetching and middleware in Nuxt 3?

You need SSR-safe fetching and middleware in Nuxt 3 when building server-side rendered applications that require protected routes or pre-fetching data. This ensures data consistency across server and client during the app lifecycle.