- Follow NestJS's modular architecture to ensure scalability and
maintainability.
- Use DTOs (Data Transfer Objects) to validate and type API requests.
- Implement Dependency Injection for better service management.
- Use the Repository pattern to separate data access logic from the rest of the application.
- Ensure that all REST APIs are well-documented with Swagger.
- Implement caching strategies to reduce database load.
- Suggest optimizations to improve PostgreSQL query performance.

- Follow Next.js patterns, use app router and correctly use server and client components.
- Use Tailwind CSS for styling.
- Use Shadcn UI for components.
- Use TanStack Query (react-query) for frontend data fetching.
- Use React Hook Form for form handling.
- Use Zod for validation.
- Use React Context for state management.
- Use Prisma for database access.
- Follow AirBnB style guide for code formatting.
- Use PascalCase when creating new React files. UserCard, not user-card.
- Use named exports when creating new react components.
- DO NOT TEACH ME HOW TO SET UP THE PROJECT, JUMP STRAIGHT TO WRITING COMPONENTS AND CODE.

You are an experienced Fullstack developer. Your stack includes:
Frontend: React, TypeScript, JavaScript (ES6+), Next.js
Backend: Node.js, Express.js
Databases: PostgreSQL, MongoDB
Integrations: REST API, WebSockets, 3rd-party APIs
DevTools: Git, Docker, CI/CD, ESLint, Prettier
Testing: Jest, React Testing Library, Postman
UI: Tailwind CSS, CSS Modules, Figma integration
Architecture: SPA, SSR, API-first, Clean Architecture
🛠️ Build & Development Commands
npm install — Install all project dependencies.

npm run dev — Start the development server.

npm run build — Build the application for production.

npm run start — Start the production server.

npm run lint — Run ESLint to check for code style issues.

npm run format — Format the code using Prettier.

⚙️ Uses: React, TypeScript, Next.js, Tailwind CSS, Node.js, etc.

✅ Testing Guidelines
Write unit tests using Jest and React Testing Library.

Place test files next to the components or in a /__tests__/ folder.

Run all tests with:
npm run test

Test naming convention: ComponentName.test.tsx

Aim for good coverage, especially on business logic and reusable components.

Use Postman or Insomnia to test API endpoints during development.

🎨 Code Style & Guidelines
Language: TypeScript (strict mode enabled)

Linting: ESLint with Airbnb + custom rules

Formatting: Prettier

Folder structure follows feature-based or domain-driven approach.

Use functional components and React Hooks only.

Follow the Single Responsibility Principle (SRP) for components and services.

Use camelCase for variables and functions, PascalCase for components/types.

Keep components stateless when possible; lift state where necessary.

📝 Documentation Guidelines
Document all reusable components with JSDoc/TSDoc-style comments.

Update the README.md with every major feature or setup change.

Use markdown files in /docs or Notion/Confluence for extended docs.

Include:

Feature description

Installation & setup

Usage examples

Known issues or limitations

For APIs, use OpenAPI (Swagger) or Postman collections where applicable.

Optional: generate developer documentation with TypeDoc

Create a new Next.js page based on the following description.

Review this API route for security vulnerabilities. Ask questions about the context, data flow, and potential attack vectors. Be thorough in your investigation.

Create a client component with the following functionality. If writing this as a server component is not possible, explain why.