What problem does it solve? Developing the EAF frontend requires navigating Angular 20, legacy jQuery code, PrimeNG components, SignalR real-time features, and EAF-specific module loading, which makes it easy to introduce inconsistent patterns or break framework integration. ## Core Features & Use Cases - Angular Best Practices: Enforces standalone components, signals, native control flow, OnPush change detection, and reactive forms aligned with Angular 18-20 conventions. - EAF Framework Integration: Covers @eaf/* path mappings, EAF.js resources, jQuery coexistence, SignalR connections, and PrimeNG 17 theming within the EAF template structure. - Migration Guidance: Provides steps for Angular version upgrades, Metronic 8 + Bootstrap 5 modernization, and PWA/offline configuration. - Use Case: When adding a new feature component to the EAF Angular UI, use this Skill to generate accessible, WCAG AA-compliant code that follows project conventions and avoids deprecated patterns like ngClass or jQuery DOM manipulation. ## Quick Start Ask the AI to create a new standalone Angular component for the EAF UI following the project's signals, PrimeNG, and accessibility conventions.