@mmerterden/multi-agent-pipeline 20.17.0 → 20.17.2

package/pipeline/skills/shared/external/hig-app-icons/references/icon-workflow.md

@@ -0,0 +1,115 @@
+# Icon workflow
+
+Steps for building, wiring and checking an iOS app icon, with the asset
+catalog route for projects that cannot move to Icon Composer yet.
+
+## Contents
+
+1. Preparing artwork
+2. Building the icon in Icon Composer
+3. Adding it to Xcode
+4. The asset catalog route
+5. Alternate icons end to end
+6. Review checklist
+
+## 1. Preparing artwork
+
+- Start from the app icon template in Apple Design Resources, or set the
+  canvas to 1024x1024 px (1088x1088 px for Apple Watch).
+- Draw layers back to front. Give them names with increasing numbers so they
+  import in order.
+- Split colours, text and graphics you may want to adjust per appearance or
+  platform into their own layers.
+- Convert text to outlines; SVG does not keep fonts.
+- Remove blurs, shadows, specular and opacity effects, background colours and
+  gradients. These are set in Icon Composer, where their interaction with
+  Liquid Glass can be previewed.
+- Export SVG. Use PNG for content SVG cannot represent. Do not export the
+  canvas mask.
+
+Fully opaque layers with transparency adjusted later in Icon Composer give the
+most control over how glass and transparency combine.
+
+## 2. Building the icon in Icon Composer
+
+1. Open Icon Composer (Xcode > Open Developer Tool > Icon Composer, or the
+   standalone download) and save the file with the name the project will use,
+   for example `AppIcon`.
+2. In the Document inspector, limit platforms to the ones the app ships on;
+   unused platform controls disappear.
+3. Drag the exported files into the sidebar. Folders become groups. Arrange
+   them into no more than four groups; the system renders groups as the depth
+   layers, bottom to top in sidebar order.
+4. Background: under Color, choose Solid or Gradient for the icon itself.
+   Importing a background image is rarely needed; if used, it must be
+   full-bleed and opaque.
+5. Liquid Glass per group: Mode (Individual or Combined), Specular
+   (Automatic, Inside, Outside, Off), then Blur, Refraction, Translucency and
+   Shadow. A layer can opt out with the Effects toggle.
+6. Appearances: use the canvas controls to preview Default, Dark and Mono.
+   Mono's options preview clear and tinted, light and dark, with any tint
+   colour. Use Vary for appearance on a setting to give one look its own
+   value; everything else inherits.
+7. Platforms: Composition settings (position, scale) can vary per platform
+   while colour and glass stay consistent.
+8. Preview against your own backgrounds (Background Image in the toolbar) and
+   compare rendering across system generations with the Effects controls.
+
+## 3. Adding it to Xcode
+
+- Drag the Icon Composer file into the target's folder in the Project
+  navigator.
+- In the target's General tab, under App Icons and Launch Screen, set App
+  Icon to the file name without its extension.
+- Several Icon Composer files can live in a project (alternates); only the one
+  named in App Icon is the primary.
+- When the deployment target includes releases without Liquid Glass icons,
+  Xcode generates look-alike flat images for them at build time. To keep the
+  previous icon on those releases, stay on the asset catalog.
+
+## 4. The asset catalog route
+
+Used for tvOS and visionOS image stacks, and for iOS projects that keep their
+existing icon on older releases.
+
+- Asset catalog, add OS variant > App Icon.
+- In the Attributes inspector choose **Single Size** for iOS: one 1024x1024 px
+  image, and Xcode generates the rest. Choose All Sizes only when a size truly
+  needs hand-tuned detail.
+- Appearance: Any, Dark, Tinted. Provide the dark icon with a transparent
+  background (the system draws the backdrop) and the tinted icon as a
+  grayscale image. Leaving them empty uses the system's automatic treatment.
+
+## 5. Alternate icons end to end
+
+1. Create one Icon Composer file per alternate, each with its own dark, clear
+   and tinted treatment, and add them to the target.
+2. Build settings, Asset Catalog Compiler - Options: set **Alternate App Icon
+   Sets** to the alternates' names, or in an `.xcconfig`:
+
+   ```
+   ASSETCATALOG_COMPILER_ALTERNATE_APPICON_NAMES = AppIcon-Night AppIcon-Mono
+   ```
+
+3. Leave `CFBundleIcons`, `CFBundlePrimaryIcon` and `CFBundleAlternateIcons`
+   to Xcode; it generates them from those settings.
+4. Offer the choice in the app's own settings UI with a preview of each icon,
+   and call `setAlternateIconName(_:)` from the person's selection. Handle the
+   error, and reflect `alternateIconName` as the current selection.
+5. Each alternate is reviewed by App Review like the primary icon.
+
+In visionOS, compatible iPhone and iPad apps can still switch icons; apps
+built with the visionOS SDK cannot, and the call has no effect there.
+
+## 6. Review checklist
+
+- [ ] Layers are square and unmasked; nothing important near the edges.
+- [ ] No baked shadows, glows, bevels or highlights.
+- [ ] Recognisable in default, dark, clear and tinted looks, light and dark.
+- [ ] Same core features in every appearance.
+- [ ] No text unless essential; no Apple hardware; no SF Symbols.
+- [ ] Crisp at small sizes (Settings, notifications, Spotlight).
+- [ ] App Icon name in General matches the Icon Composer file.
+- [ ] Alternates listed in Alternate App Icon Sets, each with its variants.
+- [ ] Archive passes `ios_app_store_audit` asset-validation.
+- [ ] Icons, alternates and in-app purchase icons suit a 4+ audience.

