Skip to content
Back to skills

Angular Architecture Control Flow Adoption

ASecurity

Adopt Angular control flow syntax in bounded post-upgrade modernization slices to replace structural directive boilerplate with `@if`, `@for`, and `@switch` without mixing the change into an Angular version hop.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 2, 2026
developmenttypescriptgoangularexpress

Security analysis

A100/100

Scanned October 2, 2026

npx -y skills add janpereira-dev/ngAutoPilot --skill angular--architecture--control-flow-adoption --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Angular Architecture Control Flow Adoption?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Angular  Architecture  Control Flow Adoption
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/janpereira-dev-angular-architecture-control-flow-adoption-ngautopilot/badge)](https://www.skillsdirectory.com/skills/janpereira-dev-angular-architecture-control-flow-adoption-ngautopilot)

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

Download with Pro
SKILL.md
---
id: angular.architecture.control-flow-adoption
name: Control Flow Adoption
description: >
  Adopt Angular control flow syntax in bounded post-upgrade modernization slices to replace structural directive boilerplate with `@if`, `@for`, and `@switch` without mixing the change into an Angular version hop.
stack:
  - Angular
  - TypeScript
category: architecture
status: stable
version: 0.10.0
owner: NgAutoPilot
triggers:
  - control flow
  - "@if"
  - "@for"
  - "@switch"
  - structural directives modernization
compatibility:
  angular:
    min: "17"
---

# Control Flow Adoption

## Purpose

Adopt Angular control flow syntax 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 control flow.
- The team wants to replace structural directive boilerplate 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 the new syntax.

## Required Inputs

- templates using `*ngIf`
- templates using `*ngFor`
- templates using `*ngSwitch`
- shared UI fragments
- test coverage for the target slice

## Procedure

1. Select a bounded feature area.
2. Replace one structural directive family at a time.
3. Keep expressions and tracking logic explicit.
4. Validate templates, accessibility, and tests.
5. Stop after the slice is stable.

## Do

- Prefer incremental conversion.
- Keep `track` expressions deliberate.
- Validate empty-state and fallback rendering.

## Do Not

- Do not convert the whole app in one pass.
- Do not mix control flow adoption with upgrade hops.
- Do not change business logic while changing template syntax.

## Review Checklist

- [ ] Slice is bounded.
- [ ] Rendering is equivalent or intentionally changed.
- [ ] Tests pass.
- [ ] Remaining template debt is documented.

## Expected Output

1. Slice converted to control flow.
2. Remaining structural directives.
3. Test result.
4. Follow-up list.

## Exit Criteria

- Adoption is incremental.
- The next slice is clear.

Attribution

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

Loading comments…