Claude Skills by janpereira-dev

Reviews Angular-inheriting classes and constructor-based DI patterns for Angular 15 hardening and decorator requirements.

Clean up Angular 20 dependency injection code that still relies on InjectFlags, TestBed.get, or untyped Injector.get usage after an Angular 20 upgrade. Use when strict ProviderToken typing or injection options must be made explicit.

Reviews custom ControlValueAccessor implementations for Angular 15 setDisabledState behavior and form integration risks.

Remove template write expressions from Angular forms that use [(ngModel)] after an Angular 18 upgrade. Use when templates assign to properties inside two-way bindings or otherwise combine writes with ngModel expressions.

Migrates Angular reactive forms to typed forms in bounded slices, or uses an untyped bridge when risk, scale, or test coverage make a full typed migration unsafe.

Use untyped reactive forms as a compatibility bridge when typed forms are not yet practical. Apply only as a temporary step before typed forms migration.

Review Angular 21 apps for custom FormArray or formArray directive and input naming conflicts after the upgrade. Use when custom directives or inputs collide with Angular reactive forms APIs.

Performs the Angular 10.x to Angular 11.x major-hop upgrade in a bounded, compatibility-aware slice with router, forms, TypeScript, Material, Universal, and validation-gate checks.

Performs the Angular 11.x to Angular 12.x major-hop upgrade in a bounded, high-control slice with Node, TypeScript, router, forms, i18n, Universal, service worker, and validation-gate checks.

Performs the Angular 12.x to Angular 13.x major-hop upgrade in a bounded, hard-boundary slice with IE11, Ivy, View Engine, libraries, Material, router, Universal, and validation-gate checks.

Performs the Angular 13.x to Angular 14.x major-hop upgrade in a bounded, high-control slice with Typed Forms strategy, Material/CDK, Router, tests, and validation-gate checks.

Performs the Angular 14.x to Angular 15.x major-hop upgrade in a bounded, compatibility-aware slice with Material, router, forms, security, styles, and validation-gate checks.

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.

Upgrade an Angular application from Angular 16.x to Angular 17.x using a controlled major-hop process. Use when the project is ready to move from Angular 16 to Angular 17 and needs explicit handling for changelog baseline review, Node.js/TypeScript/Zone.js requirements, router configuration, hydration, Signals, destroyed component styles, NgSwitch, Zone.js imports, and dynamic component behavior.

Upgrade an Angular application from Angular 17.x to Angular 18.x using a controlled major-hop process. Use when the project is ready to move from Angular 17 to Angular 18 and needs explicit handling for Node.js/TypeScript requirements, tests, SSR/platform-server, TransferState, HTTP transfer cache, router redirects, forms, OnPush, and change detection behavior.

Upgrade an Angular application from Angular 18.x to Angular 19.x using a controlled major-hop process. Use when the project is ready to move from Angular 18 to Angular 19 and needs explicit handling for standalone defaults, TypeScript 5.5+, tests, router error handling, dynamic component projection, localize builder changes, signals/effects timing, and NgModule compatibility.

Upgrade an Angular application from Angular 19.x to Angular 20.x using a controlled major-hop process. Use when the project is ready to move from Angular 19 to Angular 20 and needs explicit handling for TypeScript 5.8+, moduleResolution bundler, testing behavior, DI deprecations, router redirects, Resource API changes, template operator conflicts, ng-reflect cleanup, and SSR/module-resolution risk.

Performs the Angular 2.x to Angular 4.x major-hop upgrade in a bounded, version-aware slice with dependency alignment, code adjustments, and validation.

Upgrade an Angular application from Angular 20.x to Angular 21.x using a controlled major-hop process. Use when the project is ready to move from Angular 20 to Angular 21 and needs explicit handling for TypeScript 5.9+, Node.js compatibility, zone change detection configuration, SSR security, host binding checks, router and forms changes, dynamic component migration, and removed legacy APIs.

Performs the Angular 4.x to Angular 5.2.x major-hop upgrade in a bounded, version-aware slice with dependency alignment, compatibility checks, and validation.

Performs the Angular 5.x to Angular 6.1.x major-hop upgrade in a bounded, version-aware slice with CLI migration, RxJS planning, and validation.

Performs the Angular 6.x to Angular 7.2.x major-hop upgrade in a bounded, version-aware slice with CLI, RxJS, forms, Material, and validation-gate checks.

