# 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

# 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