A Pattern should tell a product how several components behave together in a recurring flow. It should not be encoded as a giant reusable component simply because the flow appears more than once.
Pattern 01
Forms
Collect
Required if chrome has formsPattern 02Destructive confirm
Slow down
Required if destroy existsPattern 03Publish / irreversible
Go live
Required if product publishesPattern 04Keyboard shortcuts chrome
Power path
RequiredPattern 05List → editor → back
Primary flow
RequiredPattern 06Overlay / command palette
Go somewhere
Required if overlay exists