# 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

# Copilot Instructions

## Code Style
- Use TypeScript strict mode for all new files
- Prefer functional components with hooks over class components
- Use named exports, not default exports

## Libraries
- Use date-fns for date manipulation (not moment.js)
- Use zod for runtime validation
- Prefer fetch over axios for HTTP requests

## Testing
- Write tests using Vitest
- Use Testing Library for component tests
- Aim for integration tests over unit tests

## Conventions
- Use camelCase for variables, PascalCase for components
- Prefix interfaces with I (e.g., IUserProps)
- Keep files under 300 lines; extract if longer