Angular Skills
Official Angular team skills: code generation with current practices, signals, forms, SSR and new app setup
- 101,091 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The skill tells the agent to run ng build and Angular CLI commands in the project
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/angular-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The skill tells the agent to run ng build and Angular CLI commands in the project
This is third-party code. Review the repository files before installing.
What it does
Two skills maintained by the Angular team in the main repository and published to angular/skills. angular-developer first checks the project's Angular version, then writes components, services and routes per the current style guide and runs ng build afterwards to fix build errors. References cover signals, linkedSignal and resource, Signal Forms, dependency injection, SSR, accessibility, animations and testing. angular-new-app sets the rules for creating a new app with the Angular CLI.
Who it is for. For Angular developers who want the agent to write code for their framework version rather than outdated examples.
Good fit when
- The agent writes components and services in an Angular project
- You are moving to signals or Signal Forms
- You need a new app with a modern structure
Not a fit when
- The project is on AngularJS 1.x
- The frontend uses another framework
Example request
Create an orders list component using signals with loading via httpResourceLimitations
The skills are in English and target recent Angular versions; some advice, such as Signal Forms, applies to v22 and newer. The agent needs terminal access to run ng build and the Angular CLI.
How to disable. Remove the angular-developer and angular-new-app folders from the agent's skills directory.
FAQ
Why install from angular/skills instead of angular/angular?
The skills are edited in skills/dev-skills of the main repository and synced to the separate angular/skills repository for installation.
Are the skills in .agent/skills meant for users too?
No, those are for framework contributors: PR review and compiler source references.
Discussion
No questions or reviews yet.
Related
SkillsCreative coding skills for Claude Code: motion, micro-interactions and visual systems for web, Android and Apple
Skills against boilerplate-looking UIs: layout, type, motion and spacing, plus reference image generation for web and mobile
Four official Material UI skills: styling, theming, Next.js integration and working alongside Tailwind CSS
Official Claude Code plugin from the Next.js repo: adopting Cache Components and Partial Prefetching, and verifying changes on a running dev server
A skill set for the Vue, Vite and Nuxt stack: the author's conventions plus digests of official tool documentation
Frontend Design (Ilm-Alan)
frontend-design
A frontend design skill with eight aesthetic anchors: each fixes palette, type and texture in CSS tokens. A separate project, not from Anthropic
README in short
The README in skills/dev-skills describes two skills, angular-developer and angular-new-app, meant to generate idiomatic code and give architectural guidance for current versions. Installation goes through npx skills add for Gemini CLI, Antigravity and other agents. Changes are accepted as pull requests to the main repository. MIT licensed.
README badge
Original SKILL.md
--- name: angular-developer description: Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling. license: MIT metadata: author: Copyright 2026 Google LLC version: '1.0' --- # Angular Developer Guidelines 1. Always analyze the project's Angular version before providing guidance, as best practices and available features can vary significantly between versions. If creating a new project with Angular CLI, do not specify a version unless prompted by the user. 2. When generating code, follow Angular's style guide and best practices for maintainability and performance. Use the Angular CLI for scaffolding components, services, directives, pipes, and routes to ensure consistency. 3. Once you finish generating code, run `ng build` to ensure there are no build errors. If there are errors, analyze the error messages and fix them before proceeding. Do not skip this step, as it is critical for ensuring the generated code is correct and functional. ## Creating New Projects If no guidelines are provided by the user, here are some default rules to follow when creating a new Angular project: 1. Use the latest stable version of Angular unless the user specifies otherwise. 2. Use Signal Forms for form management in new projects (stable in Angular v22 and newer) [Find out more](references/signal-forms.md). **Execution Rules for `ng new`:** When asked to create a new Angular project, you must determine the correct execution command by following these strict steps: **Step 1: Check for an explicit user version.** - **IF** the user requests a specific version (e.g., Angular 15), bypass local installations and strictly use `npx`. - **Command:** `npx @angular/cli@<requested_version> new <project-name>` **Step 2: Check for an existing Angular installation.**