Angular Best Practices Rules Reviewer

The Angular Best Practices Rules Reviewer skill analyzes codebases to identify violations of established Angular development standards and community guidelines. It provides actionable feedback on module structure, component organization, and adherence to the framework's recommended patterns.

When to use it

• Before committing changes to ensure new components follow team-specific or official Angular conventions.
• During code reviews to catch architectural drift or anti-patterns in existing modules.
• When integrating third-party libraries to verify they align with your project’s strict style guide.
• To automate linting workflows that go beyond basic syntax checking into semantic best practices.

Key capabilities

• Detects deviations from official Angular documentation and community-accepted patterns.
• Reviews module imports, dependency injection strategies, and component lifecycles.
• Identifies potential performance bottlenecks caused by inefficient change detection or data binding.
• Enforces consistent naming conventions and file structures across the application.

Example prompts

• "Review this new customer dashboard component for adherence to Angular best practices."
• "Analyze the entire src/app folder and list any violations of standard module organization."
• "Check my service layer for proper dependency injection patterns and identify any circular dependencies."

Tips & gotchas

Ensure your project is fully built or at least has a valid configuration file, as the reviewer needs context to understand the application's architecture. This skill complements but does not replace static analysis tools like ESLint; use it specifically for high-level architectural and pattern compliance.