Software Development Skills

Upgrade an Angular application from Angular 15.x to Angular 16.x using a controlled major-hop process. Use when the project is ready to move from Angular 15 to Angular 16 and needs explicit handling for ngcc removal, View Engine library compatibility, SSR/TransferState changes, dynamic component creation, router typing, and build output changes.

Performs the Angular 9.x to Angular 10.2.x major-hop upgrade in a bounded, critical compatibility slice with Ivy, DI, Material, TypeScript, and validation-gate checks.

Reviews Angular component testing patterns for Angular 17+ projects, focusing on modern template syntax awareness, stable component contracts, and contract-focused tests.

Reviews, designs, and refactors Angular dependency injection for services, providers, injectors, InjectionToken, inject(), testing overrides, standalone apps, NgModules, SSR, lazy loading, and provider scopes.

Assesses Angular enterprise training readiness by mapping current team capability, version awareness, architecture gaps, testing maturity, and safe follow-up skill routing.

Configures and governs Angular Extended Diagnostics with a progressive severity policy so template correctness issues are surfaced without turning upgrades into brittle compile blockers.

Reviews iframe bindings and host bindings for Angular 15-era security and behavior hardening.

Convert AngularJS directives into Angular components or directives as appropriate. Use when legacy directive behavior blocks migration or makes the DOM contract unstable.

Move routing from AngularJS to a hybrid Angular and AngularJS setup when both frameworks must coexist during migration. Use when route ownership is split and navigation needs explicit bridge handling.

Inventory AngularJS applications before migration to Angular. Use when the repo still contains controllers, scopes, directives, filters, services, routes, templates, or ngUpgrade artifacts that must be mapped before a hybrid or full Angular migration.

Optimizes Angular list rendering by using stable identity tracking with trackBy for legacy templates or @for track for modern Angular.

Reviews Angular Material v15 theme, density, and typography changes, including custom styles, mixins, and MDC class name impacts.

Migrate Angular SSR code from renderModuleFactory to renderModule. Use when server rendering still depends on the older factory-based API.

Build a compact review packet for Angular PRs that highlights architecture, risk, validation, and rollback points for human or agent review.

Reviews Angular Router behavior changes in Angular 15 around outlet timing, route matching, and navigation assumptions.

Reviews Angular Signals state patterns for Angular 16+ projects, focusing on signal, computed, and effect usage, local state boundaries, and RxJS coexistence.

Reviews and refactors Angular services so each service has one bounded responsibility such as API access, state ownership, mapping, validation, permissions, or feature orchestration.

Review Angular 19 standalone-by-default compatibility for NgModule-heavy apps after an Angular 19 upgrade when declarations, imports, shared modules, or library modules still rely on NgModule wiring. Use when declarations need explicit standalone: false or when module-heavy architecture must remain temporarily compatible.

Update service worker code to Angular v13 SwUpdate APIs and behavior. Use when update lifecycle handling still depends on deprecated properties or events.

Replace TestBed.get with TestBed.inject in Angular tests. Use when older tests still rely on TestBed.get and need a small, controlled modernization step.

Validate Angular 20 moduleResolution bundler compatibility after an Angular 20 upgrade when tsconfig inheritance, secondary entry points, custom builders, or monorepo tooling may break under bundler resolution.

Use when Angular 22 changes affect component creation, selector rules, host directives, or default component behavior.

Use CSS :has() and :not(:has()) to adapt layout to child content without JavaScript, Angular bindings, or class toggles.

Adopt Angular directive composition in bounded slices after the app is stable, using it to reduce inheritance-heavy patterns and share behavior without mixing the change into upgrade work.