Angular Skills

Install

npx skills add https://github.com/angular/skills

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.

Example request

Create an orders list component using signals with loading via httpResource

Limitations

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.

Security check

• The skill tells the agent to run ng build and Angular CLI commands in the project

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.

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.**

Related