Angular

What This Skill Does

The Angular skill empowers OpenClaw to act as a senior-level frontend architect specializing in the Angular framework. It provides expert guidance on modern application development, focusing on performance, memory management, and scalable architecture. The skill covers the lifecycle of components, advanced RxJS stream handling, dependency injection best practices, and effective state management using Signals. It helps developers move away from legacy approaches to adopt current standards like Standalone components and modern Change Detection strategies.

Installation

To integrate this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/angular

Use Cases

• Refactoring large-scale Angular applications to utilize OnPush change detection and Signals.
• Debugging memory leaks caused by improper RxJS subscriptions in service layers.
• Optimizing complex forms and validation logic using ReactiveForms or Template-driven approaches.
• Architecting modular services with clean dependency injection patterns to avoid circular dependencies.
• Migrating legacy module-based architectures to modern Standalone components.
• Resolving runtime issues related to Zone.js, SSR compatibility, and DOM access.

Example Prompts

1. "I am seeing memory leaks in my user dashboard. Can you analyze my component lifecycle and suggest how to use takeUntilDestroyed to clean up my RxJS subscriptions?"
2. "My *ngFor list is re-rendering entirely whenever a single item changes. Show me how to implement a trackBy function to improve performance."
3. "Help me refactor this legacy component. I need to switch from manual subscription management to the async pipe and integrate Signals for local state."

Tips & Limitations

To get the best results, always share relevant code snippets or component file structure. Remember that while this skill is expert in Angular syntax, it cannot physically manipulate your IDE files without proper permissions. Always verify the context of your ViewChild access, as the skill will frequently remind you that these are unavailable in the constructor. For SSR projects, avoid direct nativeElement access; the skill will provide Renderer2 alternatives. Use this tool early in your development cycle to establish robust architectural patterns rather than just for debugging runtime errors.