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/README.md

View on GitHub
# vue-nuxt evals

These cases are not an executable test suite — they are routing and capability rubrics for humans
or a router harness. To run them, feed each `should_trigger` prompt to the skill router and confirm
`vue-nuxt` is selected, then feed each `should_not_trigger` prompt and confirm it routes to the
named sibling (e.g. `nextjs`, `astro`, `cloudflare`, `e2e-testing`, `fastapi`) rather than here.
The single `capability` case is a manual check: have the agent answer the scenario with the skill
loaded, then verify every line in `must_include` is satisfied by the worked answer (Nuxt-4
detection first, `$fetch`→`useAsyncData`/`useFetch` with a shared key, module-`ref`→`useState`/Pinia
with the per-request-leak explanation, payload-size notes, and no RSC mental models). Pair this with
`scripts/verify.sh` run against a real Vue/Nuxt repo to confirm the emitted code typechecks/builds.
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