Back to Skills

angular-developer

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

100,442stars27,183forksUpdated 6/25/2026

Security Assessment

Safe(100/100)

Detected risks:

Agent-reviewed override(Substring false positive: 'launchD' matched the 'launchDate' form field in an Angular signal-forms example. Benign web-dev guidance skill.)
Security Score100/100

About angular-developer

An Angular development assistant that generates Angular code and provides architectural guidance across the framework's major areas. It is triggered when creating projects, components, or services, or when guidance is needed on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, server-side rendering, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling. A foundational rule is to analyze the project's Angular version first, because best practices and available features vary significantly between versions, and to scaffold with the Angular CLI for consistency. After generating code it runs ng build and fixes any build errors before proceeding, treating the build as a non-skippable correctness check.

Project creation follows strict execution rules for ng new: if the user requests a specific version it uses npx @angular/cli@<version> new; otherwise it runs ng version to detect an existing install and uses ng new when one is found, falling back to npx @angular/cli@latest new when none exists. For new applications it prefers the latest stable Angular and Signals Forms (available in Angular v21 and newer), while older applications or existing forms keep whatever form strategy already matches the codebase.

The skill is organized around topic-specific reference files it consults on demand. Components coverage spans fundamentals and template control flow (@if, @for, @switch), signal-based inputs and outputs, and host elements; reactivity covers signal/computed, linkedSignal for dependent writable state, resource for async data, and effects (including when not to use them); forms compare signal, template-driven, and reactive approaches; dependency injection covers inject(), providers, injection context, and hierarchical injectors; and routing covers route definitions, lazy loading, outlets, guards, resolvers, lifecycle events, rendering strategies (CSR, SSG, SSR with hydration), and view-transition animations. Accessible headless components and Tailwind styling are also addressed, with links to angular.dev for deeper documentation.

FAQ

Why does it check the Angular version before giving guidance?

Because Angular best practices and available features vary significantly between versions. It always analyzes the project's version first so the guidance and generated code match what that version supports.

How does it decide which command to use for creating a new project?

If you request a specific version it uses npx @angular/cli@<version> new. Otherwise it runs ng version to detect an existing install and uses ng new, falling back to npx @angular/cli@latest new when no installation exists.

Which form approach does it prefer for new apps?

Signal Forms, which are available in Angular v21 and newer. For older applications or existing forms it uses the form type that matches the app's current strategy (template-driven for simple forms, reactive for complex ones).

Does it verify the code it generates?

Yes. After generating code it runs ng build, and if there are errors it analyzes the messages and fixes them before proceeding. This step is described as critical and must not be skipped.

What does it recommend for managing reactive state?

Angular Signals — core signal and computed primitives, linkedSignal for writable state linked to a source, resource for fetching async data into signal state, and effect for side effects (with guidance on when not to use effects).

All Files

38 files
references/angular-aria.md18.0 KB
View
references/component-harnesses.md2.7 KB
View
references/components.md3.3 KB
View
references/data-resolvers.md1.6 KB
View
references/angular-animations.md3.9 KB
View
references/cli.md3.6 KB
View
references/component-styling.md2.5 KB
View
references/creating-services.md2.8 KB
View
references/define-routes.md1.7 KB
View
references/di-fundamentals.md3.4 KB
View
references/effects.md2.7 KB
View
references/hierarchical-injectors.md2.1 KB
View
references/injection-context.md1.9 KB
View
references/linked-signal.md2.6 KB
View
references/defining-providers.md2.2 KB
View
references/e2e-testing.md2.5 KB
View
references/environment-configuration.md3.2 KB
View
references/host-elements.md2.1 KB
View
references/inputs.md2.4 KB
View
references/loading-strategies.md1.4 KB
View
references/migrations.md2.0 KB
View
references/outputs.md2.6 KB
View
references/rendering-strategies.md1.8 KB
View
references/route-animations.md1.6 KB
View
references/mcp.md3.7 KB
View
references/navigate-to-routes.md1.6 KB
View
references/reactive-forms.md3.5 KB
View
references/resource.md2.6 KB
View
references/route-guards.md1.4 KB
View
references/router-testing.md3.7 KB
View
references/signal-forms.md27.5 KB
View
references/router-lifecycle.md1.5 KB
View
references/show-routes-with-outlets.md1.6 KB
View
references/signals-overview.md2.8 KB
View
references/template-driven-forms.md3.7 KB
View
SKILL.md9.5 KB
View
references/tailwind-css.md1.8 KB
View
references/testing-fundamentals.md2.5 KB
View

Install angular-developer

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

angular/angular