moai-domain-frontend

Implements React 19, Next.js 16, and Vue 3.5 frontend patterns with component architecture guidance.

2|Updated May 27, 2026
One-click install
npx skills add https://github.com/yekinya/moai-novel --skill moai-domain-frontend-yekinya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-domain-frontend
Source: https://github.com/yekinya/moai-novel/tree/main/moai-novel/.claude/skills/moai-domain-frontend
Command: npx skills add https://github.com/yekinya/moai-novel --skill moai-domain-frontend-yekinya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building modern web interfaces requires keeping up with rapidly evolving frameworks like React 19, Next.js 16, and Vue 3.5, and developers often struggle to apply correct patterns for server components, state management, accessibility, and performance optimization. ## Core Features & Use Cases - Framework Patterns: Provides detailed guidance for React 19 server components and concurrent features, Next.js 16 App Router with Server Actions and ISR, and Vue 3.5 Composition API with Pinia. - Component Architecture: Covers design tokens, CVA variants, compound components, and accessible dialog/tabs implementations with focus management. - Performance Optimization: Includes code splitting, dynamic imports, image optimization, memoization, virtualization, and Web Vitals tracking patterns. - Use Case: When building a dashboard page, use this Skill to generate a Next.js server component with cached data fetching, Suspense streaming boundaries, and a client component using useOptimistic for instant UI feedback. ## Quick Start Ask the AI to build a React 19 dashboard page with server components, Suspense loading states, and an accessible CVA-based button component.

Frequently Asked Questions about moai-domain-frontend

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

FAQPage Schema
How do I use React 19 server components with data fetching?

Create an async server component that fetches data directly, wrapping the fetch in React's cache() function for request deduplication. Use Suspense boundaries with skeleton fallbacks for streaming, and pass data to client components only where interactivity is needed.

How to handle forms with Next.js Server Actions?

Define a server action with the 'use server' directive, validate FormData with Zod's safeParse, and return error objects on failure. In the client, use useActionState to manage form state and revalidatePath to refresh cached data after mutations.

What is the difference between Zustand, Redux Toolkit, and Pinia for state management?

Zustand and Redux Toolkit are React state libraries, with Zustand offering a lighter API and Redux Toolkit providing structured slices. Pinia is the official state management library for Vue 3, designed around the Composition API with TypeScript support.

Does Next.js 16 support incremental static regeneration?

Yes, Next.js supports ISR through the revalidate export for time-based revalidation and revalidatePath or revalidateTag for on-demand invalidation. Tag-based caching lets you invalidate specific data without rebuilding entire pages.

When should I not use server components in React?

Avoid server components when you need event handlers, browser APIs like localStorage, React hooks, or real-time updates. Server components also add network round trips, so client components with proper caching can outperform them for highly interactive UI.

Why does my React app re-render too often?

Common causes include inline function definitions creating new references each render and missing memoization. Use useCallback for stable callbacks, useMemo for expensive computations, memo for pure child components, and useDeferredValue for expensive renders tied to user input.