package/pipeline/skills/shared/external/hig-components-layout/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hig-components-layout
-description: "Apple HIG for app structure mapped to SwiftUI: tab bars, split views, navigation stacks, toolbars, sheets, popovers, alerts, windows, iOS 26 Liquid Glass bars. Use when designing layout and navigation on an Apple platform."
+description: "Apple HIG app structure mapped to SwiftUI: tab bars, sidebars, split views, toolbars, sheets and popovers, including the iOS 26 and 27 tab and toolbar APIs. Use when choosing navigation structure or laying out tab bars and toolbars."
 metadata:
   risk: safe
   source: multi-agent-pipeline
@@ -30,9 +30,32 @@ A tab bar switches context and never navigates within one; do not use a tab
 to trigger an action like "new note". A sidebar-adaptable `TabView` gives a
 tab bar on iPhone and a sidebar on iPad and Mac from one declaration.
 
+## Bars on iOS 26 and 27
+
+Tab bars, toolbars, navigation bars and sidebars float in a Liquid Glass layer
+over the content. Keep destinations and actions in that layer and content
+underneath, and remove custom bar backgrounds: they cover the glass and the
+scroll edge effect.
+
+| Need | API (since) |
+|---|---|
+| Tab bar recedes while reading | `.tabBarMinimizeBehavior(.onScrollDown)` (iOS 26) |
+| Persistent mini player or status above the tab bar | `.tabViewBottomAccessory { }` (iOS 26), `isEnabled:` form (iOS 26.1) |
+| Search as its own tab, set apart at the trailing end | `Tab(role: .search)` (iOS 18; placement iOS 26) |
+| One emphasized tab | `role: .prominent` (iOS 27) |
+| Separate toolbar groups | `ToolbarSpacer(.fixed)` (iOS 26) |
+| Actions that always sit in overflow | `ToolbarOverflowMenu { }` (iOS 27) |
+| Which items survive a narrow bar | `.visibilityPriority(.high)` (iOS 27) |
+| An item that never leaves the trailing edge | `.topBarPinnedTrailing` (iOS 27) |
+| Navigation bar recedes on scroll | `.toolbarMinimizationBehavior(.onScrollDown, for: .navigationBar)` (iOS 27) |
+
 ## Details on demand
 
-Load `references/containers.md` for tab bars, sidebars, navigation bars, toolbars, scroll views, windows and size adaptation, with SwiftUI examples.
+- `references/bars-and-tabs.md`: the APIs above with code, search
+  placement, toolbar grouping rules, overflow and minimization, and a
+  checklist.
+- `references/containers.md`: sidebars, navigation stacks, scroll views,
+  windows and size adaptation, with SwiftUI examples.
 
 ## Modality: sheets, popovers, alerts
 
@@ -60,7 +83,9 @@ happen now, and always give an obvious way out.
 - Is the top-level structure chosen from the number and use of peer areas?
 - Does every tab keep its own state, and is no tab used as an action?
 - Do modals have a clear cancel, and is unsaved work protected?
-- Does content run under glass bars rather than behind opaque fills (iOS 26)?
+- Does content run under glass bars, with no custom bar backgrounds (iOS 26)?
+- Are iOS 27 bar APIs gated with `#available`, and is at most one tab
+  prominent?
 - Are toolbar items declared with semantic placements?
 - Does the layout adapt across size classes, windows and orientations?
 
@@ -69,7 +94,10 @@ happen now, and always give an obvious way out.
 - `hig-components-content` for lists, grids, charts inside these containers.
 - `hig-patterns` for flows such as first launch, search and settings.
 - `hig-platforms` for per-platform differences.
-- `swiftui-navigation` and `swiftui-liquid-glass` for implementation detail.
+- `swiftui-navigation` for navigation implementation.
+- `swiftui-liquid-glass` for the glass material itself.
+- `hig-platforms` (`references/ipad-layout.md`) for iPad windowing and size
+  classes.
 
 ## References
 

