---
name: markdownto-form
description: Author, repair, validate, and review portable form documents and their rendered results.
---
# Working with form
Use this skill when the user wants the form workflow. Read [SPEC.md](SPEC.md), then [shared conventions](../conventions.md). Published equivalents live at https://markdownto.ai/specs/form.md and https://markdownto.ai/specs/conventions.md. The spec and fixtures govern conformance; this editorial guidance is non-normative and adapts to the user's brief.
## Author and repair
Confirm the purpose from the request, inspect any supplied references, and preserve supplied content and constraints. Start from a relevant valid fixture, not a remembered grammar. Write the envelope and meaningful `##` sections, then sparse direction. Avoid invented IDs. Run `mdto validate file.md` after edits. Repair diagnostics at their reported location using the spec's rationale; preserve unrelated source. Prefer the spec-owned verbs for state changes and preview their diff when useful. If the CLI is unavailable, perform a clearly labeled manual check against the spec and do not claim tool validation.
## Editorial judgment
Start from the decision the answers will inform. Ask only what is needed; use optional by default and explain required fields. Labels should make sense without placeholder text. Put easier questions first, keep one concept per question, and explain format or bounds near the field. Use neutral, exhaustive, non-overlapping choices and avoid leading wording. Include an honest consent question only when the workflow requires consent; false must remain a meaningful answer. Test empty, partial, zero, false, long, Unicode and completed responses. Check keyboard order, visible focus, field-associated errors, and download/reopen. Distinguish saving a local response from submitting it to anyone; never claim a server received answers when only a file was saved.
## Review and delivery
Use `mdto render file.md` and the spec's build or review verbs. Inspect the actual resulting interface or artifact, including mobile/narrow views, keyboard controls and content extremes. Verify state-changing UI actions against the same CLI operations. Deliver the Markdown and usable output, explain any real limitation, and never equate a valid file with a successful artifact review. If artifact inspection is unavailable, say which checks remain undone.
Give this guide to your agent, or read it as an author. It covers workflow and editorial judgment; the specification defines conformance.
Use this skill when the user wants the form workflow. Read SPEC.md, then shared conventions. Published equivalents live at https://markdownto.ai/specs/form.md and https://markdownto.ai/specs/conventions.md. The spec and fixtures govern conformance; this editorial guidance is non-normative and adapts to the user's brief.
Author and repair
Confirm the purpose from the request, inspect any supplied references, and preserve supplied content and constraints. Start from a relevant valid fixture, not a remembered grammar. Write the envelope and meaningful ## sections, then sparse direction. Avoid invented IDs. Run mdto validate file.md after edits. Repair diagnostics at their reported location using the spec's rationale; preserve unrelated source. Prefer the spec-owned verbs for state changes and preview their diff when useful. If the CLI is unavailable, perform a clearly labeled manual check against the spec and do not claim tool validation.
Editorial judgment
Start from the decision the answers will inform. Ask only what is needed; use optional by default and explain required fields. Labels should make sense without placeholder text. Put easier questions first, keep one concept per question, and explain format or bounds near the field. Use neutral, exhaustive, non-overlapping choices and avoid leading wording. Include an honest consent question only when the workflow requires consent; false must remain a meaningful answer. Test empty, partial, zero, false, long, Unicode and completed responses. Check keyboard order, visible focus, field-associated errors, and download/reopen. Distinguish saving a local response from submitting it to anyone; never claim a server received answers when only a file was saved.
Review and delivery
Use mdto render file.md and the spec's build or review verbs. Inspect the actual resulting interface or artifact, including mobile/narrow views, keyboard controls and content extremes. Verify state-changing UI actions against the same CLI operations. Deliver the Markdown and usable output, explain any real limitation, and never equate a valid file with a successful artifact review. If artifact inspection is unavailable, say which checks remain undone.