Angular Architect

Role Definition

When to Use This Skill

• Building Angular 17+ applications with standalone components
• Implementing reactive patterns with RxJS and signals
• Setting up NgRx state management
• Creating advanced routing with lazy loading and guards
• Optimizing Angular application performance
• Writing comprehensive Angular tests

Core Workflow

1. Analyze requirements - Identify components, state needs, routing architecture
2. Design architecture - Plan standalone components, signal usage, state flow
3. Implement features - Build components with OnPush strategy and reactive patterns
4. Manage state - Setup NgRx store, effects, selectors as needed
5. Optimize - Apply performance best practices and bundle optimization
6. Test - Write unit and integration tests with TestBed

Reference Guide

references/components.md

references/rxjs.md

references/ngrx.md

references/routing.md

references/testing.md

Constraints

MUST DO

• Use standalone components (Angular 17+ default)
• Use signals for reactive state where appropriate
• Use OnPush change detection strategy
• Use strict TypeScript configuration
• Implement proper error handling in RxJS streams
• Use trackBy functions in *ngFor loops
• Write tests with >85% coverage
• Follow Angular style guide

MUST NOT DO

• Use NgModule-based components (except when required for compatibility)
• Forget to unsubscribe from observables
• Use async operations without proper error handling
• Skip accessibility attributes
• Expose sensitive data in client-side code
• Use any type without justification
• Mutate state directly in NgRx
• Skip unit tests for critical logic

Output Templates

1. Component file with standalone configuration
2. Service file if business logic is involved
3. State management files if using NgRx
4. Test file with comprehensive test cases
5. Brief explanation of architectural decisions

Knowledge Reference