@mmerterden/multi-agent-pipeline 20.2.0 → 20.3.0

package/pipeline/skills/shared/external/hig-foundations/SKILL.md

@@ -1,94 +1,66 @@
 ---
 name: hig-foundations
-description: "Apple Human Interface Guidelines design foundations. Use when a design decision turns on Apple's foundations: layout, typography, colour, motion, accessibility."
-risk: unknown
-source: community
-date_added: '2026-02-27'
+description: "Apple HIG foundations mapped to SwiftUI: Dynamic Type, semantic color, contrast, safe areas, SF Symbols, materials and Liquid Glass, motion, icons, writing. Use when a design decision turns on Apple's foundations."
+metadata:
+  risk: safe
+  source: multi-agent-pipeline
+  date_added: "2026-09-25"
 ---
 
-# Apple HIG: Design Foundations
+# HIG Foundations
 
-Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
+The foundations are the layer every other Apple design rule sits on: how text
+scales, where color comes from, which icons to use, how content relates to the
+edges of the screen, and how things move. Get these right and most component
+decisions become easy; get them wrong and no component fixes the result.
 
-## Key Principles
+This skill is written for someone building the UI, so each foundation comes
+with the question to ask, the SwiftUI tool that answers it, and what a reviewer
+should look for. The repository's design tokens win over anything here: if the
+project maps `Color.Text.primary` to a semantic color, use the token.
 
-1. **Prioritize content over chrome.** Reduce visual clutter. Use system-provided materials and subtle separators rather than heavy borders and backgrounds.
+## Order of review
 
-2. **Build in accessibility from the start.** Design for VoiceOver, Dynamic Type, Reduce Motion, Increase Contrast, and Switch Control from day one. Every interactive element needs an accessible label.
+When a screen feels off, check foundations in this order. Each step tends to
+hide problems in the steps after it.
 
-3. **Use system colors and materials.** System colors adapt to light/dark mode, increased contrast, and vibrancy. Prefer semantic colors (`label`, `secondaryLabel`, `systemBackground`) over hard-coded values.
+1. Text scales and stays readable at every size.
+2. Colors come from semantic sources and hold up in both appearances.
+3. Content respects safe areas and layout margins.
+4. Icons are symbols with consistent weight and scale.
+5. Materials and motion support the content instead of competing with it.
+6. Copy is short, specific and written in the product's voice.
 
-4. **Use platform fonts and icons.** SF Pro, SF Compact, SF Mono by default. New York for serif. Follow the type hierarchy at recommended sizes. Use SF Symbols for iconography.
+## Details on demand
 
-5. **Match platform conventions.** Align look and behavior with system standards. Provide direct, responsive manipulation and clear feedback for every action.
+Load `references/foundations-detail.md` for each review step above, with the SwiftUI APIs and code for it.
 
-6. **Respect privacy.** Request permissions only when needed, explain why clearly, provide value before asking for data. Design for minimal data collection.
+## Reporting findings
 
-7. **Support internationalization.** Accommodate text expansion, right-to-left scripts, and varying date/number formats. Use Auto Layout for dynamic content sizing.
+For each issue, give the foundation, what the user experiences, and the change:
 
-8. **Use motion purposefully.** Animation should communicate meaning and spatial relationships. Honor Reduce Motion by providing crossfade alternatives.
+```
+[Typography] Order summary total truncates at accessibility sizes.
+Fix: remove lineLimit(1); stack label and value vertically when
+dynamicTypeSize.isAccessibilitySize.
+```
 
-## Topics
+## Related skills
 
