# 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

# Project Rules

## Overview
E-commerce platform built with Go microservices and React frontend.
All services communicate via gRPC with Protocol Buffers.

## Go Services
- Follow standard Go project layout (cmd/, internal/, pkg/)
- Use structured logging with slog (not log or fmt.Println)
- Error handling: always wrap errors with fmt.Errorf("%w", err)
- Database access through repository pattern in internal/repo/
- All public functions must have godoc comments

## API Design
- Proto files live in proto/ directory with buf for linting
- Use field masks for partial updates
- Pagination via cursor-based tokens, not offset

## Testing
- Table-driven tests for all business logic
- Use testcontainers-go for integration tests
- Minimum 80% coverage on internal/ packages
- Mock external services with gomock interfaces

## Do Not
- Use global variables or init() functions
- Import internal packages across service boundaries
- Commit generated .pb.go files (CI generates them)