angular-dev

Design Angular 17+ components, state stores, and HTTP services with .NET backend integration.

10|7|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/cuongtl1992/vibe-skills --skill angular-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: angular-dev
Source: https://github.com/cuongtl1992/vibe-skills/tree/main/skills/frontend/angular-dev
Command: npx skills add https://github.com/cuongtl1992/vibe-skills --skill angular-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides Angular 17+ development guidance covering Standalone Components, Signals-based state management, NgRx, RxJS patterns, and integration with .NET backends to help engineers structure and implement frontend features efficiently.

Core Features & Use Cases

  • Standalone-first guidance for Angular apps leveraging Standalone Components (no NgModules by default)
  • Signals for local state and NgRx Signal Store guidance for feature state, with typed HTTP patterns
  • Backend integration patterns for .NET Web API, HTTP clients, and interceptors to align frontend with backend services

Quick Start

Set up a new Angular feature using Standalone Components, Signals, and NgRx Store as described in this guide.

Frequently Asked Questions about angular-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build scalable Angular 17+ frontends using Standalone Components and Signals?

Structure scalable Angular 17+ frontends by adopting Standalone Components without NgModules, managing local state with Signals, and handling feature state via NgRx Signal Store.

What is the best way to integrate an Angular frontend with a .NET Web API backend?

Integrate Angular with a .NET Web API using typed HTTP clients and interceptors to align frontend HTTP services with backend services, ensuring clean architecture and reliable data exchange.

How do I set up a new Angular feature using NgRx Signal Store and Standalone Components?

Set up a new Angular feature by creating Standalone Components, managing local UI state with Signals, and implementing NgRx Signal Store for feature-level state alongside typed HTTP patterns.

When should I use Signals instead of NgRx Store for state management in Angular 17?

Use Signals for local component state in Angular 17, and apply NgRx Signal Store for broader feature state management, combining both to structure scalable applications with clean architecture.

Can I use lazy routing with Standalone Components in Angular 17?

Yes, lazy routing works with Standalone Components in Angular 17, allowing you to structure scalable applications by loading feature modules on demand without relying on NgModules.

Does this Angular 17 guidance require using NgModules for component architecture?

No, the Angular 17 guidance adopts a standalone-first approach by default, leveraging Standalone Components to structure scalable applications without requiring NgModules for component architecture.