Adopt Angular signals in bounded post-upgrade modernization slices to replace or complement local component state, derived state, and reactive glue without mixing the change into an Angular version hop.
Scanned 10/2/2026
Skills Directorynpx -y skills add janpereira-dev/ngAutoPilot --skill angular-architecture-signals-adoption --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Angular Architecture Signals Adoption?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/janpereira-dev-angular-architecture-signals-adoption)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: angular-architecture-signals-adoption
description: "Adopt Angular signals in bounded post-upgrade modernization slices to replace or complement local component state, derived state, and reactive glue without mixing the change into an Angular version hop."
license: MIT
metadata:
ngautopilot-id: "angular.architecture.signals-adoption"
ngautopilot-source: "skills/angular/architecture/signals-adoption/SKILL.md"
ngautopilot-version: "0.10.0"
---
# Signals Adoption
## Purpose
Adopt Angular signals in bounded modernization slices after the app is stable on a compatible Angular version.
## When to Use
- The app is already on a stable Angular version that supports signals.
- The team wants to modernize local component state incrementally.
- The change is architectural modernization, not a version upgrade.
## When Not to Use
- The app is still in the middle of a major Angular hop.
- The target slice is not well tested.
- The app is not on a version that supports signals.
## Required Inputs
- local component state
- derived state usage
- reactive glue code
- computed values and effects
- tests for the target slice
## Procedure
1. Select a bounded feature area.
2. Identify state that is local and stable.
3. Replace the smallest safe slice with signals.
4. Keep interop with existing observables explicit.
5. Validate rendering, effects, and tests.
## Do
- Prefer incremental conversion.
- Keep effects narrow and intentional.
- Validate change detection and UI updates.
## Do Not
- Do not convert the whole app in one pass.
- Do not mix signals adoption with upgrade hops.
- Do not replace service-level reactive architecture without a plan.
## Review Checklist
- [ ] Slice is bounded.
- [ ] State updates are correct.
- [ ] Tests pass.
- [ ] Remaining reactive debt is documented.
## Expected Output
1. Slice converted to signals.
2. Remaining observable/state 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!
