# Agent Instructions

## Project Context
Go microservices monorepo using Bazel for builds.

## Build & Test
- Build all: bazel build //...
- Test all: bazel test //...
- Integration tests: docker compose up -d && bazel test //integration/...
- Lint: golangci-lint run ./...

## Code Conventions
- All services follow standard layout in /cmd and /internal
- Use structured logging with slog
- Error wrapping with fmt.Errorf("op: %w", err)
- See @docs/api-style-guide.md for API conventions

## Cross-Repo References
- Shared proto definitions in sourcegraph/proto
- Common Go libraries in sourcegraph/lib

## Security
- Never log sensitive data (tokens, passwords, PII)
- All external inputs must be validated
- Use parameterized queries for database access

# 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
```