Angular Enterprise Conventions

Stack declaration (EDIT PER REPO — exact versions mandatory)

Angular <X.Y>, NgRx <X> (<classic|signals> store), RxJS <X.Y>, TypeScript <X.Y>, Component library: <SyncFusion vX / Material vX>, Node <X>. Build: <ng build cmd>. Test: <cmd>. Lint: <cmd>.

State pattern

• Feature state lives in NgRx. Components read via selectors only; write via actions only. No BehaviorSubject-as-store in services for feature state (allowed for purely local, non-shared UI state).
• Effects: side effects only; no state derivation. One effect per concern.
• Action hygiene: [Source] Event naming; no action reuse across features.

Rx rules

• switchMap for replaceable requests, concatMap for ordered writes, mergeMap only with justification comment, exhaustMap for submit buttons.
• Async pipe by default. takeUntilDestroyed for imperative subscriptions.
• No logic in subscribe callbacks beyond dispatch/assignment.

Component library quirks (EDIT PER REPO — this section earns its keep)

Document each landmine once, with workaround, e.g.:

• <Grid>: change detection quirk → call X after data mutation.
• <Dialog>: destroy hooks not fired on route change → pattern Y.
• CDK drag in <context>: known bug → use the workaround directive at <path>, never inline fixes.

Never

• No logic in templates (function calls in bindings).
• No any in new code; unknown + narrowing.
• No direct DOM access; Renderer2/CDK.
• No new deps without approval label.
• Never upgrade the component library as a side effect of another task.

Migration posture

New components standalone; signals for new local state where stack allows; do not convert existing modules opportunistically — migrations are their own tasks with their own plan (see code-archaeology skill).