What problem does it solve? Scaling React and Next.js applications in Nx monorepos often leads to tangled imports, unclear ownership, and inconsistent component architecture. This Skill provides a proven library organization pattern, component conventions, and dependency rules that keep large codebases maintainable. ## Core Features & Use Cases - Domain-Based Library Structure: Organizes code into feature, ui, data-access, util, and api-interfaces libraries with clear tagging and naming conventions. - Component Architecture Patterns: Distinguishes smart/container components from presentational components, with patterns for React Server Components, client components, Server Actions, and data fetching via React Query or Zustand. - Module Boundary Enforcement: Provides ESLint configuration for @nx/enforce-module-boundaries with tag-based dependency constraints. - Use Case: When adding a new user-management domain to a Next.js app in an Nx workspace, use this Skill to scaffold the feature, ui, and data-access libraries, wire up TypeScript paths, and enforce that UI libraries never depend on data-access code. ## Quick Start Ask the AI to set up a new domain library structure for a Next.js app in your Nx workspace following the react-nx-patterns conventions.
