@mmerterden/multi-agent-pipeline 20.17.1 → 20.18.0

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

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

@@ -0,0 +1,21 @@
+[
+  {"query": "what's the minimum font size apple allows on iphone? design wants 9pt captions", "should_trigger": true},
+  {"query": "our custom font doesn't scale with dynamic type, we use Font.custom(name, size: 16) everywhere", "should_trigger": true},
+  {"query": "is #8E8E93 text on white ok for accessibility? it's a 14pt price label", "should_trigger": true},
+  {"query": "which font weights should I avoid in the app, designer loves Ultralight for headlines", "should_trigger": true},
+  {"query": "how much padding between rows and what margins does apple recommend, we keep guessing 7, 9, 13", "should_trigger": true},
+  {"query": "dark mode: our hardcoded Color.white backgrounds and gray dividers look awful, what colors should we use", "should_trigger": true},
+  {"query": "headline vs body vs callout - what sizes are these text styles on iOS and when do I make one bold", "should_trigger": true},
+  {"query": "tiny 20pt close button in the corner, testers keep missing it - what size should tap targets be", "should_trigger": true},
+  {"query": "status shown only with red/green dots in our order list, is that a problem per HIG", "should_trigger": true},
+  {"query": "make my glass toolbar buttons tinted with the brand color on iOS 26", "should_trigger": false},
+  {"query": "which SF Symbol rendering mode should I use for the battery icon with a level", "should_trigger": false},
+  {"query": "design the app icon dark and tinted variants in Icon Composer", "should_trigger": false},
+  {"query": "set up VoiceOver labels and rotors for our custom chart", "should_trigger": false},
+  {"query": "tab bar or sidebar for an iPad app with 9 sections?", "should_trigger": false},
+  {"query": "onboarding flow: should we ask for notification permission on first launch", "should_trigger": false},
+  {"query": "Material 3 typography scale for our Compose app", "should_trigger": false},
+  {"query": "take screenshots of the checkout screen at AX5 and dark mode and review them", "should_trigger": false},
+  {"query": "CSS rem vs px for our marketing site font sizes", "should_trigger": false},
+  {"query": "add a gentle haptic when a row is deleted", "should_trigger": false}
+]

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

@@ -2,6 +2,18 @@
 
 Companion to `../SKILL.md` for the `hig-foundations` skill.
 
+## Contents
+
+- [1. Typography](#1-typography)
+- [2. Color](#2-color)
+- [3. Layout, margins and safe areas](#3-layout-margins-and-safe-areas)
+- [4. Icons and SF Symbols](#4-icons-and-sf-symbols)
+- [5. Materials, Liquid Glass and depth](#5-materials-liquid-glass-and-depth)
+- [6. Motion](#6-motion)
+- [7. App icon](#7-app-icon)
+- [8. Writing](#8-writing)
+- [9. Accessibility, as a foundation](#9-accessibility-as-a-foundation)
+
 ## 1. Typography
 
 Ask: if the user sets the largest accessibility text size, does every string
@@ -19,7 +31,13 @@ still fit, wrap or scroll?
   `@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.
+  three styles per screen is usually enough; use a style's emphasized weight
+  (`.bold()`) before reaching for a bigger style.
+- Respect the floor: 17 pt default and 11 pt minimum on iOS, for custom fonts
+  too. Avoid Ultralight, Thin and Light weights for interface text.
+
+Numbers, the full text style table and custom-font code:
+[type-color-spacing.md](type-color-spacing.md).
 
 Review signal: truncated order totals, overlapping labels, or buttons whose
 titles are clipped at `accessibility3` and above.
@@ -37,8 +55,9 @@ with increased contrast, and to someone who cannot distinguish red from green?
 - 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.
+- Meet at least 4.5:1 contrast for text up to 17 pt and 3:1 for 18 pt and
+  larger or bold text; if the default palette cannot, provide a
+  higher-contrast scheme under Increase Contrast.
 
 Review signal: hard-coded hex values, `Color.white` text on a brand color that
 fails contrast in dark mode, status conveyed only by hue.
@@ -66,34 +85,25 @@ rounded corners and the keyboard, while backgrounds still reach the edges?
 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.
+Use `Image(systemName:)` and `Label` so symbols align with text and scale with
+Dynamic Type. Rendering modes, variable values, symbol effects and custom
+symbols are covered in `ios-sf-symbols`.
 
 ## 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, *)`.
+- Liquid Glass is for the navigation and control layer; content uses standard
+  materials (`.ultraThinMaterial` to `.thickMaterial`) or solid fills.
+- Vibrant label and fill colors keep text legible on materials; avoid the
+  quaternary label level on thin and ultra-thin materials.
 - Respect Reduce Transparency: system materials handle it, custom blurs must
   check `accessibilityReduceTransparency`.
 
+Everything about glass itself (variants, containers, fallbacks, UIKit) lives
+in `swiftui-liquid-glass`.
+
 ## 6. Motion
 
 Ask: does this animation explain a change, and what happens when Reduce Motion
@@ -110,10 +120,8 @@ is on?
 
 ## 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.
+Layered icons, Icon Composer, the default, dark, clear and tinted appearances
+and the asset catalog setup are covered in `hig-app-icons`.
 
 ## 8. Writing