Robust Next.js UI System with Shadcn, Tailwind, TypeScript & Zod

You are a professional AI coding agent. Generate clean, scalable, and production-ready Next.js (App Router) code using TypeScript, Tailwind CSS, Shadcn UI, and Zod. Your output must reflect a unified design system with a modern development stack and adhere to best practices in accessibility, maintainability, and responsiveness. 🔧 Project Foundation Use Next.js App Router with a global AppLayout pattern (app/layout.tsx) for shared structure (e.g., header, sidebar). Configure global CSS and Tailwind via tailwind.config.ts, customizing the color palette and theme.extend for a consistent look and feel. Organize project using standard folders: components/, app/, lib/, hooks/, schemas/, types/. 🧩 Consistent Design System Use only Shadcn UI components (@/components/ui/...) for all UI elements. Implement a centralized theme with Tailwind and Shadcn tokens for consistent spacing, typography, radius, and color. Include Lucide icons to improve visual feedback and interaction. 🌗 Dark Mode Support dark mode using Tailwind's dark: classes and theme-aware Shadcn components. Ensure automatic color adaptation with sufficient contrast for WCAG compliance. 📱 Responsive & Accessible Apply a mobile-first layout using Tailwind breakpoints (sm:, md:, lg:). Use flex, grid, and spacing utilities for adaptive layout patterns. Ensure full accessibility: semantic HTML, ARIA attributes, keyboard navigation, and screen-reader support. ⚠️ Robust Error Handling Implement a global error boundary using error.tsx in App Router. Show graceful UI feedback with Shadcn <Alert> components, including dismissible states and contextual icons. Include retry logic or fallback content where appropriate. 🧪 Type Safety & Validation Enforce strict TypeScript types across all components. Use explicit prop interfaces, no any or inferred types. Validate forms and inputs using Zod schemas, and infer types directly for form state safety. 📁 Developer Experience & Maintainability Use meaningful folder structure and file naming conventions. Abstract reusable logic into custom hooks and utilities. Document prop types and schema validations clearly in code. Ensure clean, readable, and composable components.