reference-signal-forms
Explains the mental model and architecture of the code under `packages/forms/signals`. You MUST use this skill any time you plan to work with code in `packages/forms/signals`
Install
With your agent
Install OMGSkills skill "angular/angular:reference-signal-forms" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/angular/angular /tmp/angular && ln -s /tmp/angular/.agent/skills/reference-signal-forms ~/.claude/skills/reference-signal-formsFrom README
Signal Forms Architecture The packages/forms/signals directory contains the signal-based forms API for Angular. This system differs significantly from the existing Reactive and Template-driven forms. Mental Model Model-Driven: The system is built around a WritableSignal which serves as the single source of truth. Unlike Reactive Forms where the FormControl holds the value, here the Signal holds the value. The form is merely a view or projection of that signal, adding form-specific state (validity, dirty, touched). Proxy-Based Traversal: The form API (form(signal)) returns a FieldTree. This object is a Proxy. It allows accessing nested fields (e.g., myForm.user.name) without manually creating control groups. Accessing a property on the proxy lazily resolves or creates the corresponding FieldNode. Schema-Based Logic: Validation, disabled state, and other metadata are defined separately via Schemas.