Shared Ui Behavior

Before creating a JSX component for an interaction, search the relevant core and part components for existing behavior and an accessibility contract. Reuse matching behavior. If no matching implementation exists and the interaction is domain-neutral, define its state and event handling once in headless core infrastructure, even when the first use is in one part or page. Site core may render reusable domain-neutral controls as headless JSX and semantic HTML. Put domain controls in the appropriate part site and site- or theme-specific controls in their owner. Core and part-site components must leave appearance styles to the consuming site or theme. Panel core may own reusable panel controls. Pass domain data and localized labels through generic props. A reusable clipboard action and its headless copy button may live in site core, with localized labels supplied through props and appearance supplied by the consuming site or theme.

Fix

Reuse matching interaction behavior or define missing domain-neutral behavior in headless core infrastructure. Keep rendered site controls in their owning site, theme, or part site.