Required Field Indicator

Make it obvious which fields must be filled in and which may be left alone.

simple Forms & Input

What it adds

A consistent marking of required and optional fields across every form in the app.

What your agent is told to do

1
Count the required and optional fields across the app's forms and pick the convention that marks the minority — if most fields are required, mark the optional ones instead.
2
Apply the chosen convention to every form without exception, and state the convention once at the top of each form so the marker means something to a first-time reader.
3
Expose the requirement to assistive technology as well as visually, so the control itself reports that it is required rather than relying on a symbol beside the label.
4
Recompute the marking when requirements change at runtime — a field that becomes mandatory once a plan or a country is selected must gain its marker and its announcement immediately.
5
Do not mark a read-only, disabled, or system-populated field as required. It tells the user to act on something they cannot touch, and it makes the marker untrustworthy everywhere else.

Edge cases it handles

A bare asterisk carries no meaning to a screen reader and is often skipped entirely; the requirement must be on the control, not only in the label's punctuation.
The form-level legend explaining the convention must match what the fields actually do, and a form that mixes required-marking with optional-marking teaches the user nothing.
Requirements that change mid-form must update the marker, the accessible state, and the validation rule together — a field that validates as required but shows no marker looks like a bug.
A field that is required by the server but not marked in the interface produces an error the user could not have anticipated; the marking must reflect the actual validation.
A field required only in one branch of a conditional flow must lose its marker when that branch is not active, rather than staying marked and blocking submission invisibly.
The marker must not be conveyed by colour alone, and it must survive at compact density without colliding with a long label.
How the marker is placed in the label and linked to the control is owned by Form Field Shell; this entry owns which fields are marked and what the convention is.

Definition of done

One convention — marking required or marking optional — is used across every form.
Each form states its convention once, visibly.
Requirements are exposed programmatically on the control, not only as a visual symbol.
Marking matches the validation actually enforced on submission.
Requirements that change at runtime update the marker and the accessible state together.
Read-only, disabled, and system-populated fields are never marked required.
The feature matches the existing design system.
No existing functionality is broken.

Related features

Unit Converter

Code Editor Field

Voice Dictation

How it works

1

Copy the link

Grab the Markdown instruction URL for this feature.
2

Give it to your AI

Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
3

It inspects, then implements

Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.