folder-structure

name

folder-structure

description

Enforce the standard Next.js/React consumer-app folder structure, naming, file placement, and data-flow rules for projects using Vayu UI. Use when creating, moving, naming, or reviewing pages, ui components, ui hooks, forms, modals, drawers, popovers, API services, TanStack Query hooks, WebSocket/Socket.io hooks and services, types, Zod schemas, table columns, sections, or project architecture. This skill answers "where does this go?" for app projects, not the Vayu UI toolkit monorepo.

Folder Structure

Use this locked app architecture for Next.js App Router or React projects using Vayu UI. Pages stay thin, API work stays centralized, domain UI lives in containers/, and all reusable UI (Vayu primitives, custom primitives, shared app components, and non-API hooks) lives under ui/.

Structure

project-root/
├── app/                       # routes/layouts/metadata/route handlers only
│   ├── (auth)/                # auth shell: login/register
│   ├── (dashboard)/           # main app shell
│   ├── api/                   # Next route handlers, only if needed
│   ├── layout.tsx             # root providers/fonts/metadata
│   ├── page.tsx               # home
│   └── globals.css
├── api/
│   ├── api.ts                 # axios client singleton, interceptors
│   ├── services/              # raw HTTP functions: authService.ts
│   ├── hooks/                 # TanStack Query: useLogin.ts, useUsers.ts
│   └── types/                 # rare API-only local types
├── ws/
│   ├── ws.ts                  # socket.io client singleton
│   ├── services/              # socket emitters/listeners: chatSocketService.ts
│   ├── hooks/                 # React hooks per channel: useChatSocket.ts
│   └── types/                 # WS event/message payload types
├── containers/
│   ├── Modals/
│   ├── Forms/
│   ├── PopOver/
│   ├── Drawer/
│   ├── Card/
│   └── Sections/
├── ui/
│   ├── components/            # reusable app components, Vayu/custom primitives
│   ├── hooks/                 # non-API app hooks, primitive hooks
│   └── utils/                 # helpers for sibling folders, components and hooks
├── types/
│   ├── api-types/             # shared API contracts
│   └── enums/
├── utils/
│   ├── validations/           # Zod schemas
│   └── columns/               # TanStack Table columns
├── lib/                       # axios/query-client/auth adapters
└── public/

Placement

Path	Put Here	Keep Out
app/	route segments, layout.tsx, page.tsx, route handlers, loading/error boundaries	business components, API service calls, table columns
api/api.ts	axios client singleton, interceptors, global error handling	feature logic, UI imports
api/services/	fetch/axios functions returning typed data	React hooks, UI imports
api/hooks/	one TanStack Query hook per file	non-API hooks, WS hooks
ws/ws.ts	socket.io client singleton, connection config	feature logic, UI imports
ws/services/	socket.io emitters/listeners per feature	React hooks, UI imports
ws/hooks/	one React hook per channel; consumes ws/services	non-WS hooks, direct socket.io client usage
ws/types/	WS event names, message payload types	feature-local one-off types
containers/Forms/	React Hook Form + Zod forms	generic inputs/primitives
containers/Modals/	concrete modal/dialog instances	generic dialog primitive
containers/PopOver/	concrete popover instances	generic popover primitive
containers/Drawer/	concrete drawer/sheet instances	generic drawer primitive
containers/Card/	complex domain cards	base card primitive
containers/Sections/	chunks from large pages	generic components
ui/components/	Vayu UI primitives, custom primitives, reusable domain-agnostic app components	forms, modals, drawers, popovers, page sections
ui/hooks/	non-API hooks (useDebounce, useMediaQuery) and hooks used by UI primitives	TanStack Query hooks, WS hooks
ui/utils/	helpers used by ui/components/ and ui/hooks/	validations, columns, feature utils
types/api-types/	shared request/response contracts	feature-local one-off types
types/enums/	project enums	string constants hidden in components
utils/validations/	Zod schemas	UI primitive helpers
utils/columns/	TanStack Table columns	inline route-page column defs
lib/	query-client, auth adapters, and other singletons	feature UI

Prefer types/api-types/ over api/types/ when a contract is reused. Add index.ts barrels inside api/services/, api/hooks/, ws/services/, ws/hooks/, ui/components/, and container category folders when multiple files exist.

Data Flow

