ngautopilot-angular-9-12
Angular 9 to 12 era gateway for Ivy adoption, lazy-route modernization, localize, TestBed changes, IE11 governance, and bounded major hops.
SKILL.md.agents/skills/ngautopilot-angular-9-12/SKILL.md
GitHubAngular 9-12
Purpose
Angular 9 to 12 era gateway for Ivy adoption, lazy-route modernization, localize, TestBed changes, IE11 governance, and bounded major hops.
This is a curated NgAutoPilot gateway skill for npx skills, Pi, and other broad discovery surfaces. It deliberately presents one capability boundary instead of hundreds of canonical micro-skills.
This gateway covers Angular 9-12. Angular 3 was never released; the historical 2-5 gateway therefore routes 2→4→5.
Workflow
- Inspect the receiving repository before proposing changes.
- Detect Angular, Node.js, TypeScript, RxJS, package-manager, test, and workspace evidence relevant to the task.
- Read
references/index.mdand choose the narrowest route for the task. - For Angular upgrades, move one supported major hop at a time and keep modernization separate until the hop is stable.
- Apply compatibility and risk gates before editing.
- Make the smallest reversible change.
- Run the receiving repository's real validation commands and report evidence, failures, and residual risk.
Routes represented by this gateway
Source packs:
ngautopilot-angular-8-to-9ngautopilot-angular-9-to-10ngautopilot-angular-10-to-11ngautopilot-angular-11-to-12
Every canonical procedure selected by this gateway is included locally under references/skills/. No second installer is required. External source citations and optional repository documentation links provide further reading; the procedures themselves are installed files.
Progressive disclosure
- Start with
references/index.md; it links to the exact localreferences/skills/<id>/procedure.mdneeded. - Those procedures are full copies of the canonical source, not pointers to another repository.
- Activate only the single appropriate procedure or Angular major hop; never load all referenced files into context.
- If the route requires a specialist, consult
references/agents/andreferences/agents/prompts/when present. - Do not load unrelated capability families merely because they are installed.
Safety
- Do not guess framework compatibility.
- Do not install dependencies unless the task requires them and the receiving project approves the change.
- Do not mix unrelated refactors with upgrade work.
- Do not claim validation that was not executed.
- Treat generated guidance as assistance, not as a replacement for tests, review, or security gates.
Expected output
Return the selected route, compatibility/risk notes, changed files, validation commands and results, and any remaining blockers.