Restore the overlay-clipping rule to operate.md

Deleting interaction-design.md took the last copy of
skill-interaction-dropdown-clipping with it. harden.md's `overflow:
hidden` hits are code samples, not the rule.

It lands in operate.md's Components list rather than the craft floor:
dropdowns and overlays are dense-product-UI components, and the floor
just lost 25% of its length for being a place where specifics accumulate.
The detector's clipped-overflow-container rule catches this after the
fact, but only in sessions with a hook.

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Paul Bakaus
2026-07-21 02:35:41 -07:00
co-authored by Claude
parent cd4d710cf1
commit a9540b5fe3
+1
View File
@@ -34,6 +34,7 @@ Every interactive component has: default, hover, focus, active, disabled, loadin
- Skeleton states for loading, not spinners in the middle of content. <!-- rule:product-components-skeleton-loading -->
- Empty states that teach the interface, not "nothing here." <!-- rule:product-components-empty-states -->
- Consistent affordances across the surface. Same button shape. Same form-control vocabulary. Same icon style. <!-- rule:product-components-consistent-affordances -->
- Overlays escape their container. An absolutely positioned dropdown inside an `overflow: hidden` or `overflow: auto` ancestor gets clipped; reach for `<dialog>`, the popover API, `position: fixed`, or a portal. <!-- rule:skill-interaction-dropdown-clipping -->
## Motion