@stevermeister/typescript-strict

# TypeScript Project - Project Guidelines

## Project Overview
TypeScript project with strict configuration and modern best practices.

## TypeScript Configuration

### Strict Settings
```json
{
  "compilerOptions": {
    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "strictBindCallApply": true,
    "strictPropertyInitialization": true,
    "noImplicitThis": true,
    "alwaysStrict": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true
  }
}
```

### Coding Standards
- Use modern TypeScript features
- Implement proper type guards
- Use discriminated unions
- Leverage utility types
- Avoid `any` type
- Use `unknown` instead of `any` when needed
- Implement proper generics
- Use const assertions

### Type Guidelines
- Define interfaces for objects
- Use type aliases for unions
- Implement branded types for validation
- Use mapped types
- Leverage conditional types
- Implement proper function overloads

### Code Quality Tools
- Pre-commit hooks:
  - ESLint with TypeScript plugin
  - Prettier formatting
  - Type checking
  - Unit tests
- Additional:
  - Unused exports check
  - Circular dependency detection
  - Type coverage analysis

### Development Environment

#### Requirements
- Node.js: 20.x
- TypeScript: 5.x
- Package manager: pnpm

### Error Handling
- Use custom error types
- Implement Result types
- Proper async error handling
- Type-safe error messages

### Testing
- Jest with ts-jest
- Type-safe test utilities
- Mock typing
- Coverage: 85%+