package/pipeline/skills/shared/external/hig-components-layout/evals/evals.json

@@ -0,0 +1,47 @@
+{
+  "skill_name": "hig-components-layout",
+  "evals": [
+    {
+      "id": 0,
+      "name": "music-style-tab-bar",
+      "prompt": "Podcast app, SwiftUI, deployment target iOS 26. Tabs: Home, Library, Downloads, Search, plus a 'Record' tab that opens the recorder sheet. We paint the tab bar with a purple UITabBarAppearance background and want a mini player like Apple Music that stays above the tab bar and shrinks when you scroll. How should we set this up?",
+      "expected_output": "Removes the custom tab bar background so the floating Liquid Glass tab bar and scroll edge effect work. Uses Tab with Tab(role: .search) for search, set apart at the trailing end. Moves 'Record' out of the tab bar because a tab is not an action (toolbar button or other entry point). Uses .tabViewBottomAccessory for the mini player and .tabBarMinimizeBehavior(.onScrollDown), and adapts the accessory with the tabViewBottomAccessoryPlacement environment value (.inline vs .expanded).",
+      "files": [],
+      "expectations": [
+        "Removes the custom purple tab bar background",
+        "Uses Tab(role: .search) for the search tab",
+        "Says the Record tab should not be a tab because tabs are not actions",
+        "Uses .tabViewBottomAccessory for the mini player",
+        "Uses .tabBarMinimizeBehavior(.onScrollDown) and adapts the accessory via tabViewBottomAccessoryPlacement"
+      ]
+    },
+    {
+      "id": 1,
+      "name": "crowded-toolbar-ios27",
+      "prompt": "Our document editor's navigation bar on iPhone has Undo, Redo, Share, Comment, Format, Export, Print and Done buttons and half of them get clipped. We can require iOS 27 for this redesign. What should the toolbar look like in SwiftUI?",
+      "expected_output": "Reduces and groups items (aim for at most three groups) with ToolbarSpacer, keeps one primary Done action on the trailing side using Button(role: .confirm) or confirmationAction placement, moves rarely used actions such as Export and Print into ToolbarOverflowMenu, ranks the rest with .visibilityPriority so important items stay, and may pin a key item with .topBarPinnedTrailing. Uses symbols with accessibility labels and avoids a hand-made overflow Menu and custom bar backgrounds.",
+      "files": [],
+      "expectations": [
+        "Uses ToolbarOverflowMenu for rarely used actions such as Export and Print",
+        "Uses .visibilityPriority to control which items move to overflow first",
+        "Keeps a single primary Done/confirm action on the trailing side",
+        "Groups related items with ToolbarSpacer and keeps the number of groups small",
+        "Mentions .topBarPinnedTrailing or explains that iOS 27 APIs need iOS 27 availability"
+      ]
+    },
+    {
+      "id": 2,
+      "name": "structure-choice-ipad",
+      "prompt": "Field-service app: Jobs, Map, Inventory, Messages, Reports, Settings, Team, Timesheets and Documents. iPhone and iPad. Each job has a detail with parts and photos. Should this be tabs, a sidebar or something else, and how do we present 'Log time' and the job detail?",
+      "expected_output": "With nine peer areas recommends a sidebar-adaptable TabView (tab bar on iPhone with five or fewer primary tabs, sidebar on iPad) or NavigationSplitView, keeps Settings out of the main tabs or in a sidebar section, uses NavigationSplitView or NavigationStack for job list to detail, presents 'Log time' as a sheet with Cancel and Save and protects unsaved input with interactiveDismissDisabled, and avoids stacking modals.",
+      "files": [],
+      "expectations": [
+        "Recommends .tabViewStyle(.sidebarAdaptable) or a NavigationSplitView sidebar for the many areas on iPad",
+        "Keeps the iPhone tab bar to about five tabs and moves the rest",
+        "Uses a list-detail structure (NavigationSplitView or NavigationStack) for jobs",
+        "Presents Log time as a sheet with Cancel and a confirming action",
+        "Protects unsaved input or warns against stacking modals"
+      ]
+    }
+  ]
+}

package/pipeline/skills/shared/external/hig-components-layout/evals/trigger-eval.json

