frontend-angular

Enforce Angular 19+ architecture and coding standards in the Zoppy monorepo.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/Zoppy-crm/.github --skill frontend-angular-zoppy-crm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-angular
Source: https://github.com/Zoppy-crm/.github/tree/main/skills/frontend/frontend-angular
Command: npx skills add https://github.com/Zoppy-crm/.github --skill frontend-angular-zoppy-crm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide removes ambiguity and inconsistency in Angular frontend development at Zoppy by consolidating architecture, coding, styling, design-system and testing rules so teams deliver more reliable, maintainable features and fewer regressions.

Core Features & Use Cases

  • Standardizes component architecture including standalone components, explicit signal typing, and OnPush change detection to ensure predictable reactivity.
  • Defines state management, service scoping, lazy-loaded routing, schema-driven UI patterns, Tailwind styling with design tokens, and ui-components usage for consistent visuals.
  • Specifies testing and quality practices using Jasmine for unit tests and Playwright for end-to-end, plus conventions for PR reviews and folder structure.
  • Use cases include onboarding, code review checklists, creating shareable feature libraries, and verifying new features against organizational standards.

Quick Start

Ask the AI to review a feature folder and report violations against the frontend-angular conventions.

Frequently Asked Questions about frontend-angular

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

FAQPage Schema
How do I manage Angular state with Signals and ensure correct service scoping?

Standardizing Angular state management involves using Signals for predictable reactivity and defining specific service scoping rules. This approach ensures consistent state handling and reduces regressions across feature libraries.

What testing patterns does this Angular convention specify for unit and end-to-end tests?

Yes, the Angular standard requires styling with Tailwind preset tokens and design-system integration. This enforces consistent visuals across applications by leveraging ui-components and schema-driven UI patterns.

Can I use this to review an existing Angular feature folder for convention violations?

The Angular convention specifies using Jasmine for unit tests and Playwright for end-to-end tests. These testing patterns serve as quality practices and code review checklists to verify features against organizational standards.

Why should I use standalone components and new control flow constructs in Angular 19+?

Yes, you can ask the AI to review an Angular feature folder and report violations against the frontend conventions. This quickly identifies missing lazy-loaded routes, OnPush change detection, or new control flow constructs.