---
description: 'What these instructions enforce'
applyTo: '**/*.js, **/*.ts'
---

# Instruction Title

Detailed guidelines and standards...

---
description: 'Angular-specific coding standards and best practices'
applyTo: '**/*.ts, **/*.html, **/*.scss, **/*.css'
---

# Angular Development Instructions

Instructions for generating high-quality Angular applications with TypeScript,
using Angular Signals for state management, adhering to Angular best practices
as outlined at https://angular.dev.

## Project Context
- Latest Angular version (use standalone components by default)
- TypeScript for type safety
- Angular CLI for project setup and scaffolding
- Follow Angular Style Guide (https://angular.dev/style-guide)
- Use Angular Material or other modern UI libraries for consistent styling

## Architecture
- Use standalone components unless modules are explicitly required
- Organize code by standalone feature modules or domains for scalability
- Implement lazy loading for feature modules to optimize performance
- Use Angular's built-in dependency injection system effectively
- Structure components with clear separation (smart vs. presentational)

## TypeScript
- Enable strict mode in `tsconfig.json` for type safety
- Define clear interfaces and types for components, services, and models
- Use type guards and union types for robust type checking
- Implement proper error handling with RxJS operators (e.g., `catchError`)
- Use typed forms (e.g., `FormGroup`, `FormControl`) for reactive forms

## State Management
- Use Angular Signals for reactive state management in components/services
- Leverage `signal()`, `computed()`, and `effect()` for reactive updates
- Use writable signals for mutable state and computed signals for derived state
- Handle loading and error states with signals and proper UI feedback
- Use Angular's `AsyncPipe` to handle observables in templates

---
description: 'Testing standards and best practices'
applyTo: '**/*.test.ts, **/*.test.tsx, **/*.spec.ts'
---

# Testing Instructions

## Test Structure

- Use `describe` blocks to group related tests
- One assertion per test when possible
- Clear test names: "should [expected behavior] when [condition]"

## Example Test Structure

Use describe blocks to organize tests by component and scenario.
Within each describe block, write focused it() statements.
Follow the Arrange-Act-Assert pattern for test clarity.

## Coverage Requirements

- Minimum 80% code coverage
- 100% coverage for critical paths
- Test both happy path and error cases

---
description: 'API service layer standards'
applyTo: '**/services/**/*.ts, **/api/**/*.ts'
---

# API Service Instructions

## Service Structure

Create a typed ApiResponse interface with data, optional error, and status fields.
Build ApiService classes with a baseUrl property and generic get/post methods.
Use TypeScript generics to ensure type safety for API responses.

## Error Handling

- Always wrap API calls in try-catch
- Return typed error responses
- Log errors with context
- Retry failed requests (max 3 attempts)

## Best Practices

- Use TypeScript generics for type-safe responses
- Implement request/response interceptors
- Add timeout for all requests (30s default)
- Cache GET requests where appropriate

---
description: 'Database schema and migration standards'
applyTo: '**/migrations/**/*.sql, **/schema/**/*.sql'
---

# Database Schema Instructions

## Naming Conventions

- Tables: plural, snake_case (`user_profiles`)
- Columns: snake_case (`created_at`)
- Primary keys: `id` (UUID)
- Foreign keys: `{table}_id` (`user_id`)
- Indexes: `idx_{table}_{column}`

## Required Columns

Every table must include:
- id UUID PRIMARY KEY DEFAULT gen_random_uuid()
- created_at TIMESTAMP DEFAULT NOW()
- updated_at TIMESTAMP DEFAULT NOW()

## Migration Standards

- One migration per logical change
- Include both `up` and `down` migrations
- Test migrations on sample data
- Never modify existing migrations

.github/instructions/
  ├── react-components.instructions.md
  ├── testing.instructions.md
  ├── api-services.instructions.md
  └── database-schema.instructions.md

instructions/
  ├── company-coding-standards.instructions.md
  ├── security-requirements.instructions.md
  └── accessibility-standards.instructions.md