-| Topic | Key content |
-|---|---|
-| Accessibility | VoiceOver, Dynamic Type, color contrast, motor accessibility, Switch Control, audio descriptions |
-| App Icons | Icon grid, platform-specific sizes, single focal point, no transparency |
-| Branding | Integrating brand identity within Apple's design language, subtle branding, custom tints |
-| Color | System colors, Dynamic Colors, semantic colors, custom palettes, contrast ratios |
-| Dark Mode | Elevated surfaces, semantic colors, adapted palettes, vibrancy, testing in both modes |
-| Icons | Glyph icons, SF Symbols integration, custom icon design, icon weights, optical alignment |
-| Images | Image resolution, @2x/@3x assets, vector assets, image accessibility |
-| Immersive Experiences | AR/VR design, spatial immersion, comfort zones, progressive immersion levels |
-| Inclusion | Diverse representation, non-gendered language, cultural sensitivity, inclusive defaults |
-| Layout | Margins, spacing, alignment, safe areas, adaptive layouts, readable content guides |
-| Materials | Vibrancy, blur, translucency, system materials, material thickness |
-| Motion | Animation curves, transitions, continuity, Reduce Motion support, physics-based motion |
-| Privacy | Permission requests, usage descriptions, privacy nutrition labels, minimal data collection |
-| Right-to-Left | RTL layout mirroring, bidirectional text, icons that flip, exceptions |
-| SF Symbols | Symbol categories, rendering modes, variable color, custom symbols, weight matching |
-| Spatial Layout | visionOS window placement, depth, ergonomic zones, Z-axis design |
-| Typography | SF Pro, Dynamic Type sizes, text styles, custom fonts, font weight hierarchy, line spacing |
-| Writing | UI copy guidelines, tone, capitalization rules, error messages, button labels, conciseness |
+- `hig-platforms` for how these foundations shift per device.
+- `hig-components-layout`, `hig-components-content` for specific containers.
+- `swiftui-liquid-glass` for the iOS 26 glass APIs in depth.
 
-## Applying Foundations Together
+## References
 
-Consider how principles interact:
-
-1. **Color + Dark Mode + Accessibility** -- Custom palettes must work in both modes while maintaining WCAG contrast ratios. Start with system semantic colors.
-
-2. **Typography + Accessibility + Layout** -- Dynamic Type must scale without breaking layouts. Use text styles and Auto Layout for the full range of type sizes.
-
-3. **Icons + Branding + SF Symbols** -- Custom icons should match SF Symbols weight and optical sizing. Brand elements should integrate without overriding system conventions.
-
-4. **Motion + Accessibility + Feedback** -- Every animation must have a Reduce Motion alternative. Motion should reinforce spatial relationships, not decorate.
-
-5. **Privacy + Writing + Onboarding** -- Permission requests need clear, specific usage descriptions. Time them to when the user will understand the benefit.
-
-## Output Format
-
-1. **Cite the specific HIG foundation** by topic and section.
-2. **Note platform differences** for the user's target platforms.
-3. **Provide concrete code patterns** (SwiftUI/UIKit/AppKit).
-4. **Explain accessibility impact** (contrast ratios, Dynamic Type scaling, VoiceOver behavior).
-
-## Questions to Ask
-
-1. Which platforms are you targeting?
-2. Do you have existing brand guidelines?
-3. What accessibility level are you targeting? (WCAG AA, AAA, Apple baseline?)
-4. System colors or custom?
-
-## Related Skills
-
-- **hig-platforms** -- How foundations apply per platform (e.g., type scale differences on watchOS vs macOS)
-- **hig-patterns** -- Interaction patterns where foundations like writing and accessibility are critical
-- **hig-components-layout** -- Structural components implementing layout principles
-- **hig-components-content** -- Content display using color, typography, and images
-
----
-
-*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
-
-## When to Use
-This skill is applicable to execute the workflow or actions described in the overview.
+- https://developer.apple.com/design/human-interface-guidelines/foundations
+- https://developer.apple.com/design/human-interface-guidelines/typography
+- https://developer.apple.com/design/human-interface-guidelines/color
+- https://developer.apple.com/design/human-interface-guidelines/dark-mode
+- https://developer.apple.com/design/human-interface-guidelines/layout
+- https://developer.apple.com/design/human-interface-guidelines/sf-symbols
+- https://developer.apple.com/design/human-interface-guidelines/materials
+- https://developer.apple.com/design/human-interface-guidelines/motion
+- https://developer.apple.com/design/human-interface-guidelines/app-icons
+- https://developer.apple.com/design/human-interface-guidelines/writing
+- https://developer.apple.com/design/human-interface-guidelines/accessibility

package/pipeline/skills/shared/external/hig-foundations/references/foundations-detail.md

