Run any Skill in Manus with one click

ode-custom-jsonforms-extension

Stars9

Forks13

UpdatedMarch 27, 2026 at 10:02

Guides adding ODE custom JSON Forms extensions (custom renderers, testers, ext.json, dynamic functions). Use when extending forms with non-standard controls or wiring extension manifests. Official behavior is documented on opendataensemble.org.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

OpenDataEnsemble

OpenDataEnsemble/ode

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	ode-custom-jsonforms-extension
description	Guides adding ODE custom JSON Forms extensions (custom renderers, testers, ext.json, dynamic functions). Use when extending forms with non-standard controls or wiring extension manifests. Official behavior is documented on opendataensemble.org.

ODE custom JSON Forms extensions

When to use

Custom control rendering (tester + renderer pattern).
ext.json (or app-level extension manifest) and module paths.
Dynamic choice lists or helper functions referenced from the UI schema.

What to do

Read Custom extensions and Dynamic choice lists on the docs site.
Keep bundled JS compatible with the Formulus WebView (no Node-only APIs in runtime code).
Align format in schema with the renderer contract described in docs.
For AI-only context summaries, CONTEXT_ODE_FORMS.md in custom_app may help — still verify against opendataensemble.org.

Do not

Assume vanilla jsonforms.io examples work without checking ODE’s registered renderers and extension loading rules.

More from this repository

same repository

ode-synk-bundle-publish

OpenDataEnsemble/ode

Guides publishing and managing ODE app bundles with the Synkronus CLI (synk): config, auth, upload, versions. Use when deploying custom app zips or automating bundle uploads. Official reference is opendataensemble.org and OpenDataEnsemble/ode docs.

2026-06-239

ode-custom-app-form-validation

OpenDataEnsemble/ode

Helps validate ODE custom app form definitions (JSON Schema draft-07 + UI schema) and CI integration. Use when the user asks to validate forms, add validate-forms scripts, or check schema/ui consistency for Synkronus bundles. Prefer official docs at opendataensemble.org and the custom-app template repo on GitHub.

2026-03-279

pr-description

OpenDataEnsemble/ode

Generates pull request description body in raw markdown using the ODE PR template. Use when the user asks for a PR description, types "/pr description" or "pr description", or wants copyable markdown for a PR body. Output is always in a fenced markdown code block for one-click copy.

2026-03-219

name	ode-custom-jsonforms-extension
description	Guides adding ODE custom JSON Forms extensions (custom renderers, testers, ext.json, dynamic functions). Use when extending forms with non-standard controls or wiring extension manifests. Official behavior is documented on opendataensemble.org.

ODE custom JSON Forms extensions

When to use

Custom control rendering (tester + renderer pattern).
ext.json (or app-level extension manifest) and module paths.
Dynamic choice lists or helper functions referenced from the UI schema.

What to do

Read Custom extensions and Dynamic choice lists on the docs site.
Keep bundled JS compatible with the Formulus WebView (no Node-only APIs in runtime code).
Align format in schema with the renderer contract described in docs.
For AI-only context summaries, CONTEXT_ODE_FORMS.md in custom_app may help — still verify against opendataensemble.org.

Do not

Assume vanilla jsonforms.io examples work without checking ODE’s registered renderers and extension loading rules.