best-practices
Installation
SKILL.md
Best Practices Audit: $ARGUMENTS
If $ARGUMENTS is empty, ask the user for a component path or folder before proceeding.
Audit the code at $ARGUMENTS against the project's conventions. Unlike /review-pr which checks diffs, this audits existing code as-is.
Checklist
1. Angular 21+ Patterns
- New code uses
input()/output()/model()/linkedSignal(). Existing@Input()/@Output()decorators are acceptable. -
host: {}in decorator — no@HostBinding()/@HostListener() -
@if/@for/@switch— no*ngIf/*ngFor/*ngSwitch - No
standalone: true(default since Angular 19) - No
allowSignalWritesoption ineffect()(the option no longer exists) -
DestroyRef+takeUntilDestroyed()— no customDestroyedService -
computed()+host: { '[class]': }— noCssClassBuilder/@applyCssClass - No
ngClass/ngStyle(use direct bindings)
Related skills
More from sap/fundamental-ngx
migrate
Migrate a component or directive to Angular 21+ signal-based patterns
5create-test
Generate or update unit tests for a component following project testing conventions
5a11y-audit
Audit a component for WCAG AA accessibility compliance
5review-pr
Review a pull request against project conventions and Angular 21+ best practices
5preflight
Run local quality gates before creating a PR
4update-docs
Verify and update documentation examples to match a component's current public API
4