# Project Conventions

## Language
- TypeScript strict mode, no `any` types
- Prefer const over let, never use var
- Use template literals over string concatenation

## Architecture
- Feature-based folder structure under src/features/
- Each feature exports through an index.ts barrel file
- Shared utilities go in src/lib/

## Error Handling
- Use Result<T, E> pattern for expected failures
- Throw only for programmer errors
- Always log errors with structured context

## Testing
- Colocate tests next to source files (*.test.ts)
- Use factories for test data, not fixtures
- Integration tests in __tests__/ directories

# AGENTS.md

## Project Overview

This is a Next.js 14 e-commerce application using the App Router,
Server Components, and Drizzle ORM with PostgreSQL.

## Code Conventions

- Use TypeScript strict mode throughout
- Prefer Server Components; use "use client" only when necessary
- Name files with kebab-case: `product-card.tsx`, not `ProductCard.tsx`
- Co-locate tests: `product-card.test.tsx` next to `product-card.tsx`

## Architecture

- `app/`           — Next.js App Router pages and layouts
- `components/`    — Shared UI components
- `lib/`           — Utilities, database client, auth helpers
- `actions/`       — Server Actions for mutations

## Testing

- Use Vitest for unit tests, Playwright for E2E
- Mock database calls using `lib/test-utils.ts` helpers
- Every new component needs at least one test

## Build Commands

```bash
pnpm dev          # Start dev server
pnpm build        # Production build
pnpm test         # Run Vitest
pnpm test:e2e     # Run Playwright
pnpm lint         # ESLint check
```