Adopt standalone components and bootstrap APIs in bounded post-upgrade modernization slices after Angular 19 is stable. Use when reducing NgModule usage incrementally or converting bounded feature areas without mixing the change into a version hop.
Scanned 10/2/2026
npx -y skills add janpereira-dev/ngAutoPilot --skill angular--modernization--angular-standalone-first-adoption-v19 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Angular Modernization Angular Standalone First Adoption V19?
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-standalone-first-ado)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
id: angular.modernization.angular-standalone-first-adoption-v19
name: Angular Standalone First Adoption v19
description: >
Adopt standalone components and bootstrap APIs in bounded post-upgrade modernization slices after Angular 19 is stable. Use when reducing NgModule usage incrementally or converting bounded feature areas without mixing the change into a version hop.
stack:
- Angular
- TypeScript
category: modernization
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
- standalone adoption
- standalone components
- bootstrapApplication
- NgModule reduction
compatibility:
angular:
min: "19"
---
# Angular Standalone First Adoption v19
## Purpose
Adopt standalone components and bootstrap APIs in bounded modernization slices after Angular 19 is stable.
## When to Use
- The app is already on stable Angular 19.
- The team wants to reduce `NgModule` usage 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 stable enough for architectural refactoring.
## Required Inputs
- feature module boundaries
- routing setup
- shared declarations/modules
- bootstrap entry points
- tests for the target slice
## Procedure
1. Select a bounded feature area.
2. Convert leaf components first.
3. Update routing and bootstrap paths.
4. Remove obsolete declarations only after the slice is stable.
5. Validate build, tests, and runtime behavior.
## Do
- Prefer incremental conversion.
- Keep shared module changes small.
- Validate lazy routes and bootstrap paths.
## Do Not
- Do not convert the whole app in one pass.
- Do not mix standalone adoption with version hops.
- Do not remove modules that still provide shared declarations.
## Review Checklist
- [ ] Slice is bounded.
- [ ] Routing still works.
- [ ] Bootstrap still works.
- [ ] Tests pass.
- [ ] Remaining NgModule debt is documented.
## Expected Output
1. Slice converted to standalone.
2. Remaining module dependencies.
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!