angular-developer
Generate Angular code and provide architectural guidance across the full framework stack.
- Covers components, signals, forms (signal, template-driven, reactive), dependency injection, routing, SSR, accessibility (ARIA), animations, styling, and testing
- Analyzes project Angular version before providing guidance; uses Angular CLI for scaffolding to ensure consistency
- Validates generated code with
ng buildbefore delivery to catch errors early - Recommends signal forms for Angular v21+ projects and includes references for each major topic area
Angular Developer Guidelines
-
Always analyze the project's Angular version before providing guidance, as best practices and available features can vary significantly between versions. If creating a new project with Angular CLI, do not specify a version unless prompted by the user.
-
When generating code, follow Angular's style guide and best practices for maintainability and performance. Use the Angular CLI for scaffolding components, services, directives, pipes, and routes to ensure consistency.
-
Once you finish generating code, run
ng buildto ensure there are no build errors. If there are errors, analyze the error messages and fix them before proceeding. Do not skip this step, as it is critical for ensuring the generated code is correct and functional.
Creating New Projects
If no guidelines are provided by the user, here are same default rules to follow when creating a new Angular project:
- Use the latest stable version of Angular unless the user specifies otherwise.
- Use Signals Forms for form management in new projects (available in Angular v21 and newer) Find out more.
Execution Rules for ng new:
When asked to create a new Angular project, you must determine the correct execution command by following these strict steps:
Step 1: Check for an explicit user version.