# 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

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