
Claude Skills by janpereira-dev
github.com/janpereira-devMigrate SSR code from renderModuleFactory to renderModule and related modern platform-server APIs.
Review Angular 21 SSR allowedHosts configuration and proxy trust settings after an Angular 21 upgrade when CommonEngine, AngularAppEngine, AngularNodeAppEngine, or server-side HTTP requests depend on explicit host allowlisting.
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.
Reviews component-scoped keyframes and animation-name assumptions affected by Angular 15 style scoping.
Review component style cleanup behavior after Angular 17 when the app relied on styles leaking after component destruction. Use when overlay, dynamic component, portal, or microfrontend screens depend on leaked styles or when the app needs a controlled compatibility bridge.
Review Angular 20 templates for operator and identifier compatibility when property names such as `in` or `void` collide with JavaScript operators or when parenthesized optional and nullish expressions may throw. Use when template syntax or selector names need safe compatibility cleanup.
Review Angular 21 host binding type checking after an Angular 21 upgrade when components or directives use @HostBinding or host metadata. Use when strict host binding types or inherited host bindings may fail compilation.
Remove obsolete TestBed AOT summary assumptions before or during Angular 14 migration.
Replace TestBed.get with TestBed.inject during Angular 9 modernization and related testing cleanup.
Review Angular 18 test timing, change detection, stabilization, and fixture behavior after an Angular 18 upgrade when tests rely on whenStable, autoDetectChanges, fakeAsync, tick, flush, dialog timing, or Zone stabilization.
Review Angular 19 tests that rely on effect timing, fakeAsync flush behavior, whenStable, tick, flush, or application stabilization after an Angular 19 upgrade. Use when scheduler changes or effect ordering changes can alter test outcomes.
Review Angular 20 tests that rely on effect timing, TestBed.tick, fakeAsync, animation timing, AsyncPipe error reporting, event listener errors, ApplicationRef.tick, or ng-reflect debug attributes after an Angular 20 upgrade.
Review Angular 21 tests that rely on router navigation timing, Zone.js scheduling, or PlatformLocation behavior after an Angular 21 upgrade. Use when router and zone timing changes may alter fixture stability or navigation assertions.
Migrate pre-workspace Angular CLI projects to angular.json workspace format during the Angular 5 to 6 era. Use when older .angular-cli.json configuration still exists.
Review Angular 21 apps that use provideZoneChangeDetection or Zone.js-based change detection. Use when root providers, scheduler behavior, or timing assumptions need explicit validation after an Angular 21 upgrade.
Migrate Zone.js imports to Angular 17-compatible entry points after an Angular 17 upgrade when deep imports from zone.js dist or bundles remain in app or test code.
Migrate Angular zoneless APIs after an Angular 20 upgrade when applications use provideExperimentalZonelessChangeDetection or provideExperimentalCheckNoChangesForDebug. Use when transitioning to supported zoneless or check-no-changes APIs.
Gate Angular 22 compiler, core, forms, HTTP, router, platform-server, and upgrade breaking changes. For Angular 22 projects and 21-to-22 upgrade planning.
Validate the Angular 22 hop after migration and before follow-up modernization. For Angular 22 projects and 21-to-22 upgrade planning.
Inventory Angular 21 project risks before changing dependencies. For Angular 22 projects and 21-to-22 upgrade planning.
Coordinate the bounded Angular 21 to 22 hop without mixing modernization into the dependency upgrade. For Angular 22 projects and 21-to-22 upgrade planning.
Use stable Angular Aria primitives for accessible headless components. For Angular 22 projects and 21-to-22 upgrade planning.
Validate Angular Aria behavior with harnesses, keyboard interaction, and accessibility checks. For Angular 22 projects and 21-to-22 upgrade planning.
Separate accessible interaction contracts from styling and design-system implementation. For Angular 22 projects and 21-to-22 upgrade planning.
Validate modern application builder output, Vite/esbuild behavior, assets, SSR, and production budgets. For Angular 22 projects and 21-to-22 upgrade planning.
Verify Node.js runtime and CI compatibility for the exact Angular 22 target. For Angular 22 projects and 21-to-22 upgrade planning.
Track TSGo readiness without forcing premature migration from supported TypeScript workflows. For Angular 22 projects and 21-to-22 upgrade planning.
Verify TypeScript 6 compatibility and diagnostics from the official Angular compatibility matrix before upgrading. For Angular 22 projects and 21-to-22 upgrade planning.
Identify webpack/devkit builder deprecations and plan the supported application builder path. For Angular 22 projects and 21-to-22 upgrade planning.
Find code that depended on eager change detection, implicit zones, or mutation-driven refreshes. For Angular 22 projects and 21-to-22 upgrade planning.
Control the Angular v22 change detection default shift and preserve Eager behavior only where required. For Angular 22 projects and 21-to-22 upgrade planning.
Remove ComponentFactoryResolver and ComponentFactory usage from dynamic component flows. For Angular 22 projects and 21-to-22 upgrade planning.
Use modern ViewContainerRef.createComponent(Component) or createComponent APIs with explicit injector/projectable nodes. For Angular 22 projects and 21-to-22 upgrade planning.
Detect host directive input/output aliases exposed under incompatible names. For Angular 22 projects and 21-to-22 upgrade planning.
Account for host directive de-duplication and template-match precedence. For Angular 22 projects and 21-to-22 upgrade planning.
Validate Angular bootstrap behavior inside a Shadow Root and CSS/event boundary assumptions. For Angular 22 projects and 21-to-22 upgrade planning.
Use injectAsync for lazy service loading only at safe injector and UX boundaries. For Angular 22 projects and 21-to-22 upgrade planning.
Prefetch injectAsync dependencies with safe triggers such as idle time without hiding failures. For Angular 22 projects and 21-to-22 upgrade planning.
Prevent injectAsync usage where services are not auto-provided or cross the wrong provider boundary. For Angular 22 projects and 21-to-22 upgrade planning.
Decide when @Service() is clearer than @Injectable({ providedIn: root }) and when Injectable remains required. For Angular 22 projects and 21-to-22 upgrade planning.
Audit min/max number validators so numeric contracts are not accidentally passed as strings. For Angular 22 projects and 21-to-22 upgrade planning.
Design async validation with debounce, pending state, reloadValidation, and race-safety. For Angular 22 projects and 21-to-22 upgrade planning.
Bridge Signal Forms with existing CVA and reactive-forms components without a forced rewrite. For Angular 22 projects and 21-to-22 upgrade planning.
Model dynamic collections with signal-backed arrays instead of copying FormArray mental models blindly. For Angular 22 projects and 21-to-22 upgrade planning.
Handle file upload state, validation, and FormData boundaries with Signal Forms. For Angular 22 projects and 21-to-22 upgrade planning.
Adopt Signal Forms for production while preserving validation, submit, accessibility, and migration boundaries. For Angular 22 projects and 21-to-22 upgrade planning.
Verify FetchBackend behavior and migration risk before relying on browser/server fetch semantics. For Angular 22 projects and 21-to-22 upgrade planning.
Migrate HTTP progress handling to explicit upload/download progress options when Angular 22 diagnostics require it. For Angular 22 projects and 21-to-22 upgrade planning.
Remove deprecated JSONP usage and replace it with standard HTTP or server-side integration. For Angular 22 projects and 21-to-22 upgrade planning.
Migrates Angular Material v15 chips and slider components, which have some of the largest API and template changes in the MDC rollout.