> ## Documentation Index
> Fetch the complete documentation index at: https://docs.internal.sevencanyon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Coding standards

> Angular and TypeScript coding conventions

Standards for our Angular frontend.

## Project structure

* TODO: folder structure, feature modules vs. standalone components, and shared/core modules.
* Group code by feature, not by type.

## Components

* Prefer standalone components and the modern Angular APIs.
* Keep components presentational where possible; move logic into services.
* TODO: conventions for inputs/outputs, change detection, and naming.

## TypeScript & linting

* Enforce **ESLint** + **Prettier**; CI fails on violations. TODO: link the config.
* Enable `strict` mode in `tsconfig`. Avoid `any`.

## State & RxJS

* TODO: state management approach (services + signals, NgRx, etc.).
* Always unsubscribe (or use `async` pipe / `takeUntilDestroyed`) to avoid leaks.

## Styling

* TODO: styling approach (component styles, SCSS conventions, design tokens) and naming.

## Testing

* Use **Jasmine/Karma** (or Jest) for unit tests.
* TODO: test file layout, what to test, and minimum coverage expectations.