Adopt Angular deferrable views in bounded post-upgrade modernization slices after Angular 18 is stable. Use when improving render timing, route splitting, and loading behavior with @defer without mixing the change into a version hop.
Scanned 10/2/2026
npx -y skills add janpereira-dev/ngAutoPilot --skill angular--modernization--angular-defer-views-v18-adoption --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Angular Modernization Angular Defer Views V18 Adoption?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/janpereira-dev-angular-modernization-angular-defer-views-v18-adop)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
id: angular.modernization.angular-defer-views-v18-adoption
name: Angular Defer Views v18 Adoption
description: >
Adopt Angular deferrable views in bounded post-upgrade modernization slices after Angular 18 is stable. Use when improving render timing, route splitting, and loading behavior with @defer without mixing the change into a version hop.
stack:
- Angular
- TypeScript
category: modernization
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
- defer views
- "@defer"
- deferrable views
- lazy rendering modernization
compatibility:
angular:
min: "18"
---
# Angular Defer Views v18 Adoption
## Purpose
Adopt Angular deferrable views in bounded modernization slices after Angular 18 is stable.
## When to Use
- The app is already on stable Angular 18.
- The team wants to improve render timing or split heavy views incrementally.
- The change is modernization, not a version upgrade.
## When Not to Use
- The app is still in a version hop.
- The app is not on a version that supports `@defer`.
## Required Inputs
- heavy templates
- route boundaries
- loading and placeholder behavior
- tests for the target slice
## Procedure
1. Select a bounded feature area.
2. Introduce `@defer` in the smallest safe slice.
3. Keep placeholders, loading states, and fallback content explicit.
4. Validate rendering, timing, and tests.
## Do
- Prefer incremental conversion.
- Keep loading states intentional.
- Validate empty, loading, and error paths.
## Do Not
- Do not split the whole app in one pass.
- Do not mix this with a version hop.
- Do not hide loading regressions behind a smaller diff.
## Review Checklist
- [ ] Slice is bounded.
- [ ] Loading behavior is correct.
- [ ] Tests pass.
- [ ] Remaining loading debt is documented.
## Expected Output
1. Slice converted to `@defer`.
2. Remaining view debt.
3. Test result.
4. Follow-up list.
## Exit Criteria
- Adoption is incremental.
- The next slice is clear.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!