Performs the Angular 7.x to Angular 8.2.x major-hop upgrade in a bounded, version-aware slice with CLI, Material, styles, lazy loading, and validation-gate checks.

Performs the Angular 8.x to Angular 9.1.x major-hop upgrade in a bounded, critical compatibility slice with Ivy, libraries, Material, and validation-gate checks.

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.

Review Angular HTTP transfer cache behavior after Angular 18 when SSR or hydration apps cache authenticated requests or rely on transfer cache semantics. Use when auth headers, cookies, or user-scoped responses may affect cache safety.

Migrate from Angular HttpModule and Http to HttpClientModule and HttpClient during the Angular 5 to 6 era. Use when legacy HTTP APIs block modern Angular usage.

Remove AngularJS upgrade adapter usage after an Angular 21 upgrade when hybrid applications still reference UpgradeAdapter or legacy upgrade APIs. Use when the project still combines AngularJS and Angular and needs an explicit compatibility cleanup.

Evaluate hydration and SSR behavior after Angular 17 upgrades when the app uses provideClientHydration, SSR, prerender, or DOM reuse-sensitive widgets. Use when hydration mismatches, server render errors, or third-party DOM manipulation may affect runtime behavior.

Migrate Angular applications to the v9 localize tooling and $localize runtime. Use when i18n build or runtime configuration still depends on older extraction or localization setup.

Validate Angular projects for Ivy default mode compatibility. Use when entryComponents, View Engine assumptions, or library compatibility can block Angular 9 adoption.

Block Angular 13 upgrades when Ivy is disabled or View Engine-only dependencies remain. Use when the app must be confirmed Ivy-only before moving forward.

Audit Angular libraries for ngcc and View Engine compatibility before Angular 16. Use when the project is upgrading from Angular 15 to Angular 16 or when a library may still require compatibility compilation, View Engine metadata, or postinstall ngcc scripts.

Audit Angular libraries for View Engine compatibility before Angular 13 or later. Use when package dependencies may still require ngcc or old metadata formats.

Migrate Angular localize builder configuration after Angular 19 when angular.json uses the @angular/localize builder and the project needs the name-to-project option change. Use when localization builds rely on builder options or extraction behavior.

Remove Angular NgModuleFactory usage after an Angular 21 upgrade when dynamic module loading, plugin systems, or legacy loaders still depend on NgModuleFactory. Use when replacing factory-based module creation with supported APIs.

Migrate Angular resource and rxResource code to the Angular 20 API shape after an Angular 20 upgrade when applications use resource, rxResource, ResourceStatus, request, loader, params, or stream. Use when resource-based state or SSR data loading needs explicit cleanup.

Replace Angular router string-based lazy route syntax with dynamic imports. Use when older loadChildren patterns still exist and block modern Angular routing.

Migrate Angular Router error handling after Angular 19 when routing code uses Router.errorHandler, custom navigation error handling, guards, resolvers, or route readers that depend on navigation failure behavior. Use when redirect/error handling needs explicit review.

Review Angular Router redirect behavior after Angular 18 when guards, resolvers, or route metadata rely on UrlTree redirects, Route.redirectTo, or RedirectCommand. Use when history behavior, replaceUrl, or route readers need an explicit compatibility review.

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

Migrate Angular Router code to v17 public APIs after an Angular 17 upgrade when the app uses advanced router configuration, custom URL handling, redirects, or loadComponent route inheritance. Use when router internals are mutated directly or when malformed URI handling, absolute redirects, or route inheritance need explicit review.

Clean up legacy Angular router lazy route syntax before or during Angular 13 migration.

Review router resolvers for first-emission behavior before or during Angular 14 migration. Use when multi-emission observables or delayed resolver completion affect navigation.

Validate Angular 20 router guards, redirects, and route configuration after an Angular 20 upgrade when `redirectTo`, `canMatch`, `RedirectFn`, or readonly command arrays may affect routing behavior.

Bridge Angular projects from RxJS 5 to RxJS 6, including compat package review, operator changes, and import cleanup.

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

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

Replace Angular Signals mutate usage with update-based immutable patterns after an Angular 17 upgrade when signal state changes are still written with in-place mutation. Use when a bounded slice uses signals and needs a controlled refactor.

Migrate Angular SSR and platform-server code to Angular 18 after an Angular 18 upgrade when the app uses Universal, prerender, TransferState, platform-server bootstrapping, or server URL behavior.