Description
Scaffold the base folder structure for the web project according to the agreed architecture. No components, no layout, no placeholder UI.
Folders to create
components/ - reusable UI components
components/ui/ - shadcn components only
app/api/ - Next.js route handlers
lib/ - third party configs and utility functions
hooks/ - custom React hooks
types/ - shared TypeScript types (API responses, common types)
services/ - reusable backend caller methods as classes, using fetch (no axios)
services/actions/ - Next.js server actions
Rules to respect (add as a comment or README in each folder)
- Never use axios, use native fetch for edge compatibility
- Services must be classes
- Server actions go under services/actions, be mindful of Next.js caching
- shadcn components go under components/ui only
- Custom hooks go under hooks, never inline in components
- Types shared across features go under types
Acceptance Criteria
Description
Scaffold the base folder structure for the web project according to the agreed architecture. No components, no layout, no placeholder UI.
Folders to create
components/- reusable UI componentscomponents/ui/- shadcn components onlyapp/api/- Next.js route handlerslib/- third party configs and utility functionshooks/- custom React hookstypes/- shared TypeScript types (API responses, common types)services/- reusable backend caller methods as classes, using fetch (no axios)services/actions/- Next.js server actionsRules to respect (add as a comment or README in each folder)
Acceptance Criteria
.gitkeepor a short explanatory comment file