@@ -0,0 +1,22 @@
+[
+  {"query": "how do I get a mini player above the tab bar like Apple Music in SwiftUI on iOS 26", "should_trigger": true},
+  {"query": "tab bar should shrink when the user scrolls down a feed, ios 26", "should_trigger": true},
+  {"query": "iOS 27: can I make the middle 'Create' tab look prominent like the new Photos app?", "should_trigger": true},
+  {"query": "navigation bar has 8 buttons and they get cut off on iphone, how do I decide what goes into the overflow menu", "should_trigger": true},
+  {"query": "our designer wants a solid brand-colored tab bar background on iOS 26, is that still ok?", "should_trigger": true},
+  {"query": "tabs or sidebar for an app with 9 sections on iPad and iPhone?", "should_trigger": true},
+  {"query": "ToolbarSpacer vs Spacer in toolbar - how do i split the buttons into separate glass groups", "should_trigger": true},
+  {"query": "should 'edit profile' be a sheet, a push or a full screen cover? and where do cancel and save go", "should_trigger": true},
+  {"query": "keep the Add button always visible on the trailing side of the nav bar even when search is open, iOS 27", "should_trigger": true},
+  {"query": "nav bar should collapse when scrolling an article on iOS 27", "should_trigger": true},
+  {"query": "make my custom floating button use liquid glass with a tint", "should_trigger": false},
+  {"query": "deep link into the third tab and push a detail screen with NavigationPath", "should_trigger": false},
+  {"query": "what font sizes and contrast ratios should my list rows use", "should_trigger": false},
+  {"query": "empty state for the downloads tab when nothing is saved yet", "should_trigger": false},
+  {"query": "support iPadOS 26 free-form window resizing and Stage Manager in my layout", "should_trigger": false},
+  {"query": "bottom sheet with medium and large detents and a grabber - how to implement the drag", "should_trigger": false},
+  {"query": "Compose Material 3 NavigationBar with badges", "should_trigger": false},
+  {"query": "tab bar icon: which SF Symbol variant should be used for the selected state", "should_trigger": false},
+  {"query": "React Native bottom tabs library recommendation", "should_trigger": false},
+  {"query": "animate the transition when switching tabs with a matched geometry effect", "should_trigger": false}
+]

package/pipeline/skills/shared/external/hig-components-layout/references/bars-and-tabs.md

