Skip to content

ericrisco/rsc-harness / skills/vue-nuxt

vue-nuxt

Verified

Use when building or reviewing a Vue 3 + Nuxt 4 app — `<script setup>` reactivity, SSR/SSG/hybrid `routeRules`, the `app/`+`server/` layout, SSR-safe fetching (`useFetch`/`useAsyncData`) and state (`useState`/Pinia), Nitro routes, hydration mismatches, Nuxt 3→4 migration. NOT React/RSC (that is nextjs), NOT a static islands site (that is astro).

FileKindSize
SKILL.mdskill md16.4 KB
evals/README.mdmarkdown906 B
evals/cases.yamlconfig3.8 KB
references/data-and-state.mdmarkdown5.1 KB
references/migration-nuxt4.mdmarkdown3.9 KB
references/nitro-and-rendering.mdmarkdown4.4 KB
references/reactivity.mdmarkdown5.2 KB
scripts/verify.shexecutablescript5.5 KB

evals/cases.yaml

View on GitHub
skill: vue-nuxt

should_trigger:
  - prompt: "Why does my Nuxt page fetch the API twice on page load?"
    why: "Classic SSR double-fetch symptom from a bare $fetch in setup — the core data-fetching boundary this skill owns. Non-obvious: the user describes a symptom, not an API."
  - prompt: "Hydration node mismatch error in my .vue page after deploy"
    why: "Hydration mismatch is a Vue/Nuxt SSR trap (Date/random/localStorage in setup); .vue + hydration is squarely this skill."
  - prompt: "Should I use useFetch or useAsyncData here, and how do I share the result between two components?"
    why: "The exact useFetch-vs-useAsyncData decision plus shared-key dedupe — the load-bearing Nuxt section."
  - prompt: "Building a Nuxt 4 app, where do composables and stores go now?"
    why: "Nuxt 4 app/ srcDir structure (app/composables, app/stores) — the version/structure detection this skill leads with."
  - prompt: "per què el meu estat de Pinia es filtra entre peticions al servidor?"
    why: "Catalan; SSR cross-request state leak (module-level singleton / store init at module scope). Non-obvious server-side leak that this skill diagnoses."
  - prompt: "Convert this Vue component to defineModel and reactive props destructure"
    why: "Vue 3.5 / 3.4 Composition API modernization (defineModel, reactive props destructure) — the reactivity core."
  - prompt: "How do I set per-route ISR and SSG in nuxt.config with routeRules?"
    why: "routeRules hybrid rendering strategy — non-obvious that prerender/swr/isr live in routeRules, not per-page config."

should_not_trigger:
  - prompt: "Set up React Server Components and server actions in my app/ dir"
    route_to: nextjs
    why: "RSC and server actions are React/Next concepts; Vue has no server-component boundary. The shared 'app/' word is a false signal."
  - prompt: "Build a content-heavy static blog mixing React and Vue islands"
    route_to: astro
    why: "Multi-framework islands on a content-first static site is Astro's domain, not a single-framework Nuxt app."
  - prompt: "Deploy my Nuxt app to Cloudflare Pages with the right adapter"
    route_to: cloudflare
    why: "Platform deploy specifics (adapter, edge config, bindings) belong to cloudflare; this skill only selects the Nitro preset."
  - prompt: "Write Playwright E2E tests for my Vue checkout flow"
    route_to: e2e-testing
    why: "E2E test strategy and Playwright authoring live in e2e-testing; this skill only states the test setup."
  - prompt: "Build a Python FastAPI backend for my Vue frontend"
    route_to: fastapi
    why: "A non-Nitro backend in Python is fastapi's domain; this skill owns only the Nitro/JS server."

capability:
  - scenario: >
      A Nuxt 4 product page double-fetches the product API on SSR (data appears twice in the
      network panel) and a shared "current user" value leaks between concurrent requests on the
      server. The current code does `const product = await $fetch('/api/products/' + id)` in setup
      and exports `export const user = ref(null)` at module scope. Ask the agent to fix both and
      explain why.
    must_include:
      - "Detects/confirms Nuxt 4 (app/ srcDir, nuxt.config) before prescribing Nuxt-only APIs"
      - "Replaces the bare $fetch in setup with useAsyncData/useFetch (one server fetch + payload transfer to client) and explains $fetch does not transfer a payload"
      - "Uses a stable key so the two components share one data/error/status ref (dedupe + auto-cleanup)"
      - "Replaces the module-level ref with useState(key, init) or a Pinia store, explaining the per-request server leak from a module singleton"
      - "Notes shallowRef payload (Nuxt 4) and/or pick/transform to keep the SSR payload small where relevant"
      - "Does NOT introduce RSC / 'use server' / server-component mental models"
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall