@mmerterden/multi-agent-pipeline 20.17.1 → 20.18.0

package/pipeline/skills/shared/external/hig-app-icons/SKILL.md

@@ -0,0 +1,159 @@
+---
+name: hig-app-icons
+description: "iOS app icons: Icon Composer layered icons, default, dark, clear and tinted appearances, asset catalogs, alternate icons and the archive checks icons fail. Use when designing, exporting, wiring up or reviewing an app icon, or diagnosing an icon upload error or rejection."
+metadata:
+  source: multi-agent-pipeline
+  date_added: "2026-10-08"
+---
+
+# App icons
+
+An iOS icon is no longer a stack of PNGs at a dozen sizes. It is a layered
+design that the system renders: it adds the rounded mask, the Liquid Glass
+highlights and refraction, the dark, clear and tinted looks, and every size the
+system needs. The designer's job moves from exporting sizes to giving the
+system good layers.
+
+## What the system expects
+
+| | iOS, iPadOS |
+|---|---|
+| Canvas | 1024x1024 px, square, unmasked (Apple Watch: 1088x1088 px) |
+| Style | Layered: a background plus foreground layers |
+| Appearances | Default, dark, clear light, clear dark, tinted light, tinted dark |
+| Sizes | Generated by the system from the one design |
+| Colour spaces | sRGB, Gray Gamma 2.2, Display P3 |
+
+People choose the Home Screen look (default, dark, clear or tinted). Variants
+you do not design are generated automatically. Provide your own when the
+automatic result loses the idea of the icon, for example when a brand colour
+carries the meaning.
+
+## Icon Composer is the default path
+
+Icon Composer ships with Xcode (Xcode > Open Developer Tool > Icon Composer)
+and as a download from developer.apple.com/icon-composer. One Icon Composer
+file describes the icon for iPhone, iPad, Mac and Apple Watch, in every
+appearance.
+
+1. Draw the layers in any vector tool on the Apple template from Apple Design
+   Resources. Separate anything you may want to restyle per appearance.
+   Convert text to outlines. Leave out blurs, shadows, highlights, background
+   fills and the corner mask; Icon Composer and the system add those.
+2. Export layers as SVG; use PNG only for art SVG cannot express (mesh
+   gradients, raster artwork).
+3. In Icon Composer, import the layers, organise them into at most four
+   groups (the groups become the depth layers), set the background as a solid
+   colour or gradient, and tune Liquid Glass per group: specular, blur,
+   translucency, shadow, refraction.
+4. Preview default, dark and mono (mono covers clear and tinted, light and
+   dark), on each platform, over real wallpapers. Fix variants under Color in
+   the Style inspector.
+5. Add the file to the Xcode project. The App Icon field in the target's
+   General tab must match the file name without extension. This file replaces
+   any `AppIcon` asset catalog for the build.
+
+For deployment targets older than the Liquid Glass releases, Xcode generates
+flat images from the Icon Composer file at build time. If the existing icon
+must keep appearing unchanged on those older releases, keep the asset catalog
+instead. Step-by-step detail and the asset catalog route are in
+`references/icon-workflow.md`.
+
+## Design rules worth enforcing
+
+Each of these comes from the HIG app icon page; the reason is given so a
+review can argue the point instead of citing a rule.
+
+- **Square, unmasked layers.** The system masks the corners; a pre-masked layer
+  breaks the specular edge and leaves jagged corners.
+- **Primary content centred.** Masks and corner adjustments crop the edges.
+- **Clean, hard edges on foreground shapes.** System highlights and shadows
+  read soft edges as mistakes.
+- **No baked effects.** Your shadows and glows are static; the system's react
+  to light and motion, and the two fight.
+- **Simple concept, few shapes.** Detail disappears at small sizes and under
+  glass.
+- **Text only when it is essential.** It cannot be localized or read by
+  VoiceOver and is usually too small.
+- **Same features in every appearance.** Swapping elements per look makes the
+  app hard to find when people change their Home Screen style.
+- **No Apple hardware, no SF Symbols.** Apple product replicas are not allowed
+  in icons, and the SF Symbols terms prohibit symbols (or look-alikes) in app
+  icons and logos. See `ios-sf-symbols`.
+- **No photos or UI screenshots.** They do not survive layering, small sizes
+  or the dark and tinted looks.
+
+## Alternate icons
+
+People can pick another icon from inside the app (a team colour, a seasonal
+look). Each alternate is its own Icon Composer file with its own dark, clear
+and tinted variants, and each goes through App Review.
+
+- List them in the **Alternate App Icon Sets** build setting
+  (`ASSETCATALOG_COMPILER_ALTERNATE_APPICON_NAMES`); the primary is the
+  **Primary App Icon Set Name**. Xcode writes `CFBundleIcons`,
+  `CFBundlePrimaryIcon` and `CFBundleAlternateIcons` into Info.plist from
+  those settings, so do not edit those keys by hand.
+- Switch with `UIApplication.setAlternateIconName(_:completionHandler:)`, or
+  its `async throws` form. Pass `nil` to return to the primary icon. Check
+  `supportsAlternateIcons` first and read the current one from
+  `alternateIconName`.
+- The system shows an alert telling the person the icon changed. Trigger the
+  change from an explicit choice in the UI, not on launch or on a timer.
+
+```swift
+import OSLog
+import UIKit
+
+private let logger = Logger(subsystem: "app.icons", category: "alternate")
+
+@MainActor
+func applyIcon(named name: String?) async {
+    let app = UIApplication.shared
+    guard app.supportsAlternateIcons, app.alternateIconName != name else { return }
+    do {
+        try await app.setAlternateIconName(name)
+    } catch {
+        logger.error("Icon change failed: \(error.localizedDescription)")
+    }
+}
+```
+
+## Before upload
+
+Run the archive through `apple-archive-compliance` (the `ios_app_store_audit`
+tool). Its `asset-validation` rule fails an archive with no icon configuration
+or asset catalog. Upload validation (`ios_testflight_validate`) maps the icon
+errors Apple returns:
+
+| Code | Meaning | Usual fix |
+|---|---|---|
+| ITMS-90022 | A required iPhone icon size is missing | Use the Icon Composer file or a Single Size 1024 asset |
+| ITMS-90023 | A required iPad icon size is missing | Add iPad to the Icon Composer file's platforms, or use a Single Size 1024 asset that covers iPad |
+| ITMS-90717 | App Store icon has an alpha channel | Supply an opaque image where a flattened icon is used |
+
+App Review issues that involve icons:
+
+- **2.3.8**: icons, including alternates and in-app purchase icons, must suit
+  a 4+ audience even if the app is rated higher.
+- **4.1**: an icon that copies or impersonates another app.
+- **5.2.5**: an icon confusingly similar to an Apple product or app.
+
+## Reviewing an icon
+
+On a device or in Device Hub, set the Home Screen to dark, clear and tinted
+and look at the icon among system apps and widgets. Ask: is it still
+recognisable in every look, is anything important near the edges, does it
+look crisp at the Settings and notification sizes, and does the dark variant
+keep enough contrast? Coloured backgrounds usually give dark icons the most
+contrast.
+
+## References
+
+- `references/icon-workflow.md`: Icon Composer steps, asset catalog route, alternate icon setup, review checklist.
+- HIG app icons: https://developer.apple.com/design/human-interface-guidelines/app-icons
+- Creating your app icon using Icon Composer: https://developer.apple.com/documentation/xcode/creating-your-app-icon-using-icon-composer
+- Configuring your app icon using an asset catalog: https://developer.apple.com/documentation/xcode/configuring-your-app-icon
+- Alternate app icons sample: https://developer.apple.com/documentation/xcode/configuring-your-app-to-use-alternate-app-icons
+- setAlternateIconName: https://developer.apple.com/documentation/uikit/uiapplication/setalternateiconname(_:completionhandler:)
+- Icon Composer: https://developer.apple.com/icon-composer/

package/pipeline/skills/shared/external/hig-app-icons/evals/evals.json

@@ -0,0 +1,48 @@
+{
+  "skill_name": "hig-app-icons",
+  "evals": [
+    {
+      "id": 0,
+      "name": "migrate-legacy-icon-set",
+      "prompt": "Our app still ships an AppIcon asset catalog with 18 hand-exported PNG sizes and a separate dark PNG. Design wants the new Liquid Glass look. What exactly do we hand over from the design tool, what happens in Icon Composer, and how do we wire it into Xcode without breaking users on older iOS?",
+      "expected_output": "Explains that iOS now uses one layered 1024x1024 design that the system renders at every size and appearance. Design exports square, unmasked layers as SVG (PNG only where needed) with text outlined and no baked blurs, shadows, highlights, background fills or mask. Icon Composer: import, organise into at most four groups, set background, tune Liquid Glass, preview default, dark and mono (clear and tinted). Xcode: add the file and make the App Icon field match its name; it replaces the asset catalog, and Xcode generates flat images for older deployment targets, or keep the asset catalog if the old icon must stay unchanged on older releases.",
+      "files": [],
+      "expectations": [
+        "States sizes are generated from one 1024x1024 design rather than hand-exported",
+        "Asks for unmasked square layers exported as SVG without baked effects",
+        "Mentions grouping into at most four groups in Icon Composer",
+        "Covers default, dark, clear and tinted appearances",
+        "Says the App Icon name in the target must match the Icon Composer file",
+        "Explains older-release behaviour (generated images, or keeping the asset catalog)"
+      ]
+    },
+    {
+      "id": 1,
+      "name": "alternate-icons-setup",
+      "prompt": "Product wants users to pick between three team-colour icons from our settings screen. How do we set that up in Xcode and Swift, and will App Review care?",
+      "expected_output": "One Icon Composer file per alternate, each with its own dark, clear and tinted variants. Lists them in the Alternate App Icon Sets build setting (ASSETCATALOG_COMPILER_ALTERNATE_APPICON_NAMES) and leaves CFBundleIcons keys to Xcode. Calls setAlternateIconName from the person's choice after checking supportsAlternateIcons, passes nil for the primary, reads alternateIconName, handles the error, and notes the system alert. Notes each alternate goes through App Review, must suit 4+ (2.3.8) and must not resemble another app or Apple product.",
+      "files": [],
+      "expectations": [
+        "Uses one Icon Composer file per alternate with its own appearance variants",
+        "Names the Alternate App Icon Sets setting or ASSETCATALOG_COMPILER_ALTERNATE_APPICON_NAMES",
+        "Warns against editing CFBundleIcons by hand",
+        "Uses setAlternateIconName with supportsAlternateIcons and nil for the primary",
+        "Mentions that alternate icons are reviewed by App Review"
+      ]
+    },
+    {
+      "id": 2,
+      "name": "upload-error-and-design-critique",
+      "prompt": "Upload failed with ITMS-90717 on our App Store icon, and while we are at it, the designer put a gear SF Symbol and the word 'Pro' on the icon with a drop shadow. What is wrong?",
+      "expected_output": "Explains ITMS-90717 as an alpha channel in the App Store icon and that a flattened icon must be opaque, and suggests running the archive through apple-archive-compliance or ios_app_store_audit and validation. Critiques the design: SF Symbols terms prohibit symbols in app icons, text should be avoided unless essential, and baked shadows conflict with system effects.",
+      "files": [],
+      "expectations": [
+        "Identifies ITMS-90717 as an alpha channel problem",
+        "Points to apple-archive-compliance or ios_app_store_audit for archive checks",
+        "Says SF Symbols may not be used in app icons",
+        "Advises against nonessential text in the icon",
+        "Says to remove the baked drop shadow and let the system apply effects"
+      ]
+    }
+  ]
+}

package/pipeline/skills/shared/external/hig-app-icons/evals/trigger-eval.json

@@ -0,0 +1,22 @@
+[
+  { "query": "How do I make our app icon with Icon Composer for iOS 26?", "should_trigger": true },
+  { "query": "Do I still need to export all the app icon sizes by hand?", "should_trigger": true },
+  { "query": "Add dark and tinted variants to our app icon", "should_trigger": true },
+  { "query": "Let users choose an alternate app icon from settings", "should_trigger": true },
+  { "query": "setAlternateIconName returns an error, what's wrong with our setup?", "should_trigger": true },
+  { "query": "App Store upload failed with ITMS-90022 missing icon size", "should_trigger": true },
+  { "query": "Review our new app icon design against Apple guidelines", "should_trigger": true },
+  { "query": "What does the clear app icon appearance look like and do we need to design it?", "should_trigger": true },
+  { "query": "Our icon looks jagged at the corners after the Liquid Glass update", "should_trigger": true },
+  { "query": "Where do I set the alternate app icon names in build settings?", "should_trigger": true },
+  { "query": "Which SF Symbol should I use for the settings tab?", "should_trigger": false },
+  { "query": "Make our toolbar buttons use Liquid Glass", "should_trigger": false },
+  { "query": "Generate App Store screenshots in five languages", "should_trigger": false },
+  { "query": "Our archive fails privacy manifest checks before submission", "should_trigger": false },
+  { "query": "Create a custom SF Symbol and annotate its layers", "should_trigger": false },
+  { "query": "Design a launch screen storyboard", "should_trigger": false },
+  { "query": "Improve our App Store listing keywords and subtitle", "should_trigger": false },
+  { "query": "Add images with dark mode variants to the asset catalog", "should_trigger": false },
+  { "query": "Design review of the home screen layout in dark mode", "should_trigger": false },
+  { "query": "Show a badge count on the app icon for unread messages", "should_trigger": false }
+]

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}
+]