Angular Standards

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 the project's configured build script to ensure there are no build errors. If there are errors, analyze the error messages and fix them before proceeding.

LIFT Principle

Before creating any new component, service, directive, guard, helper, generator, or test, apply the LIFT principle:

• Locate: Find existing code, contracts, generators, patterns, and references in the project and domain.
• Identify: Determine what already solves part of the problem and where there is potential duplication.
• Find: Find the smallest coherent point of reuse, extension, or composition before introducing new code.
• Try to be DRY: Eliminate real duplication without creating premature abstractions or unnecessary generic structures.

Creating New Projects