Input Group Component

Join prefixes, suffixes, and buttons to an input so they read as one control.

moderate Forms & Input

What it adds

A composite control binding an input to adjoining affixes and buttons within a single visual frame.

What your agent is told to do

1
Find the places the app already fakes this — a currency symbol floating beside a number field, a copy button jammed next to a token, a domain suffix drawn as separate text — and rebuild them as one group.
2
Draw the focus treatment around the whole group when any child inside it holds focus, so the composite reads as one control rather than a box beside a button.
3
Give the group one accessible name from the field's label and describe affixes separately; a currency symbol or a unit must be exposed as description, not as a second label.
4
Manage borders and corner radii from the group so the first and last visible children round correctly no matter which affixes are present, including when one is conditionally hidden.
5
Do not let a button inside the group become the form's default submit by accident. Declare each embedded button's behaviour explicitly, because a reveal or copy control that submits the form on Enter is a data-loss bug.

Edge cases it handles

Focus lives on exactly one child at a time, but the invalid, disabled, and focused treatments belong to the frame — a ring drawn only around the inner input looks like a rendering fault.
The affix must not repeat the label; a field labelled Amount in USD with a dollar prefix announces the currency twice to a screen reader.
A group containing more than one control needs per-child validity — a disabled or invalid button inside the group must not make the text input unusable, and vice versa.
Radii and borders must be recomputed when an affix appears or disappears at runtime, or the group will render with a square corner in the middle of a rounded frame.
Long affix content and long input values must not push the group past its container; the input should shrink and the affixes hold their intrinsic width.
Every embedded icon-only button needs an accessible name and a hit area meeting the minimum touch target, even when the group is rendered at compact density.
The label, description, and error text around the group are owned by Form Field Shell — this component owns the inside of the frame only.

Definition of done

Grouped affixes, inputs, and buttons render inside a single continuous frame.
Focus on any child produces one focus treatment on the whole group.
The group carries one accessible name, with affixes exposed as description.
Corner radii and borders remain correct when affixes are added or removed at runtime.
Embedded buttons have explicit behaviour and never submit the form unintentionally.
Icon-only buttons in the group have accessible names and adequate touch targets.
The feature matches the existing design system.
No existing functionality is broken.

Related features

Unit Converter

Voice Dictation

Code Editor Field

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.