modus-angular-forms-validation

Guidance for building and checking forms in Angular with Modus Web Components, which are reusable interface elements provided by the Modus design system.

In plain words
What is it for?
Use it when creating forms with required fields, email checks, password length rules, and visible validation messages.
Why use it?
It explains how to validate fields and track when users have interacted with them, since these components do not automatically update Angular’s touched state.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/julianoczkowski/create-trimble-app/modus-angular-forms-validation
Clone the repo
git clone --depth 1 https://github.com/julianoczkowski/create-trimble-app

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 840 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00840
Opus 5 $0.00000 $0.00420
Sonnet 5 $0.00000 $0.00168
Haiku 4.5 $0.00000 $0.00084

Measured 2d ago against content hash e9a16ecae6d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

modus-angular-forms-validation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

templates/angular/.cursor/rules/modus-angular-forms-validation.mdc · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Forms and Validation Rules

Comprehensive guide for implementing forms and validation in Angular applications with Modus Web Components.

Core Principles

ALWAYS Use Reactive Forms

import { FormBuilder, ReactiveFormsModule, Validators } from '@angular/forms';

@Component({
  imports: [ReactiveFormsModule],
})
export class MyFormComponent {
  private readonly fb = new FormBuilder();

  readonly form = this.fb.group({
    email: ['', [Validators.required, Validators.email]],
    password: ['', [Validators.required, Validators.minLength(8)]],
  });
}

CRITICAL: Track Touched State Manually

Modus Web Components don't automatically track Angular form touched state. You must manually track which fields have been touched.

export class FormComponent {
  readonly touchedFields = signal<Set<string>>(new Set());

  handleFieldChange(event: InputEvent, fieldName: string): void {
    const target = event.target as HTMLInputElement;
    const control = this.form.controls[fieldName];
    control.setValue(target.value);
    this.markFieldTouched(fieldName);
  }

  handleFieldBlur(fieldName: string): void {
    this.markFieldTouched(fieldName);
  }

  private markFieldTouched(fieldName: string): void {
    this.touchedFields.update((fields) => {
      const newFields = new Set(fields);
      newFields.add(fieldName);
      return newFields;
    });
  }
}

Validation Feedback Pattern

Use Computed Signals for Validation Feedback

readonly emailFeedback = computed<IInputFeedbackProp | undefined>(() => {
  const control = this.form.controls.email;
  const isTouched = this.touchedFields().has('email');

  if (!isTouched || !control.errors) return undefined;

  if (control.errors['required']) {
    return { level: 'error', message: 'Email address is required.' };
  }
  if (control.errors['email']) {
    return { level: 'error', message: 'Please enter a valid email address.' };
  }
  return undefined;
});

Connecting Modus Components to Forms

Read the full file on GitHub · 125 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 125 lines · 0 tokens per session scan A e9a16ecae6d3

Subscribe to this mod's changes

modus-angular-forms-validation is a cursor rule published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 840 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.