@@ -0,0 +1,132 @@
+# Foundations in detail
+
+Companion to `../SKILL.md` for the `hig-foundations` skill.
+
+## 1. Typography
+
+Ask: if the user sets the largest accessibility text size, does every string
+still fit, wrap or scroll?
+
+- Use text styles (`.font(.body)`, `.headline`, `.caption`) rather than fixed
+  point sizes. Text styles track Dynamic Type automatically.
+- For a custom font, pass `relativeTo:` so it scales with a text style:
+  `.font(.custom("Brand-Regular", size: 17, relativeTo: .body))`.
+- Scale non-text measurements that sit next to text with `@ScaledMetric`, for
+  example an icon frame of 24 points that should grow with the label.
+- Allow wrapping. Avoid `.lineLimit(1)` on primary content; where a single line
+  is required, add `.minimumScaleFactor` only as a last resort.
+- At accessibility sizes, switch horizontal arrangements to vertical. Read
+  `@Environment(\.dynamicTypeSize)` and check `.isAccessibilitySize`, or use
+  `ViewThatFits` to let the layout choose.
+- Keep a clear hierarchy with weight and style, not with many sizes. Two or
+  three styles per screen is usually enough.
+
+Review signal: truncated order totals, overlapping labels, or buttons whose
+titles are clipped at `accessibility3` and above.
+
+## 2. Color
+
+Ask: does this color mean something, and does it still mean it in dark mode,
+with increased contrast, and to someone who cannot distinguish red from green?
+
+- Prefer semantic colors: `.primary`, `.secondary`, `Color(.systemBackground)`,
+  `Color(.secondarySystemBackground)`, `.tint`. They adapt to appearance and
+  contrast settings for free.
+- Define brand colors in the asset catalog with light, dark and high-contrast
+  variants instead of branching on `colorScheme` in code.
+- Set the app accent once with `.tint(...)` near the root; controls pick it up.
+- Never carry meaning by color alone. A failed payment shows an icon and a
+  word, not only a red row.
+- Aim for at least 4.5:1 contrast for body text and 3:1 for large text and
+  essential glyphs.
+
+Review signal: hard-coded hex values, `Color.white` text on a brand color that
+fails contrast in dark mode, status conveyed only by hue.
+
+## 3. Layout, margins and safe areas
+
+Ask: is content kept clear of the status bar, Dynamic Island, home indicator,
+rounded corners and the keyboard, while backgrounds still reach the edges?
+
+- Leave safe areas alone for content; extend only backgrounds with
+  `.ignoresSafeArea()` or `.background(..., ignoresSafeAreaEdges: .all)`.
+- Use `.safeAreaInset(edge:)` for a bottom bar that content should scroll
+  behind, instead of padding by a guessed height.
+- Use `.contentMargins` on scroll views to keep reading width comfortable on
+  iPad and in landscape.
+- Keep interactive targets at least 44 by 44 points on iOS and iPadOS; pad the
+  hit area with `.contentShape` if the visual is smaller.
+- Group related items by proximity and alignment. Reach for a divider only when
+  spacing alone does not separate groups.
+- Adapt to size classes (`@Environment(\.horizontalSizeClass)`) instead of
+  device checks.
+
+## 4. Icons and SF Symbols
+
+Ask: is there a system symbol for this, and does it match the weight of the
+text beside it?
+
+- Use `Image(systemName:)` and `Label` so symbols align with text baselines and
+  scale with Dynamic Type.
+- Pick a rendering mode on purpose: `.symbolRenderingMode(.hierarchical)` for
+  depth, `.palette` for brand pairs, `.multicolor` where the symbol ships it.
+- Use `.symbolVariant(.fill)` for selected states, as tab bars do.
+- Animate state with `.symbolEffect` (bounce on add-to-cart, pulse while
+  syncing) and `.contentTransition(.symbolEffect(.replace))` between glyphs.
+- Custom symbols belong in the asset catalog as symbol templates so they gain
+  weights and scales like system ones.
+
+## 5. Materials, Liquid Glass and depth
+
+Ask: does this layer float above content, and does the content stay legible
+under it?
+
+- On iOS 26 and later, system bars, tab bars, sheets and toolbars adopt Liquid
+  Glass automatically when built with standard SwiftUI containers. Avoid
+  painting opaque backgrounds on them; that removes the effect.
+- For custom floating controls, apply `.glassEffect()` and group neighbors in a
+  `GlassEffectContainer` so shapes blend and morph together. Keep glass for the
+  navigation and control layer, not for content cards.
+- Use `.buttonStyle(.glass)` or `.glassProminent` for floating actions that
+  should match system controls.
+- Before iOS 26, use materials (`.regularMaterial`, `.thinMaterial`) for
+  overlays; gate newer APIs with `if #available(iOS 26, *)`.
+- Respect Reduce Transparency: system materials handle it, custom blurs must
+  check `accessibilityReduceTransparency`.
+
+## 6. Motion
+
+Ask: does this animation explain a change, and what happens when Reduce Motion
+is on?
+
+- Animate to show cause and effect: an item moving into a list, a sheet coming
+  from where it was triggered. Use `matchedGeometryEffect` or
+  `.navigationTransition(.zoom(sourceID:in:))` for continuity.
+- Prefer spring animations (`.smooth`, `.snappy`, `.bouncy`) that can be
+  interrupted.
+- Read `@Environment(\.accessibilityReduceMotion)` and replace large movement
+  with cross-fades.
+- Never block interaction until an animation finishes.
+
+## 7. App icon
+
+- Provide a single 1024 by 1024 source and let Xcode generate sizes; on iOS 18
+  and later supply dark and tinted variants. From iOS 26, author layered icons
+  in Icon Composer so the system can render the glass appearance.
+- Keep the icon a simple, recognizable shape without text or screenshots.
+
+## 8. Writing
+
+- Use the words people use: "Save note", not "Persist entry".
+- Buttons are verbs; alerts say what happened and what the person can do.
+- Keep error text specific and blameless: "This coupon has expired" rather than
+  "Invalid input".
+- Localize every user-facing string and leave room for text that grows by 30 to
+  40 percent in other languages.
+
+## 9. Accessibility, as a foundation
+
+Accessibility is a property of every item above, not a separate pass. A quick
+screen test covers most of it: largest text size, VoiceOver swipe through the
+screen, Increase Contrast, Reduce Motion, and right-to-left pseudo-language.
+Deeper implementation guidance lives in the `ios-accessibility` skill.

