Angular

Avoid common Angular mistakes — subscription leaks, change detection, dependency injection, and module organization.

Security Scan

This is an instruction-only Angular best-practices skill whose requested resources and instructions match its description; it contains no installers, no code, and asks for no credentials.

Purpose & Capability

Name/description (Angular best practices) align with the provided files: components.md, rxjs.md, di.md, forms.md, http.md, routing.md and an overview SKILL.md. There are no unrelated environment variables, binaries, or install steps requested.

Instruction Scope

SKILL.md and the included Markdown files contain only guidance about Angular pitfalls and patterns. They do not instruct the agent to read local system files, access credentials, send data to external endpoints, or run arbitrary commands. They stay within the stated purpose.

Install Mechanism

No install spec and no code files are included. Because this is instruction-only, nothing is written to disk or downloaded during install — minimal install risk.

Credentials

The skill declares no required environment variables, credentials, or config paths. There are no requests for unrelated secrets or broad permissions that would be disproportionate to an Angular guidance skill.

Persistence & Privilege

Flags are default (always: false, user-invocable: true, agent invocation allowed). The skill does not request permanent presence or modify other skills/configurations. Autonomous invocation is allowed by default but is not combined with other red flags here.

Assessment

This skill is just static guidance (Markdown) about Angular best practices and does not request credentials or install code — that makes it low-risk and consistent with its description. Before sharing, remember: an agent using this skill might ask you to paste project code or configs to give concrete advice; only share code you are comfortable exposing. If you plan to allow the agent autonomous access to your repositories or environment later, consider limiting that access and reviewing any proposed commands before execution.

When to Use

User needs Angular expertise — component architecture, RxJS patterns, change detection, dependency injection, routing, and forms.

Quick Reference

Topic	File
Components & change detection	components.md
RxJS & subscriptions	rxjs.md
Forms & validation	forms.md
Dependency injection	di.md
Routing & guards	routing.md
HTTP & interceptors	http.md

Common Mistakes

• OnPush with mutated objects won't trigger change detection — always create new reference: {...obj} or [...arr]
• @ViewChild is undefined in constructor/ngOnInit — access in ngAfterViewInit or later
• *ngFor without trackBy re-renders entire list on any change — add trackBy returning stable ID
• Manual subscribe() without unsubscribe leaks memory — use async pipe, takeUntilDestroyed(), or unsubscribe in ngOnDestroy
• HttpClient returns cold Observable — each subscribe() fires new HTTP request
• setTimeout/setInterval outside NgZone — change detection won't run, use NgZone.run() or signals
• Circular DI dependency crashes app — use forwardRef() or restructure services
• ElementRef.nativeElement direct DOM access breaks SSR — use Renderer2 or @defer
• Route params via snapshot miss navigation changes — use paramMap Observable for same-component navigation
• setValue() on FormGroup requires ALL fields — use patchValue() for partial updates