app/page or layout -> containers/* -> api/hooks/* -> api/services/* -> api/api.ts -> backend
app/page or layout -> containers/* -> ws/hooks/* -> ws/services/* -> ws/ws.ts -> backend
containers/* -> ui/components/* | utils/validations/* | utils/columns/* | types/*
api/hooks/* -> api/services/*
api/services/* -> types/api-types/*
ws/hooks/* -> ws/services/*
ws/services/* -> ws/types/*
ui/components/* -> ui/hooks/* | ui/utils/*

Keep imports one-way. Lower layers must not import pages, containers, or domain UI.

Naming

Category	Pattern	Example
API types	<APIname><Request/Response>.ts	LoginResponse.ts, GetUsersRequest.ts
API services	<feature>Service.ts	authService.ts, paymentService.ts
Query hooks	use<Operation>.ts	useLogin.ts, useUsers.ts
WS services	<feature>SocketService.ts	chatSocketService.ts, notificationSocketService.ts
WS hooks	use<ChannelName>.ts	useChatSocket.ts, useNotifications.ts
WS types	<Feature>SocketPayload.ts, <Feature>SocketEvent.ts	ChatSocketPayload.ts
UI components	PascalCase.tsx	DataTable.tsx, Button.tsx
UI hooks	use<Name>.ts	useDebounce.ts, useMergeRefs.ts
Modals	<Action><Modal>.tsx	AddUserModal.tsx, DeleteConfirmModal.tsx
Drawers	<Name>Drawer.tsx	UserDetailsDrawer.tsx
Popovers	<Name>Popover.tsx	UserActionsPopover.tsx
Forms	<Name>Form.tsx	LoginForm.tsx, CheckoutForm.tsx
Sections	<MainFile><SectionName>Section.tsx	OnboardingPageInfoSection.tsx
Zod schemas	<feature>Schema.ts	loginSchema.ts, userSchema.ts
Table columns	<feature>Columns.ts	userColumns.ts, orderColumns.ts
Enums	PascalCase.ts	UserRole.ts, OrderStatus.ts

Use PascalCase for React components/enums. Use camelCase for services, schemas, columns, utilities, and hooks.

Recipes

• Page: keep page.tsx orchestration-only. Compose containers/sections; do not define full forms, modals, or columns inline.
• Page size: extract sections after about 100 lines or multiple visual blocks. Never let any page.tsx exceed 400 lines; split into containers/Sections/<Page><SectionName>Section.tsx.
• Form: containers/Forms/<Name>Form.tsx + utils/validations/<feature>Schema.ts + types/api-types/* + api/hooks/use<Operation>.ts.
• Users table page: use api/hooks/useUsers.ts, utils/columns/userColumns.ts, and action UI such as containers/PopOver/UserActionsPopover.tsx.
• Modal/drawer/popover: concrete instance in containers/<Category>/; underlying primitive from ui/components/; Vayu UI usage/composition verified with the MCP usage skill.
• Reusable app component: ui/components/<Name>.tsx when it is domain-agnostic and shared across containers/pages.
• API: containers and ui/components/ call query hooks, not services. Services perform HTTP only; query hooks own query keys, useQuery, and useMutation.
• WebSocket: containers/ → ws/hooks/use<ChannelName> → ws/services/<feature>SocketService.ts → ws/ws.ts. UI imports hooks only; hooks import services only; services import the socket client only.
• Root utils/: app-level validations, columns, and feature helpers. ui/utils/: helpers scoped to ui/components/ and ui/hooks/ only.

Anti-Patterns

• Do not put domain forms, modals, drawers, popovers, cards, or large sections in ui/components/.
• Do not create a root-level components/ or hooks/ folder — use ui/components/ and ui/hooks/ instead.
• Do not put primitives in containers/.
• Do not call fetch or axios directly from page.tsx, containers, forms, or UI primitives.
• Do not put TanStack Query hooks in ui/hooks/.
• Do not define table columns inside route pages.
• Do not let app/ become a business-component dumping ground.
• Do not let any page.tsx exceed 400 lines.
• Do not put app validations, columns, or feature helpers in ui/utils/.
• Do not duplicate shared API contracts between api/types/ and types/api-types/.
• Do not import upward, such as api/services importing from containers.
• Do not use Socket.io client directly in UI or containers; always go through ws/hooks/.
• Do not put WS hooks in ui/hooks/.
• Do not duplicate WS types between ws/types/ and types/ws-types/.