angular-19_skill

This skill helps you implement Angular 19 patterns with signals, standalone components, and resource APIs to modernize reactive UI development.
  • TypeScript

0

GitHub Stars

4

Bundled Files

3 weeks ago

Catalog Refreshed

2 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill avvale/aurora-front --skill angular-19

  • resource-api.md1.8 KB
  • signals-api.md2.3 KB
  • SKILL.md6.3 KB
  • template-syntax.md2.0 KB

Overview

This skill covers practical Angular 19 patterns: signals, standalone components, resource APIs, signal queries, dependency injection, and integration with the Aurora framework. It focuses on modern reactive practices, tree-shakable providers, lifecycle hooks, and RxJS interop to build efficient, predictable UI. Use it when implementing components, directives, pipes, services, or migrating to Angular 19 idioms.

How this skill works

The skill inspects component and service implementations and recommends Angular 19 idiomatic replacements (signals, input/output helpers, and view queries). It highlights lifecycle and rendering utilities (afterRenderEffect, afterRender, afterNextRender), resource and rxResource usage for async data, and rxjs interop helpers like toSignal/toObservable and takeUntilDestroyed. It also suggests DI patterns using inject(), providedIn singletons, and provideAppInitializer for app startup tasks.

When to use it

  • Implementing new or migrated Angular components, directives, pipes, or services
  • Adopting reactive state with signals, computed, and effect in component logic
  • Loading async data with resource(), rxResource(), or signal-based queries
  • Rewriting DI to use inject(), provideAppInitializer(), and tree-shakable providers
  • Integrating third-party libs or Aurora framework features that need post-render initialization

Best practices

  • Prefer standalone components by default; avoid explicit standalone: true
  • Use signal(), computed(), and effect() for local reactive state; replace @Input/@Output with input()/output() helpers
  • Use resource()/rxResource() for async data and avoid ngOnInit for data loading
  • Use inject() inside classes rather than constructor injection for brevity and tree shaking
  • Adopt OnPush change detection with signals and use takeUntilDestroyed() for RxJS cleanup

Example use cases

  • Detail view component using signals for local model, computed values for derived state, and resource() for remote loading
  • Directive that exposes a signal input and focuses an element when the signal becomes true
  • Service providedIn: 'root' that exposes a signal-backed API and converts observables with toSignal
  • App initializer using provideAppInitializer() to load configuration before bootstrap
  • Component that uses afterRenderEffect to sync a chart library with signal-driven data

FAQ

No. Angular 19 assumes standalone by default; only add NgModule if you need legacy module behavior.

When should I use resource() vs rxResource()?

Use resource() for simple signal-backed async reads and rxResource() when you need Observable-based patterns or more advanced RxJS control.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational