Configure Angular Router with lazy-loaded routes, functional guards, and component input binding. Use when defining routes, lazy-loading features, creating route guards, or setting up resolvers. (triggers: *.routes.ts, angular router, loadComponent, canActivate, resolver)
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
loadComponent (standalone) or loadChildren (route file) for every feature route.See routing patterns for lazy loading and guard examples.
CanActivateFn) instead of deprecated class-based guards.See routing patterns for functional guard implementation.
withComponentInputBinding() in provideRouter(routes, withComponentInputBinding()).input.required<string>() in components — Angular auto-maps route params, query params, and resolve data.ResolveFn<T> to pre-fetch critical data before navigation.TitleStrategy or use title: 'Dashboard' in route data.loadComponent or loadChildren for all feature routes.19a1140
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.