Angular's Official Agent Skills Helps AI Coding Tools Write Modern Angular

Google's Angular team has released a repository of Agent Skills that teach AI coding tools to write modern Angular v20 code instead of outdated patterns. The skills, designed for tools like Gemini CLI, enforce current conventions such as Signals and standalone components while avoiding deprecated syntax like `*ngIf` and `standalone: true`. The release addresses a common problem where AI coding agents suggest obsolete Angular patterns due to lack of current framework context.

Google's Angular team has published angular/skills https://github.com/angular/skills , a dedicated repository of Agent Skills that teach AI coding agents to write modern, idiomatic Angular instead of the outdated patterns that models still reach for by default. Agent Skills are structured, domain-specific instruction files, an open format introduced by Anthropic, that load on demand to give an agent expertise for a particular task. The Angular collection currently ships two skills. The angular-developer skill generates code and provides architectural guidance across reactivity signals , linkedSignal , resource , forms, dependency injection, routing, SSR, accessibility, animations, styling, and testing, while a ngular-new-app scaffolds a fresh application using the Angular CLI. In practice the angular-developer skill enforces v20 conventions, preferring @if over ngIf and dropping the now redundant standalone: true flag. They are designed for agentic tools such as Gemini CLI and Antigravity, and the official documentation https://angular.dev/ai/agent-skills notes they keep an agent in sync with conventions like Signals and standalone components. The repository is a published snapshot rather than the source of truth, since contributions are made in the main angular/angular https://github.com/angular/angular repository and mirrored out automatically. The motivation is well documented. As Brandon Roberts explained https://dev.to/brandontroberts/angular-skills-agent-skills-for-ai-assisted-development-3jgg , coding agents "often suggest outdated Angular patterns, NgModules, @Input decorators, ngIf, and constructor injection" because they lack current context. Installation uses the community skills CLI: npx skills add <https://github.com/angular/skills The release builds on community work, and Agent Skills have, as Angular newsletter author Gérôme Grignon observed https://www.linkedin.com/pulse/8-official-angular-agent-skills-g%C3%A9r%C3%B4me-grignon-ddwwe , become "the most popular" way to feed framework context to LLMs. The most widely used predecessor was Roberts' analogjs/angular-skills https://github.com/analogjs/angular-skills . Competing approaches remain, including alfredoperez/angular-best-practices https://alfredo-perez.dev/blog/2026-02-12-angular-best-practices-for-ai , inspired by Vercel's react-best-practices. Commentary has focused on why an official, repo-based skill matters. Writing for Angular.love http://Angular.love , Dominik Donoch praised https://angular.love/implementing-the-official-angular-claude-skills its "autonomous verification loop," which forces the agent to run ng build after edits, and its orchestrator design that loads only relevant reference files to limit token use. On Reddit https://www.reddit.com/r/angular/comments/1s2dkvz/implementing the new official angular claude/ , developers said the skills "feel more native because they live in the repo" and are "versionable, diffable," while another admitted they "didn't know angular had its own best practices skill." Skeptics are less convinced the format fixes reliability. On Hacker News https://news.ycombinator.com/item?id=48015397 , one commenter argued such harnesses: These harnesses approaches pretend as if LLMs are strict and perfect rule followers and the only problem is not being able to specify enough rules clearly enough. That's fundamental cognitive lapse in how LLMs operate. While others countered that you should not "let the perfect be the enemy of the good." For migration, teams replacing community packages should remove them first with npx skills remove analogjs/angular-skills. The CLI also tracks drift through a lock file, so npx skills check and npx skills update keep pace with Angular's frequent releases. Because the skills target v20 and later, older projects should first follow the official update guide https://angular.dev/update-guide to adopt standalone components, inject , and built-in control flow that the skills assume. Angular is Google's open-source, TypeScript-first web framework, widely adopted across enterprise applications and built around standalone components and signal-based reactivity.