formio/ai / plugin/skills/formio-form
formio-form
VerifiedEmbed and render Form.io forms in any web app with the `@formio/js` renderer — by URL or JSON, pre-filled, controlled from JavaScript — and own field behavior: conditionals, calculated values, JSON Logic validation, cascading selects. The default "embed a form" entry point. Use when the user asks to "embed a form", "render a form", "add this form to my page", "pre-fill a form", "show or hide a field based on another field", "calculate a field value", "add custom validation to a field", or add conditional wizard pages — field behavior in ANY framework's form stays here. Not for: Angular (see `formio-angular`) or React-named (see `formio-react`) embedding; building an app (see `formio-application`) or its data model (see `formio-resource-planner`); REST endpoints (see `formio-api`); the raw SDK (see `formio-sdk`); creating a new form (see `formio-form-builder`); agent-filled forms or chats (see `formio-uag`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.4 KB |
| references/calculated-values.md | markdown | 1.8 KB |
| references/conditionals.md | markdown | 2.0 KB |
| references/external-data.md | markdown | 7.9 KB |
| references/field-logic.md | markdown | 4.0 KB |
| references/javascript-api.md | markdown | 3.6 KB |
| references/json-logic.md | markdown | 3.2 KB |
| references/options.md | markdown | 2.5 KB |
| references/rendering.md | markdown | 2.9 KB |
| references/setup.md | markdown | 5.0 KB |
| references/validation.md | markdown | 2.2 KB |
| references/wizards.md | markdown | 3.3 KB |
references/validation.md
View on GitHub# Custom Validation with JSON Logic
## Overview
A component's `validate.json` property holds a JSON Logic expression the renderer evaluates on every value change and on submit. The contract:
- The expression result is **`true`** → the value is valid.
- The expression result is a **string** → the value is invalid and that string is the validation error message shown on the component.
Expression syntax and the operations vocabulary live in [json-logic.md](./json-logic.md). Inside `validate.json`, `{"var": "input"}` resolves to the value of the component being validated, and `{"var": "data.<key>"}` reaches any other field for cross-field rules.
## Canonical example
An `if` that returns `true` for the valid case and the error string otherwise:
```json
{
"type": "textfield",
"key": "name",
"label": "Name",
"input": true,
"validate": {
"json": {
"if": [{ "===": [{ "var": "input" }, "Bob"] }, true, "Your name must be 'Bob'!"]
}
}
}
```
Typing anything but `Bob` marks the field invalid with exactly `Your name must be 'Bob'!`; typing `Bob` clears the error. A failed rule also blocks `form.submit()` — the promise rejects and the messages land on `form.errors` (see [javascript-api.md](./javascript-api.md)).
## Cross-field rules
Reach other fields through `data`:
```json
{
"validate": {
"json": {
"if": [
{ ">=": [{ "var": "input" }, { "var": "data.minimumBid" }] },
true,
"Your bid must be at least the minimum bid."
]
}
}
}
```
## Composing with standard validation
`validate.json` runs alongside the declarative `validate` keys — it does not replace them. All configured rules must pass:
```json
{
"validate": {
"required": true,
"minLength": 2,
"pattern": "[A-Za-z]+",
"json": { "if": [{ "===": [{ "var": "input" }, "Bob"] }, true, "Your name must be 'Bob'!"] }
}
}
```
`required`, `minLength`/`maxLength`, `min`/`max`, `pattern`, and `customMessage` keep their standard meanings; `json` adds the escape hatch for everything they cannot express.
## See also
- [json-logic.md](./json-logic.md) — operations and `var` resolution.
- [field-logic.md](./field-logic.md) — reacting to values beyond validity (disable, hide, mutate).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |