formio-angular-form

Embedding a Form.io form in Angular

Nested sub-skill. formio-angular-form/SKILL.md sits inside the formio-angular skill folder, beside formio-angular-resources. The name: formio-angular-form frontmatter is there so recursive-scan clients classify the file; it is not a separately-registered top-level skill. The formio-angular parent reaches this document the same way it reaches SETUP.md and AUTH.md — it is loaded by path. Never invoke it by frontmatter name; open the file.

One component

FormioComponent from @formio/angular, as the element <formio>:

<formio [src]="formUrl" (submit)="onSubmit($event)"></formio>

That is the whole entry point. It fetches the definition, renders it, saves the submission, places server errors on the fields that caused them, and shows its own alert and loading chrome. Its inputs are reactive, so a parent can change the form, the submission, or the language after the first render.

There is no component decision to make on arrival. When <formio> is genuinely the wrong tool — a form mounted outside Angular's tree, a page that must not carry @formio/angular at all — the second path is the renderer itself, and references/renderer-directly.md is where that goes. It is a different job, not a different component.

Capture the workspace root first

This branch is exempted from the parent skill's workspace pre-flight, so nothing has captured a path for it — and everything below runs commands and edits files. Capture one absolute path before the first of them: the directory the user invoked you from, which is the working directory this session started in, NOT the output of a pwd run after other commands. A shell working directory persists between commands in an agent session, so one cd earlier in the turn retargets every relative path after it.

Call it workspaceRoot, give every command its own directory (cd "<workspaceRoot>" && <command>), read and write files at absolute paths under it, and pass it as cwd to project_get when references/config.md needs the project URLs. If you cannot account for where the shell currently is, state the path you intend to use and confirm it before touching anything.