package/pipeline/skills/shared/external/hig-inputs/SKILL.md

@@ -1,110 +1,151 @@
 ---
 name: hig-inputs
-description: "Apple Human Interface Guidelines for input methods: touch gestures, keyboards, Apple Pencil, pointing devices, game controllers, Digital Crown and spatial input. Use when designing or reviewing input controls, forms or text entry on an Apple platform."
-risk: unknown
-source: community
-date_added: '2026-02-27'
+description: "Apple HIG for input mapped to SwiftUI: touch gestures, keyboards, pointer, Apple Pencil, focus and game controllers, Digital Crown, eyes and hands, haptics. Use when designing or reviewing input on an Apple platform."
+metadata:
+  risk: safe
+  source: multi-agent-pipeline
+  date_added: "2026-09-25"
 ---
 
-# Apple HIG: Inputs
-
-Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
-
-## Key Principles
-
-### General
-
-1. **Support multiple input methods.** Touch, pointer, keyboard, pencil, voice, eyes, hands, controllers. Design for the inputs available on each platform. On iPadOS, support both touch and pointer; on macOS, both pointer and keyboard.
-
-2. **Consistent feedback for every input action.** Visible, audible, or haptic response.
-
-### Gestures
-
-3. **Standard gestures must behave consistently.** Tap to activate, swipe to scroll/navigate, pinch to zoom, long press for context menus, drag to move. Don't override system gestures (edge swipes for back, Home, notifications).
-
-4. **Use standard recognizers; keep custom gestures discoverable.** Apple's built-in recognizers handle edge cases and accessibility. If you add non-standard gestures, provide hints or coaching to teach them.
-
-### Apple Pencil
-
-5. **Precision drawing, markup, and selection.** Support pressure, tilt, and hover. Distinguish finger from Pencil when appropriate (finger pans, Pencil draws).
-
-6. **Support Scribble in text fields.** Users expect to write with Pencil in any text input.
-
-### Keyboards
-
-7. **Keyboard shortcuts and full navigation.** Standard shortcuts (Cmd+C/V/Z) plus custom ones visible in the iPadOS Command key overlay. Logical tab order.
-
-8. **Respect the software keyboard.** Adjust layout when keyboard appears. Use keyboard-avoidance APIs.
-
-### Game Controllers
-
-9. **MFi controllers with on-screen fallbacks.** Map to extended gamepad profile, sensible defaults, remappable. Always offer touch or keyboard alternatives.
-
-### Pointer and Trackpad
-
-10. **Native feel.** Hover effects, pointer shape adaptation, standard cursor behaviors. Two-finger scroll, pinch to zoom, swipe to navigate.
-
-### Digital Crown
-
-11. **Primary scrolling and value-adjustment input on watchOS.** Scrolling lists, adjusting values, navigating views. Haptic feedback at detents.
-
-### Eyes and Spatial (visionOS)
-
-12. **Look and pinch.** Generous hit targets (eye tracking is less precise than touch). Avoid sustained gaze for activation. Direct hand manipulation in immersive experiences.
-
-### Focus System
-
-13. **Critical for tvOS and visionOS.** Predictable focus movement. Every interactive element focusable. Clear visual indicators (scale, highlight, elevation). Logical focus groups.
-
-### Remotes
-
-14. **Siri Remote: limited surface.** Touch area for swiping, clickpad for selection, few physical buttons. Keep interactions simple.
-
-### Motion and Nearby
-
-15. **Gyroscope, accelerometer, UWB: use judiciously.** Suits gaming, fitness, AR. Not for essential tasks. Provide calibration and reset. For UWB, communicate distance and direction with visual or haptic cues.
-
-## Topics
-
-| Topic | Key content |
-|---|---|
-| Touch gestures | Tap, swipe, pinch, long press, drag, system gestures |
-| Apple Pencil | Precision, pressure, tilt, hover, handwriting |
-| Keyboards | Shortcuts, navigation, software keyboard, Command key |
-| Game controllers | MFi, extended gamepad, remapping, fallbacks |
-| Pointer/trackpad | Hover, cursor morphing, trackpad gestures |
-| Digital Crown | Scrolling, value adjustment, haptic detents |
-| Eye tracking | Look and tap, gaze targeting, hit target sizing |
-| Spatial input | Hand gestures, direct manipulation, immersive input |
-| Focus system | tvOS/visionOS navigation, focus indicators, groups |
-| Remotes | Touch surface, clickpad, simple interactions |
-| Motion sensors | Gyroscope, accelerometer, calibration, gaming |
-| Nearby interactions | U1 chip, directional finding, proximity triggers |
-| Camera Control | iPhone camera hardware button, quick launch |
-
-## Output Format
-
-1. **Input method recommendations by platform** and how they interact.
-2. **Gesture specification table** -- standard and custom gestures with expected behaviors.
-3. **Keyboard shortcut recommendations** following system conventions.
-4. **Accessibility input alternatives** for VoiceOver, Switch Control, etc.
-
-## Questions to Ask
-
-1. Which platforms and input devices?
-2. Productivity or casual app?
-3. Custom gestures in the design?
-4. Game controller support needed?
-
-## Related Skills
-
-- **hig-components-status** -- Progress indicators responding to input (pull-to-refresh)
-- **hig-components-system** -- System experiences with unique input constraints
-- **hig-technologies** -- VoiceOver, Siri voice input, ARKit spatial gesture context
-
----
-
-*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
-
-## When to Use
-This skill is applicable to execute the workflow or actions described in the overview.
+# HIG Inputs
+
+People reach the same app with fingers, a trackpad, a keyboard, a pencil, a
+remote, a crown, or their eyes. The design goal is that every task can be done
+with whichever input the person has, and that each input feels native rather
+than emulated. This skill covers what each input expects and how SwiftUI
+supports it.
+
+## The baseline rule
+
+Any action exposed only through a gesture must also be reachable some other
+way: a button, a menu item, a context menu, or an accessibility action. Gestures
+are shortcuts, not the only door.
+
+Checklist for a new interactive element:
+
+- Is there a visible control or menu entry for it?
+- Does it respond to touch, pointer and keyboard where the platform has them?
+- Does VoiceOver expose it (label, trait, and custom actions for swipes)?
+- Is the hit area at least 44 by 44 points (about 60 on visionOS)?
+- Is there feedback: a visual change, and a haptic where it adds meaning?
+
+## Touch gestures
+
+- Use standard gestures with their standard meanings: tap to activate, swipe to
+  reveal row actions, long press for a context menu, pinch to zoom, edge swipe
+  to go back. Do not repurpose them.
+- Prefer built-in behavior over custom recognizers: `.swipeActions` on list
+  rows, `.contextMenu` for long press, `.refreshable` for pull to refresh.
+- For custom gestures use `DragGesture`, `MagnifyGesture` and `RotateGesture`
+  and compose with `.simultaneously(with:)` or `.exclusively(before:)`.
+- Do not fight the system: leave screen edges and the home indicator area to
+  system gestures.
+- Give custom gestures an accessibility equivalent with
+  `.accessibilityAction(named:)`.
+
+## Keyboards
+
+On-screen keyboard:
+
+- Choose the keyboard and content type so AutoFill and suggestions work:
+  `.keyboardType(.decimalPad)` for a quantity, `.textContentType(.oneTimeCode)`
+  for a verification code.
+- Set `.submitLabel` and move focus with `@FocusState` so Return advances
+  through a form.
+- Keep the focused field visible above the keyboard; SwiftUI's safe area
+  handles this if you do not disable keyboard avoidance.
+- Dismiss with `.scrollDismissesKeyboard(.interactively)` on scrolling forms.
+
+Hardware keyboard (iPad, Mac, visionOS):
+
+- Add shortcuts with `.keyboardShortcut("n", modifiers: .command)` for common
+  commands such as a new note; list them in `.commands` so they appear in the
+  menu bar and the iPad shortcut overlay.
+- Do not override system shortcuts (Command-C, Command-Q, Command-Tab).
+- Support full keyboard navigation: focusable controls, visible focus rings,
+  `.onKeyPress` for arrow-key movement in custom views.
+
+## Pointer and trackpad
+
+- On iPad and Mac, controls should react to hover. Standard buttons do; custom
+  views use `.hoverEffect(.highlight)` or `.onHover`.
+- Offer context menus on secondary click (the same `.contextMenu` serves long
+  press and right click).
+- Support precise interactions the pointer enables: multi-select, drag to
+  reorder, resizing, tooltips via `.help`.
+- Use `.pointerStyle` (iPadOS 18 and macOS 15 and later) to signal resize or
+  precision regions.
+
+## Apple Pencil
+
+- Pencil is for drawing, writing and precise marking; do not require it.
+- Use PencilKit (`PKCanvasView`) for inking rather than a custom renderer.
+- Scribble lets people handwrite into any standard text field; do not block it
+  with custom text input.
+- Handle the double tap and squeeze gestures through
+  `.onPencilDoubleTap` and `.onPencilSqueeze`, respecting the preferred action
+  the person set in Settings.
+- Show hover previews on supported iPads when the pencil approaches.
+
+## Focus-driven input: Apple TV, keyboard navigation, game controllers
+
+- Every interactive element must be focusable and show a clear focused state.
+- Shape movement with `.focusSection()` so focus jumps between logical groups
+  rather than scanning element by element.
+- Set a sensible starting focus with `.defaultFocus`.
+- The Siri Remote touch surface swipes and clicks; Menu or Back always goes back.
+- For games, use the Game Controller framework, support standard button
+  mappings, and show on-screen touch controls when no controller is attached.
+
+## Digital Crown
+
+- The crown scrolls by default. For value adjustment bind it with
+  `.digitalCrownRotation($value, from:through:by:sensitivity:)`.
+- Pair crown changes with haptic detents so each step is felt.
+- Keep crown use predictable: the same rotation direction increases values
+  throughout the app.
+
+## Eyes and hands (visionOS)
+
+- People look at an element to target it and pinch to activate. Standard
+  controls show the system hover effect automatically; custom views need
+  `.hoverEffect()` and a `.contentShape` matching their visual shape.
+- Keep targets well separated and avoid placing them at the edges of vision.
+- Direct touch works for content within reach; design for both.
+- Avoid actions triggered by gaze alone; always require a pinch or tap.
+
+## Haptics and motion input
+
+- Use haptics to confirm meaningful events, not every tap:
+  `.sensoryFeedback(.selection, trigger: selectedSize)` in a picker,
+  `.success` when an order is placed.
+- Shake is reserved for undo; avoid other shake gestures.
+- Motion-based input (tilt) needs a non-motion alternative.
+
+## Review output
+
+```
+[Gesture] Archiving a task is only possible by swiping.
+Fix: add an Archive button to the row's context menu and an
+accessibilityAction(named: "Archive").
+```
+
+## Related skills
+
+- `hig-platforms` for which inputs each device has.
+- `hig-components-system` for menus, controls and text fields.
+- `swiftui-gestures` for gesture implementation detail.
+- `pencilkit-drawing` for Apple Pencil canvases.
+
+## References
+
+- https://developer.apple.com/design/human-interface-guidelines/inputs
+- https://developer.apple.com/design/human-interface-guidelines/gestures
+- https://developer.apple.com/design/human-interface-guidelines/keyboards
+- https://developer.apple.com/design/human-interface-guidelines/pointing-devices
+- https://developer.apple.com/design/human-interface-guidelines/apple-pencil-and-scribble
+- https://developer.apple.com/design/human-interface-guidelines/focus-and-selection
+- https://developer.apple.com/design/human-interface-guidelines/digital-crown
+- https://developer.apple.com/design/human-interface-guidelines/game-controls
+- https://developer.apple.com/design/human-interface-guidelines/eyes
+- https://developer.apple.com/design/human-interface-guidelines/playing-haptics