Profile My skills Saved Collections Edit profile Submit a skill

Commentary Form Rendering

Implement a Commentary Form as native rendering, a Markdown or MDX embed, declarative static HTML, or a customer-owned Live Preview custom renderer. Use for data-commentary bindings, Forms SDK bridge integration, sandbox and origin constraints, responsive control implementation, and renderer review handoff; use design-effective-forms for question and experience decisions.

commentary-dev f600272 3 files · 2.9 KB Updated
Web & Frontend

File contents

Commentary Form Rendering

Keep the Form Contract authoritative for field ids, validation, required rules, and destinations. Choose one renderer:

  • Native standalone contract when standard rendering is sufficient.
  • Markdown or MDX embed when the form belongs inside explanatory content.
  • Static HTML for custom layout without customer JavaScript.
  • Live Preview custom renderer only for a customer-owned interactive application.

Validate the contract through commentary_forms validate_contract and validate submitted values server-side. Static HTML must use declarative bindings and cannot rely on inline handlers or arbitrary scripts. A custom renderer must use the Forms SDK inside an origin-bound Live Preview Review and must never include tokens, cookies, local storage, or private review URLs in values or metadata.

Read references/rendering-patterns.md for syntax. Use commentary-draft-review for source artifact review and commentary-live-preview-review for selected-element feedback on an interactive renderer.

commentary-dev/commentary-skills/tree/main/skills/commentary-form-rendering commit f600272db8

Browse category

Frequently asked questions

npx skillmds@latest add commentary-dev/commentary-form-rendering