angular-material-19_skill

This skill helps you implement Angular Material 19 theming, timepicker, CDK drag-drop, and dark mode to build cohesive, accessible UIs.
  • TypeScript

0

GitHub Stars

5

Bundled Files

2 months ago

Catalog Refreshed

4 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 veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill avvale/aurora-front --skill angular-material-19

  • cdk-patterns.md3.9 KB
  • custom-controls.md4.2 KB
  • SKILL.md7.8 KB
  • theming.md4.0 KB
  • timepicker.md2.3 KB

Overview

This skill provides concise guidance for using Angular Material 19: components, Material 3 theming, CDK patterns, the new timepicker, and building signal-based custom form controls. It focuses on practical imports, patterns, and migration steps to modernize apps to M19 and M3 theming. The content highlights dark mode, CSS variables, and recommended CDK usage for drag-and-drop and overlays.

How this skill works

It inspects common Material usage patterns and recommends concrete replacements and APIs for v19: component imports, signal-based queries, ControlValueAccessor/MatFormFieldControl implementations, and CSS-variable theming with the M3 mixins. It summarizes CDK patterns (2D drag-drop, overlay, selection), the mat-timepicker integration, and dialog/table examples to accelerate implementation. It also lists anti-patterns and a migration checklist to reduce breaking changes and styling conflicts.

When to use it

  • You are building or upgrading a UI with Angular Material 19 components
  • Creating custom form controls or MatFormFieldControl using signals
  • Implementing Material 3 theming with CSS variables and dark/light switching
  • Adding CDK features: 2D drag-drop, overlay, tab reordering, accessibility
  • Replacing third-party timepickers with the new mat-timepicker

Best practices

  • Import only required Material modules instead of a global Material module
  • Use CSS design tokens (--mat-*) and the mat.theme() mixin for M3 theming
  • Prefer signal-based queries (viewChild -> viewChild(signal)) and effects over manual stateChange calls
  • Use light-dark() and set color-scheme on html for robust dark mode
  • Implement typed interfaces for dialog data and avoid any for safety

Example use cases

  • Replace a legacy timepicker with mat-timepicker and validate intervals with built-in APIs
  • Create a signal-based data table with mat-paginator and mat-sort using computed dataSource
  • Implement draggable 2D kanban boards using CDK DragDropModule and tab reordering
  • Build a custom form control that implements ControlValueAccessor and MatFormFieldControl using signals and effect-driven updates
  • Theme an app with Material 3 tokens, override component styles with styling mixins, and add a dark/light toggle

FAQ

No. M3 makes design tokens available as CSS variables; you can migrate gradually and override per-component using the provided styling mixins.

Should I replace existing ViewChild patterns immediately?

Prefer converting to signal queries for new code and during feature updates; prioritize areas where lifecycle or change detection issues occur.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
angular-material-19 skill by avvale/aurora-front | VeilStrat