Examples

These examples are intentionally short. They are designed to create a clear first impression in demos, marketplace listings, and agent onboarding flows.

The example files use a <your-handle> slug placeholder. deploy_form replaces it with the caller's account handler when available, which keeps demo deployments from colliding across users. If you copy the file into another workflow, replace <your-handle> with your account handle, team name, or a timestamp before publishing.

Media-rich survey

Repo file:

apps/motivation-form/forms/demo-multimedia-survey.md

Use this when you want to show the breadth of survey rendering quickly:

• YouTube video prompt
• image A/B visual-card choice
• code-snippet A/B comparison
• multi-choice copy preference
• respondent code input
• rating question

Good demo prompt:

Deploy the media-rich survey demo and give me the public URL. If the file still has `<your-handle>` in the slug, personalize it with my account handle before publishing.

Scored quiz

Repo file:

apps/motivation-form/forms/demo-quiz.md

Use this when you want to show quiz mode without a long assessment:

• four scored questions
• single-choice and multi-select answers
• pass/fail threshold
• score reveal
• answer reveal

Good demo prompt:

Deploy the Motivation Form quick-check quiz and show me the public URL. If the file still has `<your-handle>` in the slug, personalize it with my account handle before publishing.

Agent flow

When an MCP-connected agent can read the repo, ask it to:

Use the Motivation Form MCP server. Read apps/motivation-form/forms/demo-multimedia-survey.md and apps/motivation-form/forms/demo-quiz.md. Deploy both examples with deploy_form; if either file still has `<your-handle>` in the slug, personalize it with my account handle first. Return both public URLs and short URLs.

The agent should call deploy_form for each Markdown file. For a new form created directly from a prompt, use create_form instead.