GEMINI.md for TypeScript Projects

# Project: [PROJECT NAME]

## General Instructions
- All code must be TypeScript with strict mode enabled
- Use functional programming patterns where practical
- Prefer composition over inheritance
- Every exported function must have JSDoc documentation
- No `any` types — use `unknown` with type guards instead
- Prefer `const` assertions and template literal types for string unions

## Code Style
- 2 spaces for indentation
- Single quotes for strings
- No semicolons (rely on ASI)
- Prefer arrow functions for callbacks
- Use named exports, not default exports
- File naming: kebab-case (e.g., `user-service.ts`)

## Architecture
- Follow the repository pattern for data access
- Use dependency injection via constructor parameters
- Keep business logic in pure functions separate from I/O
- Error handling: use Result types, not try/catch for expected failures

## Testing
- Test files colocated with source: `*.test.ts`
- Use describe/it blocks with descriptive names
- One assertion per test when possible
- Mock at the boundary, not inside business logic

## Git
- Conventional commits: feat, fix, chore, docs, refactor, test
- One logical change per commit
- PR description must explain WHY, not just WHAT