# React Component Standards

## Purpose
Ensure consistent React component patterns across the frontend codebase.

## Priority
High

## Instructions
- Use functional components with TypeScript
- Define props interfaces above the component
- Use React.FC only when children are expected
- Colocate styles using CSS Modules (*.module.css)
- Extract hooks into separate files when reused
- Memoize expensive computations with useMemo
- Use React.lazy for route-level code splitting

# Project Instructions

## Architecture
- Monorepo with apps/ and packages/ directories
- Each app is a standalone Next.js deployment
- Shared packages use TypeScript project references

## Code Standards
- TypeScript strict mode everywhere
- Use Zod for runtime validation at API boundaries
- Prefer server components; use "use client" only when needed
- All database queries go through the data-access layer

## Testing
- Unit tests with Vitest for business logic
- Integration tests for API routes
- E2E tests with Playwright for critical user flows

## Deployment
- Preview deployments on every PR
- Production deploys from main branch only
- Environment variables managed via .env.local (never committed)