Prompt · Intermediate

Prompt for an accessible contact form

Generate a labeled contact form with server-trust boundaries, recoverable errors, privacy context, and no fake delivery state.

Author: Editorial team
Reviewer: Publication review pending
Review tier: 180-day

Version 1.0.0 · components

Variables

[FORM_PURPOSE] · Form purpose: Why information is being collected. Required.
[REQUIRED_FIELDS] · Required fields: The minimum necessary information. Required.
[DELIVERY_STATE] · Delivery state: The real configured endpoint or explicit demo-only state. Required.

Expected output

Field Contract
Html
Css
Enhancement
Server Contract
Tests

Common failures

Placeholder Only labels
Client Only trust
Lost values on error

Compatible modes: Chat, Agent, Ide Assistant

Design a contact form for [FORM_PURPOSE]. Collect only [REQUIRED_FIELDS]. The
actual delivery state is [DELIVERY_STATE].

Start with a field contract listing purpose, type, label, autocomplete value,
required state, validation rule, error wording, and retention need. Use
persistent labels, fieldset and legend for groups, useful input types, and a
real submit button.

Create an HTML baseline, mobile-first CSS, and optional client enhancement.
Server validation remains authoritative. Preserve safe input after errors,
associate messages with fields, provide an error summary, and announce final
status without moving focus unpredictably.

Do not claim delivery unless [DELIVERY_STATE] names a configured endpoint. Do
not collect passwords, payment data, or unnecessary personal information.
Return the server contract, rate-limit and spam assumptions, privacy copy, and
keyboard/error-recovery tests.

Complete prompt

Design a contact form for [FORM_PURPOSE]. Collect only [REQUIRED_FIELDS]. The
actual delivery state is [DELIVERY_STATE].

Start with a field contract listing purpose, type, label, autocomplete value,
required state, validation rule, error wording, and retention need. Use
persistent labels, fieldset and legend for groups, useful input types, and a
real submit button.

Create an HTML baseline, mobile-first CSS, and optional client enhancement.
Server validation remains authoritative. Preserve safe input after errors,
associate messages with fields, provide an error summary, and announce final
status without moving focus unpredictably.

Do not claim delivery unless [DELIVERY_STATE] names a configured endpoint. Do
not collect passwords, payment data, or unnecessary personal information.
Return the server contract, rate-limit and spam assumptions, privacy copy, and
keyboard/error-recovery tests.

Common AI mistakes

Reject placeholder-only labels, instant validation before input, messages rendered as HTML, detailed provider errors, and success screens with no verified delivery.

Verification checklist

Complete the form with a keyboard, force server and client failures, confirm safe fields persist, and compare actual collection with the privacy notice.