nuxt-domain-delivery

Protect Nuxt page-to-Nitro seams with render-mode-aware, verified full-stack slices.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill nuxt-domain-delivery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuxt-domain-delivery
Source: https://github.com/vTRKA/supervibe/tree/main/skills/nuxt-domain-delivery
Command: npx skills add https://github.com/vTRKA/supervibe --skill nuxt-domain-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Nuxt feature work often lands as uncertain, hard-to-verify changes across pages, SSR payloads, Nitro server routes, and runtime configuration, which increases the risk of hydration issues, broken routing, SEO regressions, and deployment surprises.

Core Features & Use Cases

  • Nuxt seam protection: Guides implementation and review across Vue pages/layouts, middleware, Nitro server routes/handlers, render mode boundaries, and SSR/hydration correctness.
  • Evidence-first delivery: Requires source-of-truth inspection, explicit render-mode and routeRules justification, scoped verification, and recorded proof before completion.
  • Rollback discipline: Ensures each change includes a clear rollback path (feature flag/revert/previous build redeploy and related cache/routeRules impacts).

Quick Start

Ask your AI coding tool: implement or review the Nuxt change using Nuxt Domain Delivery, ensuring render mode and routeRules are correct, all server inputs are validated, SSR/hydration risks are handled, SEO is server-rendered, and a rollback path plus scoped verification evidence are recorded.

Frequently Asked Questions about nuxt-domain-delivery

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

FAQPage Schema
How do I prevent hydration mismatches when deploying Nuxt SSR changes?

Prevent Nuxt SSR hydration mismatches by enforcing render-mode-aware verification during implementation. This requires checking SSR payload consistency, validating routeRules, and recording server-rendered SEO proof before completing any page or Nitro server route changes.

What is the best way to plan a rollback for a Nuxt Nitro deployment?

The best way to plan a Nuxt rollback is to define an explicit path using feature flags, reverts, or previous build redeploys. You must document cache invalidation and routeRules impacts to ensure safe Nitro server route recovery.

How do you verify useFetch and useAsyncData data fetching in Nuxt layouts?

Verify Nuxt data fetching by inspecting the source-of-truth and applying scoped verification with confidence caps. This ensures useFetch and useAsyncData payloads correctly cross the page-to-Nitro seam without breaking SSR hydration.

Does this approach work for validating server middleware and runtimeConfig in Nuxt?

Yes, this approach validates Nuxt server middleware and runtimeConfig by requiring server input validation and authz checks. It treats runtimeConfig changes as full-stack slices to prevent deployment surprises across Nitro handlers.

Why do my Nuxt pages break after updating Nitro server routes?

Nuxt pages break after Nitro updates because page-to-Nitro seams are often unverified. Fix this by enforcing evidence-first delivery, which requires source-of-truth inspection and render-mode justification before changes are merged.