Canonical contexts: chat threads, customer-support conversations, peer-to-peer messaging, and comment composers docked to the bottom of a scroll view.

• Icon frames are generically named container. Both the leading (plus/attach) and trailing (send) slots share the layer name container, so Code Connect can't tell leading from trailing. Should be semantic: leading / trailing (or attach-slot / send-slot) to match native HStack ordering. C1 · Layer Structure & Naming
• Boolean uses yes/no and misnames the intent. active=yes/no cannot map to Swift Bool / Kotlin Boolean without a translation layer, and active is ambiguous — the true meaning is "inner field is focused". The property is redundant with the inner Input Field's State=Active. C2 · Variant & Property Naming
• Composer maps to three native siblings, not a single primitive. iOS and Android both compose this pattern as HStack { Button + TextField + Button } / Row { IconButton + OutlinedTextField + IconButton }. Shipping Chat Field as a single Figma component with a private active boolean hides that composition from Code Connect, making 1:1 mapping impossible. C4 · Native Mappability
• 2 variants cover less state than the inner Input Field already has. Input Field ships 8 variants (State × isFilled). Chat Field wraps it but collapses the surface to a single Active toggle — Error, Disabled, and the Default-but-filled case are unreachable through Chat Field. C5 · Interaction State Coverage
• Leading and trailing icons are raster PNGs. Both Add_Full (plus, 32×32) and Send Message Medium (paper-plane, 32×32) are referenced via PNG asset URLs (imgShapeFull / imgShapeFull1). Native platforms ship vector SF Symbols (plus, paperplane.fill) / Material icons (Add, Send); the rasters cannot tint, scale, or accept token-based color. C6 · Asset & Icon Quality
• Code Connect mappings not registered. Blocked by the composition decision, property rename, and icon vectorization. Once the composer is rebuilt as Input Field + two Icon Button slots, mapping is a direct pass-through to the sibling components' own Code Connect entries. C7 · Code Connect Linkability

• Rename to Chat Composer (or Message Composer) and rebuild as a composed pattern. Target schema: a 3-slot layout — leadingAction (Icon Button instance), field (Input Field instance with multiline/lineLimit 1…5 per the Text Area consolidation), trailingAction (Icon Button instance). Drop the active boolean — focus comes from the nested field. Result: 0 net variants on the composer, full field state matrix inherited, and both icons become recomposable. Family
• Rename active=yes/no away. If the composer keeps any boolean at all, use semantic naming tied to a real affordance — e.g. sendEnabled: true/false — and let the field's own focus state carry the focused appearance. Rename
• Expose leadingAction and trailingAction as Figma Slots. Consumers will need to swap plus for camera, microphone, or emoji entry points, and paper-plane for voice-note-record without forking the component. Slots also let the layer names convey leading vs trailing, fixing C1. Slot
• Vectorize both action glyphs. Replace the PNG Add_Full and Send Message Medium with vector icon components tinted via main/chat-field/color/icon. Aligns with the token that already exists and with SF Symbols / Material icons on native. Asset
• Add a send-disabled visual for empty fields. Common chat pattern: the send icon dims to ~40% opacity or a muted token when the field has no text. Currently not representable. Covered naturally by exposing trailingAction as an Icon Button slot with its own enabled/disabled variant. State
• Document a Chat component family. This is the first component in the Chat group. Plan siblings now: Chat Bubble (sent/received), Chat Bubble (with attachment), Chat Typing Indicator, Chat Date Separator. Defining the family shape now prevents each bubble from being drawn ad-hoc in product files. Family