@@ -0,0 +1,231 @@
+# Bars, tabs and toolbars on iOS 26 and 27
+
+Companion to `../SKILL.md` for the `hig-components-layout` skill. Each API
+carries the iOS release it first shipped in; gate anything newer than the
+deployment target with `#available`. The glass material itself (variants,
+custom glass, fallbacks) is in `swiftui-liquid-glass`.
+
+## Contents
+
+1. [Content layer and navigation layer](#1-content-layer-and-navigation-layer)
+2. [Tab bars](#2-tab-bars)
+3. [Search in a tab bar or toolbar](#3-search-in-a-tab-bar-or-toolbar)
+4. [Toolbars and navigation bars](#4-toolbars-and-navigation-bars)
+5. [Overflow, priority and pinning (iOS 27)](#5-overflow-priority-and-pinning-ios-27)
+6. [Minimizing bars on scroll](#6-minimizing-bars-on-scroll)
+7. [Review checklist](#7-review-checklist)
+
+## 1. Content layer and navigation layer
+
+From iOS 26, tab bars, toolbars, navigation bars and sidebars float in a
+Liquid Glass layer above the content. Three consequences:
+
+- **Keep navigation and content apart.** Destinations live in tab bars and
+  sidebars, actions in toolbars, and content scrolls underneath. Do not put
+  navigation inside content cards, or content inside bars.
+- **No custom bar backgrounds.** Background images, colors and appearance
+  fills on `TabView`, toolbars and navigation bars sit on top of the glass and
+  break the scroll edge effect. Remove them and let content color the bar. Where
+  the bar must separate more from content, adjust
+  `scrollEdgeEffectStyle(_:for:)` rather than painting.
+- **Tint sparingly.** Bar symbols are monochrome by default and follow the
+  content beneath. Over colorful content keep them monochrome, or pick an
+  accent that differs clearly from the content.
+
+## 2. Tab bars
+
+| API | Since | What it does |
+|---|---|---|
+| `Tab(_:systemImage:value:content:)` | iOS 18 | A tab; keep five or fewer by default |
+| `.tabViewStyle(.sidebarAdaptable)` | iOS 18 | Tab bar on iPhone, sidebar on iPad and Mac |
+| `.tabBarMinimizeBehavior(_:)` | iOS 26 | `.automatic`, `.never`, `.onScrollDown`, `.onScrollUp` |
+| `.tabViewBottomAccessory { }` | iOS 26 | A persistent accessory, such as a mini player, above the tab bar |
+| `.tabViewBottomAccessory(isEnabled:content:)` | iOS 26.1 | The same, shown and hidden dynamically |
+| `@Environment(\.tabViewBottomAccessoryPlacement)` | iOS 26 | `.expanded` above the bar or `.inline` beside a minimized bar |
+| `Tab(role: .search)` | iOS 18 | The search tab; iOS 26 sets it apart at the trailing end |
+| `TabRole.prominent` | iOS 27 | Prominent treatment for one tab; without one, the search tab may get it |
+
+```swift
+TabView(selection: $selection) {
+    Tab("Trips", systemImage: "airplane", value: .trips) { TripsView() }
+    Tab("Wallet", systemImage: "wallet.pass", value: .wallet) { WalletView() }
+        .badge(pendingPasses)
+    Tab("Account", systemImage: "person.crop.circle", value: .account) { AccountView() }
+    Tab(value: .search, role: .search) { SearchView() }
+}
+.tabViewStyle(.sidebarAdaptable)
+.tabBarMinimizeBehavior(.onScrollDown)
+.tabViewBottomAccessory {
+    BoardingStatusBar()
+}
+```
+
+Accessory content adapts to its placement:
+
+```swift
+struct BoardingStatusBar: View {
+    @Environment(\.tabViewBottomAccessoryPlacement) private var placement
+
+    var body: some View {
+        if placement == .inline {
+            Label("Gate B12", systemImage: "airplane.departure")
+        } else {
+            HStack {
+                Label("Gate B12", systemImage: "airplane.departure")
+                Spacer()
+                Text("Boarding 09:40")
+            }
+            .padding(.horizontal)
+        }
+    }
+}
+```
+
+On iOS 27, mark the one tab that deserves emphasis. With an older deployment
+target, build the iOS 27 `TabView` in its own `@available(iOS 27, *)` view and
+choose between the two with `if #available`.
+
+```swift
+Tab("Book", systemImage: "plus", value: .book, role: .prominent) {
+    BookingFlow()
+}
+```
+
+Rules:
+
+- A tab switches context; never use a tab as an action ("New trip"). Only one
+  tab can be prominent.
+- Do not hide or disable tabs because of state; explain inside the tab.
+- Minimize the tab bar only when reading content benefits; people restore it
+  by tapping a tab or scrolling the other way.
+- The accessory is for something persistent and app-wide (playback, an active
+  trip), not for a screen's primary action.
+
+## 3. Search in a tab bar or toolbar
+
+- `Tab(role: .search)` gives search its own tab; the first tab with that role
+  implements search. `tabViewSearchActivation(.searchTabSelection)` (iOS 26)
+  activates search when the tab is selected and returns to the previous tab
+  when search is dismissed.
+- `.searchable(text:)` on a `NavigationStack` places the field where the
+  platform expects; `searchToolbarBehavior(.minimize)` (iOS 26) shows the
+  bottom-toolbar field on iPhone as a compact button until used.
+- Scopes and suggestions for large catalogs: `.searchScopes(_:scopes:)` (iOS
+  16), the `activation:` form iOS 16.4, and `.searchSuggestions`.
+
+```swift
+NavigationStack {
+    LibraryList(query: query, scope: scope)
+        .searchable(text: $query)
+        .searchScopes($scope) {
+            ForEach(LibraryScope.allCases, id: \.self) { Text($0.label).tag($0) }
+        }
+}
+```
+
+## 4. Toolbars and navigation bars
+
+| API | Since | What it does |
+|---|---|---|
+| Semantic placements (`.primaryAction`, `.confirmationAction`, `.cancellationAction`, `.topBarLeading`, `.topBarTrailing`, `.bottomBar`) | iOS 14 / 17 SDK | Let the system position items per platform |
+| `ToolbarSpacer(.fixed)` / `ToolbarSpacer(.flexible)` | iOS 26 | Splits items into separate glass groups, or pushes groups apart |
+| `.sharedBackgroundVisibility(.hidden)` | iOS 26 | Takes an item out of the shared glass group |
+| `Button(role: .confirm)` / `Button(role: .close)` | iOS 26 | System confirm and close buttons in a toolbar |
+
+```swift
+.toolbar {
+    ToolbarItem(placement: .cancellationAction) {
+        Button(role: .close) { dismiss() }
+    }
+    ToolbarItem { Button("Share", systemImage: "square.and.arrow.up", action: share) }
+    ToolbarItem { Button("Duplicate", systemImage: "plus.square.on.square", action: duplicate) }
+    ToolbarSpacer(.fixed)
+    ToolbarItem(placement: .confirmationAction) {
+        Button(role: .confirm) { save() }
+    }
+}
+```
+
+HIG guidance for toolbars:
+
+- Prefer system symbols without borders to text; do not mix text and icons in
+  one group. Every icon still gets an accessibility label.
+- One primary action, on the trailing side, with the prominent treatment.
+- Aim for at most three groups; group items that act on the same thing.
+- Use the standard Back and Close buttons, not custom "Back" text.
+- Hide a toolbar item itself rather than the view inside it, or an empty glass
+  slot remains.
+- Custom components inside a bar keep corner radii concentric with the bar.
+
+## 5. Overflow, priority and pinning (iOS 27)
+
+| API | What it does |
+|---|---|
+| `ToolbarOverflowMenu { }` | Actions that always live in the toolbar's overflow menu, whatever the width; on iOS it is the navigation bar's overflow menu |
+| `.toolbarOverflowMenu { }` (view modifier) | Configures that overflow menu from a view |
+| `.visibilityPriority(.high)` / `.low` | When space runs out, lower-priority items move to overflow first; `ToolbarItemVisibilityPriority(higherThan:)` and `(lowerThan:)` give relative ranks |
+| `ToolbarItemPlacement.topBarPinnedTrailing` | Pins an item to the trailing edge of the top bar; it moves to overflow only when search is active and space is short |
+
+```swift
+.toolbar {
+    ToolbarItem(placement: .topBarPinnedTrailing) {
+        Button("Add", systemImage: "plus", action: add)
+    }
+    ToolbarItem { Button("Filter", systemImage: "line.3.horizontal.decrease", action: filter) }
+        .visibilityPriority(.high)
+    ToolbarItem { Button("Sort", systemImage: "arrow.up.arrow.down", action: sort) }
+    ToolbarOverflowMenu {
+        Button("Export", action: export)
+        Button("Print", action: printList)
+    }
+}
+```
+
+With an older deployment target, keep this toolbar in an
+`@available(iOS 27, *)` view modifier and apply it behind `if #available`,
+with a plain toolbar for earlier releases. HIG says the system adds an overflow menu by itself on
+iPad and Mac when items do not fit: do not hand-build a "more" `Menu` for that,
+and choose priorities so the important items stay.
+
+## 6. Minimizing bars on scroll
+
+| API | Since | What it does |
+|---|---|---|
+| `.tabBarMinimizeBehavior(.onScrollDown)` | iOS 26 | Tab bar recedes while scrolling |
+| `.toolbarMinimizationBehavior(_:for:)` | iOS 27 | Navigation bar minimizes on scroll; an integrated top tab bar minimizes with it. Supported placement: `.navigationBar` |
+| `.toolbarMinimizationRestoration(.atScrollEdge, for:)` | iOS 27 | Restore only at the scroll edge (with `.onScrollDown`, navigation bar only) |
+| `.toolbarMinimizationSafeAreaAdjustment(_:for:)` | iOS 27 | Whether the safe area follows the minimizing bar |
+
+```swift
+NavigationStack {
+    ArticleView()
+        .navigationTitle("Reading")
+        .toolbarMinimizationBehavior(.onScrollDown, for: .navigationBar)
+}
+```
+
+Use minimization for long reading or browsing surfaces, not for forms or
+screens whose bar holds the main actions.
+
+## 7. Review checklist
+
+- [ ] No custom backgrounds on tab bars, toolbars or navigation bars
+- [ ] Navigation in bars and sidebars, content in the content layer
+- [ ] Tabs are destinations, five or fewer by default, at most one `.prominent` (iOS 27)
+- [ ] Search uses `Tab(role: .search)` or `.searchable`, not a custom field in a bar
+- [ ] Toolbar items use semantic placements, symbols with labels, one prominent action, groups split with `ToolbarSpacer`
+- [ ] iOS 27 overflow, priority, pinning and minimization APIs are gated with `#available`
+- [ ] Minimizing bars only on reading surfaces; accessory content adapts to `.inline`
+
+Sources:
+[HIG: Tab bars](https://developer.apple.com/design/human-interface-guidelines/tab-bars),
+[HIG: Toolbars](https://developer.apple.com/design/human-interface-guidelines/toolbars),
+[Adopting Liquid Glass](https://developer.apple.com/documentation/technologyoverviews/adopting-liquid-glass),
+[tabBarMinimizeBehavior(_:)](https://developer.apple.com/documentation/swiftui/view/tabbarminimizebehavior(_:)),
+[tabViewBottomAccessory(content:)](https://developer.apple.com/documentation/swiftui/view/tabviewbottomaccessory(content:)),
+[TabRole.prominent](https://developer.apple.com/documentation/swiftui/tabrole/prominent),
+[ToolbarOverflowMenu](https://developer.apple.com/documentation/swiftui/toolbaroverflowmenu),
+[visibilityPriority(_:)](https://developer.apple.com/documentation/swiftui/toolbarcontent/visibilitypriority(_:)),
+[topBarPinnedTrailing](https://developer.apple.com/documentation/swiftui/toolbaritemplacement/topbarpinnedtrailing),
+[toolbarMinimizationBehavior(_:for:)](https://developer.apple.com/documentation/swiftui/view/toolbarminimizationbehavior(_:for:)),
+[ToolbarSpacer](https://developer.apple.com/documentation/swiftui/toolbarspacer).

package/pipeline/skills/shared/external/hig-components-layout/references/containers.md

@@ -8,31 +8,9 @@ Companion to `../SKILL.md` for the `hig-components-layout` skill.
   back returns people to where they left off.
 - Never hide or disable a tab because of state. Show the tab and explain
   inside it (an empty state or sign-in prompt).
-- On iOS 18 and later, `Tab(role: .search)` places search as a dedicated tab;
-  on iOS 26 it is set apart at the trailing end of the floating glass tab bar.
-- iOS 26 renders the tab bar as floating Liquid Glass above content. Let
-  content scroll underneath it; do not paint an opaque background behind it.
-- `.tabBarMinimizeBehavior(.onScrollDown)` (iOS 26) shrinks the bar while
-  reading; `.tabViewBottomAccessory` places a persistent control such as a
-  playback bar above it.
 - Badges (`.badge(3)`) are for counts people act on, not marketing.
-
-```swift
-TabView(selection: $selection) {
-    Tab("Orders", systemImage: "shippingbox", value: .orders) {
-        OrdersView()
-    }
-    .badge(pendingCount)
-    Tab("Products", systemImage: "square.grid.2x2", value: .products) {
-        ProductsView()
-    }
-    Tab(value: .search, role: .search) {
-        SearchView()
-    }
-}
-.tabViewStyle(.sidebarAdaptable)
-.tabBarMinimizeBehavior(.onScrollDown)
-```
+- Minimize behavior, the bottom accessory, the search tab and the iOS 27
+  prominent tab are in [bars-and-tabs.md](bars-and-tabs.md).
 
 ## Sidebars and split views
 
@@ -60,12 +38,9 @@ TabView(selection: $selection) {
 
 ## Toolbars
 
-- Declare actions with `.toolbar` and placements (`.primaryAction`,
-  `.topBarTrailing`, `.bottomBar`, `.confirmationAction`,
-  `.cancellationAction`) so the system positions them per platform.
-- On iOS 26 toolbar items sit on glass and are grouped automatically;
-  `ToolbarSpacer` separates groups. Prefer SF Symbols over text for bar items
-  and let the system apply glass; do not add your own backgrounds.
+- Declare actions with `.toolbar` and semantic placements so the system
+  positions them per platform. Grouping, `ToolbarSpacer`, overflow, priority
+  and pinning are in [bars-and-tabs.md](bars-and-tabs.md).
 - Use `.toolbarRole(.editor)` on document-style screens and let people
   customise Mac and iPad toolbars with `id`-based toolbar items.
 

package/pipeline/skills/shared/external/hig-components-status/SKILL.md

@@ -111,7 +111,7 @@ struct UploadRow: View {
 ## Feedback after an action
 
 - Confirm success quietly and in place: a checkmark in the button, a row that
-  updates, a short haptic with `.sensoryFeedback(.success, trigger:)`.
+  updates, a short haptic (see `ios-haptics`).
 - Reserve alerts for failures that need a decision. For everything else,
   explain inline next to the thing that failed.
 - Network and sync status belongs near the affected content (a banner above

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

@@ -1,6 +1,6 @@
 ---
 name: hig-foundations
-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."
+description: "Apple HIG foundations mapped to SwiftUI: typography and Dynamic Type, semantic color, contrast, spacing, safe areas, touch targets, motion and UX writing. Use when a design decision turns on type, color, contrast or spacing."
 metadata:
   risk: safe
   source: multi-agent-pipeline
@@ -27,13 +27,28 @@ hide problems in the steps after it.
 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.
+4. Icons are symbols with consistent weight and scale (`ios-sf-symbols`).
 5. Materials and motion support the content instead of competing with it.
 6. Copy is short, specific and written in the product's voice.
 
+## The numbers that come up most
+
+| Question | Answer (iOS and iPadOS) |
+|---|---|
+| Default and minimum text size | 17 pt and 11 pt, for system and custom fonts |
+| Weights | Prefer Regular, Medium, Semibold, Bold; avoid Ultralight, Thin, Light |
+| Second level of hierarchy inside a style | The emphasized weight via `.bold()` |
+| Custom font that scales | `Font.custom(_:size:relativeTo:)`, plus `@ScaledMetric` for sizes beside text |
+| Contrast | 4.5:1 for text up to 17 pt, 3:1 from 18 pt or for bold text |
+| Touch target | 44 x 44 pt default, 28 x 28 pt minimum |
+
 ## Details on demand
 
-Load `references/foundations-detail.md` for each review step above, with the SwiftUI APIs and code for it.
+- `references/foundations-detail.md`: each review step above with the
+  question to ask, the SwiftUI tools and what a reviewer looks for.
+- `references/type-color-spacing.md`: the text style table with emphasized
+  weights, custom-font scaling, color roles, contrast table, color on Liquid
+  Glass, spacing scale, margins and touch targets, with code.
 
 ## Reporting findings
 
@@ -49,7 +64,11 @@ dynamicTypeSize.isAccessibilitySize.
 
 - `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.
+- `swiftui-liquid-glass` for materials and Liquid Glass (the single owner).
+- `ios-sf-symbols` for symbol rendering modes, variable values and effects.
+- `hig-app-icons` for app icons, Icon Composer and appearance variants.
+- `ios-accessibility` for implementing Dynamic Type, contrast and motion
+  settings; `ios-design-review` for checking them with screenshots.
 
 ## References
 

package/pipeline/skills/shared/external/hig-foundations/evals/evals.json

@@ -0,0 +1,47 @@
+{
+  "skill_name": "hig-foundations",
+  "evals": [
+    {
+      "id": 0,
+      "name": "brand-typography-scale",
+      "prompt": "Our brand font is 'Moderat' and the design file uses Moderat Light 10 pt for row metadata, Moderat Thin 15 pt for body copy and hard-coded .font(.custom(\"Moderat-Bold\", size: 24)) for titles. Accessibility audit says text doesn't grow with the system setting. Rewrite our Font extension for SwiftUI and tell me what to push back on with design.",
+      "expected_output": "Pushes back on 10 pt (below the 11 pt iOS minimum) and on Light and Thin weights for interface text, recommending Regular or heavier and sizes at or above the defaults. Rewrites fonts with Font.custom(_:size:relativeTo:) tied to text styles (body 17 pt relative to .body, titles relative to .title or .largeTitle, metadata to .caption or .footnote), uses @ScaledMetric for adjacent dimensions, and suggests the emphasized weight via .bold() for hierarchy. Mentions checking accessibility sizes and adapting layout.",
+      "files": [],
+      "expectations": [
+        "Flags 10 pt as below the 11 pt iOS minimum text size",
+        "Advises against Light and Thin weights in favor of Regular, Medium, Semibold or Bold",
+        "Uses Font.custom(_:size:relativeTo:) mapped to text styles so the custom font scales with Dynamic Type",
+        "Mentions 17 pt as the iOS default body size",
+        "Mentions @ScaledMetric or adaptive layout at accessibility sizes"
+      ]
+    },
+    {
+      "id": 1,
+      "name": "contrast-and-color-roles",
+      "prompt": "Product page in SwiftUI: price in Color(hex: \"#9AA0A6\") on white at 15 pt, 'Out of stock' shown only by turning the row red, background Color.white, and a custom gray for dividers. Dark mode looks broken. What do the HIG foundations say and what do we change?",
+      "expected_output": "Explains the HIG minimum contrast (4.5:1 for text up to 17 pt, 3:1 for 18 pt and larger or bold), that the light gray price likely fails, and replaces hard-coded colors with semantic ones (.secondary or secondaryLabel only if contrast holds, systemBackground, separator) or asset catalog colors with light, dark and increased-contrast variants. Says out-of-stock must not be conveyed by color alone and adds a label or symbol. Mentions testing with Increase Contrast and both appearances.",
+      "files": [],
+      "expectations": [
+        "States the 4.5:1 minimum for text up to 17 pt (and 3:1 for larger or bold text)",
+        "Replaces hard-coded white and gray with semantic system colors such as systemBackground and separator, or asset colors with dark variants",
+        "Says color alone must not convey out-of-stock and adds text or a symbol",
+        "Mentions an increased-contrast variant or testing with Increase Contrast",
+        "Does not recommend hard-coding the documented system color values"
+      ]
+    },
+    {
+      "id": 2,
+      "name": "spacing-and-targets-review",
+      "prompt": "Review this SwiftUI row: HStack(spacing: 3) { Image(systemName: \"trash\").font(.system(size: 12)).onTapGesture(perform: delete); Text(title).font(.system(size: 13)).lineLimit(1) }.padding(.horizontal, 7). It sits in a ScrollView edge to edge on iPad too. Give findings in the foundations format.",
+      "expected_output": "Reports findings per foundation: the trash target is far below 44x44 pt and should become a Button with a 44 pt hit area (contentShape/frame) or use swipe actions; spacing values 3 and 7 are off any grid and should be omitted or taken from tokens or a 4 pt scale; fixed system sizes should be text styles so Dynamic Type works, and lineLimit(1) truncates at large sizes; on iPad use contentMargins or readable width instead of edge to edge. Uses the [Foundation] issue plus Fix format.",
+      "files": [],
+      "expectations": [
+        "Flags the tap target as below 44 x 44 pt and makes it a Button with a larger hit area",
+        "Replaces .system(size:) with text styles for Dynamic Type and questions lineLimit(1)",
+        "Flags the arbitrary 3 and 7 point values and suggests default spacing, tokens or a 4 pt scale",
+        "Suggests contentMargins or a readable width for iPad instead of edge-to-edge text",
+        "Reports each finding with the foundation name and a concrete fix"
+      ]
+    }
+  ]
+}