<< All versions
Skill v1.0.2
currentAutomated scan100/100janpereira-dev/ngautopilot/angular-components-angular-v22-component-contracts
+4 new
──Details
PublishedNovember 5, 2026 at 04:32 AM
Content Hashsha256:4dd6954a54ae38ff...
Git SHAb7faf9d17097
Bump Typepatch
──Files
Files (1 file, 2.0 KB)
SKILL.md2.0 KBactive
SKILL.md · 72 lines · 2.0 KB
name: angular-components-angular-v22-component-contracts description: "Use this skill when Angular 22 changes affect component creation, selector rules, host directives, or default component behavior." license: MIT metadata: version: "1.0.2" ngautopilot-id: "angular.components.angular-v22-component-contracts" ngautopilot-source: "skills/angular/components/angular-v22-component-contracts/SKILL.md" ngautopilot-version: "0.11.0"
Angular v22 Component Contracts
Purpose
Use this skill when Angular 22 changes affect component creation, selector rules, host directives, or default component behavior.
When to Use
Use this skill when:
- Dynamic components use APIs that changed or were removed in v22.
- Multiple selectors or host directives may now collide.
- Component change detection behavior needs to stay explicit.
When Not to Use
Do not use this skill when:
- The issue is only template syntax.
- The task is only about routing or SSR.
- A more specific dynamic-component skill is the better match.
Required Inputs
- dynamic component code
- selectors
- host directives
- change detection expectations
Procedure
- Replace removed component creation APIs with the supported v22 path.
- Normalize selectors so the compiler no longer sees collisions.
- Review host-directive exposure and any default change-detection assumptions.
- Validate dynamic component behavior with targeted tests.
Do
- Keep component creation explicit.
- Prefer one clear selector per component contract.
- Validate lifecycle behavior after the migration.
Do Not
- Do not keep removed factory APIs in the codebase.
- Do not ignore compile-time selector errors.
- Do not rely on an implicit change-detection default without confirming it.
Review Checklist
- [ ] Removed component APIs are gone.
- [ ] Selectors are unambiguous.
- [ ] Component tests still pass.
Expected Output
- A component-contract summary.
- The removed API replacement.
- Remaining component risks.