- Home
- Skills
- Frontend & Web Apps
- Vue Nuxt Pro Kit
Vue Nuxt Pro Kit
Audit SSR hydration, plan Vue 2 to Nuxt 4 migrations, and review Vue 3 architecture with automated scanning scripts.
$14
Works with the AI Agents you already use
Vue Nuxt Pro Kit
Example session with this skill installed
Run an architecture review on this Nuxt 3 project. I'm seeing slow build times and props are getting confusing in the checkout flow. Project path is ./my-nuxt-app.
- Read your context and instructions
- Compiled the vue nuxt pro
I have completed the architecture review for the Nuxt 3 project in ./my-nuxt-app. The scan identified several large components and significant prop drilling in the checkout flow.
Architecture Review: my-nuxt-app
| Priority | Area | Evidence | Impact | Fix | Effort |
|---|---|---|---|---|---|
| P0 | State | composables/useAuth.ts:4 | Cross-request leak (module-scope ref) | Move ref inside useState | S |
| P1 | Components | components/checkout/OrderSummary.vue | High change cost (620 lines, 14 props) | Split into sub-components | M |
| P1 | Props | components/checkout/Step3.vue:12 | Prop drilling (4 levels) | Use Pinia store or Provide/Inject | M |
| P2 | Types | stores/cart.ts:22 | Type safety risk (use of any) | Define strict interfaces | S |
Refactor Example: Prop Drilling in Checkout
Before:
<!-- Step1 -> Step2 -> Step3 -> PaymentInput -->
<Step3 :user-data="userData" :cart-total="total" @update="handleUpdate" />
After:
// stores/checkout.ts
export const useCheckoutStore = defineStore('checkout', () => {
const userData = ref<User | null>(null)
const cartTotal = computed(() => ... )
return { userData, cartTotal }
})
// PaymentInput.vue
const store = useCheckoutStore()
const { userData } = storeToRefs(store)
Next steps
- Fix the P0 leak in
useAuth.tsimmediately to prevent data bleed between users. - Encapsulate the checkout state in a Pinia store to eliminate the 4-level prop drilling.
- Run
node scripts/nuxt-ssr-scan.mjsto check if these changes impact hydration.
Connects securely to your tools. The creator never sees your data.
About this skill
This package provides a comprehensive toolkit for senior Vue and Nuxt developers to audit, migrate, and architect enterprise-grade applications. It solves the technical debt and performance issues that arise when scaling Vue codebases, specifically targeting SSR hydration errors, legacy Vue 2 transitions, and architectural rot. The toolkit includes three specialized agents that perform static scans and manual reviews to identify P0 crashes, data leaks, and breaking changes.
What it does
- SSR & SEO Auditing finds hydration mismatches, cross-request state leaks, and missing technical SEO in Nuxt 3/4 HTML.
- Migration Planning inventories Vue 2/Nuxt 2 codebases to generate a phased roadmap for Nuxt 4, including dependency verdicts and effort estimates.
- Architecture Reviewing analyzes component boundaries, prop drilling, and store usage to provide a prioritized refactor plan.
- Static Scanning uses local scripts to detect large components, undeclared emits, and module-scope reactive state without running the app.
How it works
- Inventory: The agent reads
package.json, lockfiles, and directory structures to determine the Vue/Nuxt version and rendering mode. - Scan: Specialized scripts (
nuxt-ssr-scan.mjs,vue2-scan.mjs, orvue-arch-scan.mjs) analyze the project for specific anti-patterns. - Report: You receive a prioritized findings table with evidence (file:line), impact assessment, and effort estimates (S/M/L).
- Fix: The agent provides minimal before/after code patches and a shippable retest plan for every critical finding.
Frameworks & tools
Built for Vue 2.6/2.7, Vue 3.x, Nuxt 2, and Nuxt 3/4. Supports Pinia, Vuex, Vite, Webpack, Vitest, and TypeScript.
Why this beats prompting it yourself
Generic LLMs often miss the Nuxt-specific data-fetching contract and the subtle differences between Nuxt 3 and 4. These agents use dedicated reference files and scanning scripts to catch cross-request state leaks and hydration mismatches that standard prompts overlook.
Use cases
- Debugging "Hydration mismatch" warnings and flickering content in production Nuxt sites.
- Creating a sprint-by-sprint roadmap for upgrading a legacy Vue 2 CLI project to Nuxt 4.
- Performing a technical due diligence audit on a Vue codebase before a handover or major feature launch.
- Identifying memory leaks caused by module-scope state in SSR environments.
Known limitations
Does not perform Core Web Vitals tuning or content SEO strategy. Cannot migrate apps to other frameworks. Estimates are ranges for planning, not fixed quotes.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.
Requires access to project files like package.json and src/. Cannot run builds or deploys. Vue 2 projects are redirected to the migration planner. Nuxt 3 EOL dates are strictly observed.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 13 days ago
- Software
- codemod
Node.jsnuxi