angular-forms
ALWAYS use when working with Angular Forms, reactive forms, template-driven forms, form validation, or form handling in Angular applications.
What this skill does
# @angular/forms
**Version:** Angular 21 (2025)
**Tags:** Forms, Validation, Reactive Forms, Template-Driven
**References:** [Reactive Forms](https://angular.dev/guide/reactive-forms) • [Template-Driven](https://angular.dev/guide/forms) • [API](https://angular.io/api/forms)
## API Changes
This section documents recent version-specific API changes.
- NEW: Signal-based form controls — Angular 19+ signal integration for form controls
- NEW: Functional validators — Prefer functional validators over class-based validators
- NEW: `AbstractControl.markAllAsTouched()` — New method to mark all controls as touched
- NEW: `nonNullable` option — Create non-nullable FormControls
- NEW: Typed forms — Full TypeScript support for form groups and arrays
- DEPRECATED: Class-based validators — Migrate to functional validators
## Best Practices
- Use Reactive Forms for complex forms — Better structure, validation, and testability
```ts
import { FormBuilder, Validators, ReactiveFormsModule } from '@angular/forms';
@Component({
standalone: true,
imports: [ReactiveFormsModule],
template: `
<form [formGroup]="form" (ngSubmit)="onSubmit()">
<input formControlName="email" />
<div *ngIf="form.controls.email.invalid && form.controls.email.touched">
Email is required
</div>
</form>
`
})
export class LoginComponent {
private fb = inject(FormBuilder);
form = this.fb.nonNullable.group({
email: ['', [Validators.required, Validators.email]],
password: ['', [Validators.required, Validators.minLength(8)]]
});
onSubmit() {
if (this.form.valid) {
console.log(this.form.getRawValue());
}
}
}
```
- Use FormBuilder for cleaner code
```ts
form = this.fb.group({
name: ['', Validators.required],
email: ['', [Validators.required, Validators.email]],
address: this.fb.group({
street: [''],
city: ['']
})
});
```
- Use custom validators for complex logic
```ts
// Functional validator (preferred)
const forbiddenNameValidator = (control: AbstractControl): ValidationErrors | null => {
const forbidden = ['admin', 'root', 'superuser'];
return forbidden.includes(control.value) ? { forbiddenName: true } : null;
};
// Usage
name: ['', forbiddenNameValidator]
```
- Use async validators for server-side validation
```ts
email: ['',
[Validators.email],
[asyncValidator, { debounceTime: 300 }]
]
```
- Use FormArray for dynamic form fields
```ts
const form = this.fb.group({
emails: this.fb.array([
this.fb.control('')
])
});
get emails(): FormArray {
return this.form.get('emails') as FormArray;
}
addEmail() {
this.emails.push(this.fb.control(''));
}
```
- Use `updateOn` option for performance
```ts
// Only validate on blur
email: ['', { updateOn: 'blur' }]
// Only validate on submit
password: ['', { updateOn: 'submit' }]
```
- Show validation errors conditionally
```ts
<input formControlName="email"
[class.is-invalid]="email.invalid && (email.dirty || email.touched)" />
```
- Use disable() for conditionally disabled fields
```ts
// Disable based on another control
this.form.statusChanges.subscribe(() => {
if (this.form.value.isAdmin) {
this.form.controls.permissions.enable();
} else {
this.form.controls.permissions.disable();
}
});
```
- Reset form properly
```ts
// Reset with default values
this.form.reset({ email: '', name: 'Default' });
// Reset and clear validators
this.form.reset();
this.form.clearValidators();
```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.