moai-domain-frontend

Implements frontend components and patterns for React 19, Next.js 16, and Vue 3.5 applications.

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-domain-frontend-seung-zedd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-domain-frontend
Source: https://github.com/Seung-zedd/secure-file-upload/tree/main/.claude/skills/moai-domain-frontend
Command: npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-domain-frontend-seung-zedd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building modern web UIs requires keeping up with rapidly evolving frameworks like React 19, Next.js 16, and Vue 3.5, plus consistent decisions on state management, accessibility, and performance. This Skill provides structured patterns, implementation quickstarts, and verification checklists so frontend work follows current best practices instead of ad-hoc guesses. ## Core Features & Use Cases - Framework Patterns: Covers React 19 Server Components and cache(), Next.js 16 App Router and Server Actions, and Vue 3.5 Composition API with Pinia. - Architecture & Performance Guidance: Includes component architecture with CVA variants, state management with Zustand/Redux Toolkit/Pinia, code splitting, memoization, and Vercel's 45 React best-practice rules. - Quality Gates: Ships red-flag lists, common rationalization counters, and verification checklists covering accessibility, TypeScript strictness, and bundle size. - Use Case: When asked to build a new dashboard page, the Skill guides creation of a Next.js Server Component with Suspense loading states, a validated Server Action using zod, and accessible interactive elements. ## Quick Start Ask the agent to build a React 19 server component page with a Suspense loading state and a validated Next.js server action for form submission.

Frequently Asked Questions about moai-domain-frontend

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

FAQPage Schema
How do I build a React 19 server component with data fetching?▼

Create an async page component that uses React's cache() function to memoize data fetching, then wrap the display component in Suspense with a skeleton fallback. Await the fetched data and pass it as props to the child component.

How to create a Next.js server action with validation?▼

Add the 'use server' directive, define a zod schema for the form fields, and validate FormData with safeParse inside the action. On success, write to the database and call revalidatePath; on failure, return the validation errors.

React vs Vue for a new frontend project, which does this cover?▼

The Skill covers both ecosystems: React 19 with Next.js 16 (Server Components, App Router, Server Actions) and Vue 3.5 with the Composition API, composables, and Pinia state management. Patterns are provided for each framework side by side.

Does Next.js 16 App Router work with TypeScript strict mode?▼

Yes, the patterns assume TypeScript 5.9+ and explicitly forbid the any type in component props and state. Verification checklists require grep proof that no any types exist in new or modified code.

Why is my React bundle size growing after adding components?▼

Bundle growth usually comes from missing code splitting, static imports of large libraries, or unmemoized dependencies. The Skill flags any increase over 50KB without justification and recommends dynamic imports and bundle analyzer output.

What accessibility checks should frontend components pass?▼

Every interactive element needs an accessible name via aria-label or visible text, and async components must define loading, error, and empty states. The Skill treats missing ARIA attributes and unsanitized user HTML as red flags.