angular-developerlisted

# Angular Developer Guidelines ## When to Activate - Working in any Angular project or codebase - Creating or scaffolding a new Angular project, application, or library - Generating components, services, directives, pipes, guards, or resolvers - Implementing reactivity with Angular Signals, `linkedSignal`, or `resource` - Working with Angular forms (signal forms, reactive forms, or template-driven) - Setting up dependency injection, routing, lazy loading, or route guards - Adding accessibility (ARIA), animations, or component styling - Writing or debugging Angular-specific tests (unit, component harness, E2E) - Configuring Angular CLI tooling or the Angular MCP server 1. 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. 2. 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. 3. Once you finish generating code, run `ng build` to 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, use