Angular Router Angular V22 Router Upgrade Contracts

Name: Angular Router Angular V22 Router Upgrade Contracts
Author: janpereira-dev

ASecurity

Use this skill when Angular 22 changes affect route configuration, guards, redirects, route reuse, or navigation behavior.

4 stars

0 votes

0 copies

0 views

Added 10/2/2026

developmenttypescriptgoangularapi

Works with

api

Security Analysis

A100/100

Scanned 10/2/2026

npx -y skills add janpereira-dev/ngAutoPilot --skill angular--router--angular-v22-router-upgrade-contracts --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Angular Router Angular V22 Router Upgrade Contracts?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Angular Router Angular V22 Router Upgrade Contracts

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-angular-router-angular-v22-router-upgrade-contract/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-angular-router-angular-v22-router-upgrade-contract)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

Files

SKILL.md

---
id: angular.router.angular-v22-router-upgrade-contracts
name: Angular v22 Router Upgrade Contracts
description: >
  Use this skill when Angular 22 changes affect route configuration, guards, redirects, route reuse, or navigation behavior.
stack:
  - Angular
  - TypeScript
category: router
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - router
  - provideRouter
  - CanMatch
  - paramsInheritanceStrategy
  - route cleanup
compatibility:
  angular:
    min: "22"
---

# Angular v22 Router Upgrade Contracts

## Purpose

Use this skill when Angular 22 changes affect route configuration, guards, redirects, route reuse, or navigation behavior.

## When to Use

Use this skill when:

- The bootstrap router config needs a v22 update.
- Guards, redirects, or route reuse rely on older contracts.
- The app depends on route parameter inheritance or navigation behavior.

## When Not to Use

Do not use this skill when:

- The issue is only a template syntax problem.
- No route config or navigation contract changed.
- The task is already covered by a more specific routing satellite.

## Required Inputs

- bootstrap route config
- guards and redirects
- route reuse strategy
- router tests

## Procedure

1. Review the router bootstrap and remove deprecated config patterns.
2. Update guard signatures and route parameter assumptions.
3. Check route reuse and cleanup behavior if cached views are involved.

## Do

- Use the supported router configuration path.
- Keep guard contracts explicit.
- Validate the route behavior after changing defaults.

## Do Not

- Do not keep deprecated route helpers in new code.
- Do not assume the old route parameter inheritance still applies.
- Do not ignore cached-route cleanup when memory matters.

## Review Checklist

- [ ] Router config uses the supported API.
- [ ] Guard signatures still compile.
- [ ] Route tests pass with the new defaults.

## Expected Output

1. A router contract summary.
2. The changed defaults or APIs.
3. Validation evidence.

Attribution

janpereira-dev

View source See grades on GitHub More from janpereira-dev →

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

--- id: angular.router.angular-v22-router-upgrade-contracts name: Angular v22 Router Upgrade Contracts description: > Use this skill when Angular 22 changes affect route configuration, guards, redirects, route reuse, or navigation behavior. stack: - Angular - TypeScript category: router status: stable version: 0.10.0 owner: NgAutoPilot triggers: - router - provideRouter - CanMatch - paramsInheritanceStrategy - route cleanup compatibility: angular: min: "22" --- # Angular v22 Router Upgrade Contracts ## Purpose Use this skill when Angular 22 changes affect route configuration, guards, redirects, route reuse, or navigation behavior. ## When to Use Use this skill when: - The bootstrap router config needs a v22 update. - Guards, redirects, or route reuse rely on older contracts. - The app depends on route parameter inheritance or navigation behavior. ## When Not to Use Do not use this skill when: - The issue is only a template syntax problem. - No route config or navigation contract changed. - The task is already covered by a more specific routing satellite. ## Required Inputs - bootstrap route config - guards and redirects - route reuse strategy - router tests ## Procedure 1. Review the router bootstrap and remove deprecated config patterns. 2. Update guard signatures and route parameter assumptions. 3. Check route reuse and cleanup behavior if cached views are involved. ## Do - Use the supported router configuration path. - Keep guard contracts explicit. - Validate the route behavior after changing defaults. ## Do Not - Do not keep deprecated route helpers in new code. - Do not assume the old route parameter inheritance still applies. - Do not ignore cached-route cleanup when memory matters. ## Review Checklist - [ ] Router config uses the supported API. - [ ] Guard signatures still compile. - [ ] Route tests pass with the new defaults. ## Expected Output 1. A router contract summary. 2. The changed defaults or APIs. 3. Validation evidence.