• The task and expected outcome are clear, with a reproducible example.
• Public exports, props, defaults, and supported variants match the installed declaration and implementation.
• Controlled and uncontrolled value ownership is explicit.
• Callback values, ordering, cancellation, and no-op behavior are covered where applicable.
• Any compatibility change is documented; a shared name with SwiftUI does not imply equivalent behavior.

• The rendered element and accessible role fit the task.
• Controls have accessible names and visible labels where useful.
• Keyboard activation, focus visibility, disabled and loading behavior are reviewed.
• Overlay changes cover dismissal, background interaction, initial focus, and focus restoration.
• Errors, progress, and selection are understandable without color alone.
• Application-owned behavior, including persistence and error recovery, is identified separately.

• Both themes and relevant contrast or motion preferences have been reviewed.
• Narrow layouts, enlarged text, and long labels remain usable.
• The component is checked over realistic content, including translucent backgrounds.
• Styling follows public tokens and supported props; generated CSS is updated through its owner when needed.
• Examples use meaningful labels and original or appropriately licensed assets.

• A behavioral change has a focused regression test and follows the repository's test-first policy.
• Specifications, stories, and documentation describe the same contract.
• Relevant package checks and repository gates have results attached to the change.
• Package changes are checked through the repository's packed-consumer workflow when applicable.
• Captures identify the revision, browser, viewport, and theme.
• Unavailable checks, evidence gaps, and follow-up work are stated explicitly.

See Contributing overview for commands and Enhancing components for applying the checklist to an existing component.