@mmerterden/multi-agent-pipeline 20.36.0 → 20.37.1

package/pipeline/skills/shared/external/ios-accessibility/SKILL.md

@@ -15,6 +15,7 @@ UIKit and AppKit.
 
 References:
 
+- [Assistive technology review](references/assistive-tech-review.md): Reduce Motion and appearance code, the per-technology review rules (Voice Control, Switch Control, Full Keyboard Access, Assistive Access), UIKit and AppKit specifics, custom content, and the manual and XCTest test steps.
 - [Code patterns](references/a11y-patterns.md): worked examples of the
   modifiers in both UI frameworks, grouping, custom and adjustable controls, custom actions, rotors,
   Dynamic Type, AppKit, Voice Control, Switch Control, Full Keyboard Access,
@@ -184,46 +185,16 @@ unread threads or headings. Add them to screens dense with content; see
 
 With Reduce Motion on, replace movement with a crossfade or with no animation.
 
-```swift
-struct FilterDrawer: View {
-    @Environment(\.accessibilityReduceMotion) private var reduceMotion
-    @State private var isExpanded = false
-
-    var body: some View {
-        VStack {
-            Button("Filters") {
-                withAnimation(reduceMotion ? nil : .spring()) { isExpanded.toggle() }
-            }
-            if isExpanded {
-                PanelView()
-                    .transition(reduceMotion ? .opacity : .move(edge: .bottom))
-            }
-        }
-    }
-}
-```
-
 Go through every moving transition, not just the obvious one: row removal,
 quantity changes, presenting a sheet or checkout, dismissing a modal. Slides,
 bounces, parallax, springs and big spatial moves become fades, an immediate
 jump to the end state, or no animation at all.
 
-### Transparency, contrast, bold text
+A `FilterDrawer` example that swaps the spring and slide for no animation and a fade: [Assistive technology review](references/assistive-tech-review.md).
 
-```swift
-@Environment(\.accessibilityReduceTransparency) private var reduceTransparency
-@Environment(\.colorSchemeContrast) private var contrast
-@Environment(\.legibilityWeight) private var legibilityWeight
-
-private let base = Color(uiColor: .systemBackground)
+### Transparency, contrast, bold text
 
-var body: some View {
-    Text(caption)
-        .foregroundStyle(contrast == .increased ? .primary : .secondary)
-        .fontWeight(legibilityWeight == .bold ? .bold : .regular)
-        .background(reduceTransparency ? base : base.opacity(0.8))
-}
-```
+Code that adapts foreground style, font weight and background opacity to these three settings: [Assistive technology review](references/assistive-tech-review.md).
 
 ## Decorative versus meaningful images
 
@@ -244,62 +215,15 @@ instead of hiding it.
 
 ## Voice Control
 
-Spoken commands find their target through its accessibility label: the label
-is the name a person says to tap the element. An element with no label, or a label nobody can say, cannot be
-targeted by voice.
-
-- Every interactive element needs a label a person can say aloud. No labels
-  made only of emoji or symbols.
-- Labels must differ among the elements on screen at the same time;
-  duplicates push users onto overlay numbers.
-- Add `accessibilityInputLabels` before feature freeze, not as late polish,
-  wherever a label is long, clumsy, localized, full of acronyms, or usually
-  shortened when spoken. Both Full Keyboard Access and Voice Control consume
-  them. List the entries most important first.
-- Good candidates: media controls, settings and account links, per-row
-  actions that repeat down a list, quantity steppers, localized labels that
-  contain product names or acronyms.
-- Turn Voice Control on and say "Show Names", then "Show Numbers". The names
-  overlay proves labels can be spoken; the numbers overlay proves every
-  visible target stays reachable even if its name is missing, duplicated or
-  awkward. A review
-  checks both overlays.
-
-Examples and speakable-label guidance: [code patterns](references/a11y-patterns.md).
+Every interactive element needs a unique label a person can say aloud; add `accessibilityInputLabels` early for long, localized or acronym-heavy labels, and check both the Show Names and Show Numbers overlays. Full rules: [Assistive technology review](references/assistive-tech-review.md).
 
 ## Switch Control
 
-Switch Control steps through accessibility elements one at a time in reading
-order, so grouping and custom actions matter more here than anywhere else.
-
-- `.accessibilityElement(children: .combine)` merges related pieces and
-  removes scan stops. Each remaining stop should mean something and do
-  something.
-- Anything hidden from VoiceOver as decorative is skipped by Switch Control
-  too.
-- Multi-finger gestures, long presses and swipe-to-delete are out of reach
-  for switch users. Offer those operations as `.accessibilityAction(named:)`; Switch
-  Control lists them in a menu.
-- In point scanning mode, a custom control whose tappable area is unusual
-  must report an `accessibilityFrame` that matches that area.
+Scanning follows reading order: combine related pieces to cut scan stops, and offer gestures (multi-finger, long press, swipe-to-delete) as named custom actions. Full rules: [Assistive technology review](references/assistive-tech-review.md).
 
 ## Full Keyboard Access
 
-Available since iOS and iPadOS 13.4, Full Keyboard Access lets people run the
-app from a hardware keyboard. This skill owns the review: can everything be
-reached, is it clearly labelled, is focus visible, does it work without touch.
-`UIFocusGuide`, tvOS focus, scene-focused values, directional movement,
-`focusSection()`, `@FocusState`, `.focusable()`, custom cards that Tab jumps
-over, and Tab traversal bugs in general go to `hig-inputs` first; only the accessibility finding
-stays here.
-
-Audit:
-
-- the keyboard alone can reach and trigger every interactive element;
-- the traversal order makes sense and never traps focus;
-- focus indicators stay visible at every contrast and text-size setting;
-- anything that only works through a gesture has a keyboard route;
-- the app's own shortcuts leave system ones (Cmd+C, Cmd+V, Cmd+Tab) alone.
+Audit that the keyboard alone reaches and triggers everything, order never traps focus, focus stays visible, gestures have a keyboard route, and system shortcuts stay free; focus-system mechanics go to `hig-inputs`. Full audit list: [Assistive technology review](references/assistive-tech-review.md).
 
 ## Traversal order
 
@@ -314,70 +238,19 @@ the ordering audit and its accessibility impact are reported here.
 
 ## Assistive Access (iOS 18+)
 
-This pared-down system mode serves people with cognitive disabilities, and
-apps should behave well inside it.
-
-```swift
-struct LibraryScreen: View {
-    @Environment(\.accessibilityAssistiveAccessEnabled) private var assistiveAccess
-
-    var body: some View {
-        if assistiveAccess { SimpleLibraryView() } else { FullLibraryView() }
-    }
-}
-```
-
-- Less on screen: fewer controls, bigger targets, flatter navigation.
-- Literal, plain wording in labels and instructions.
-- Only a few choices at a time.
-- Try it under Settings > Accessibility > Assistive Access.
-
-From iOS 26 an app can also declare `UISupportsAssistiveAccess` in its
-Info.plist and provide a dedicated `AssistiveAccess` scene.
+Read `accessibilityAssistiveAccessEnabled` and offer a simpler screen: fewer controls, bigger targets, literal wording, few choices. Example and the iOS 26 scene option: [Assistive technology review](references/assistive-tech-review.md).
 
 ## UIKit
 
-- `isAccessibilityElement = true` on custom views that carry meaning.
-- `accessibilityLabel` on every interactive element without visible text.
-- Change traits with `.insert()` and `.remove()` instead of assigning:
-  `badgeView.accessibilityTraits.insert(.button)`,
-  `badgeView.accessibilityTraits.remove(.staticText)`.
-- `accessibilityViewIsModal = true` on custom overlays to keep focus inside.
-- Post `.announcement` for passing status, `.layoutChanged` with a target for
-  partial updates, `.screenChanged` for full transitions.
+Custom views that carry meaning set `isAccessibilityElement`, labels and traits (insert and remove, never assign), overlays set `accessibilityViewIsModal`, and changes post the matching notification. Details: [Assistive technology review](references/assistive-tech-review.md).
 
 ## AppKit
 
-AppKit accessibility rests on `NSAccessibilityProtocol` plus role-specific
-protocols. Standard controls already publish most of what assistive apps need,
-including notifications, so prefer them and customise only where the defaults
-fall short.
-
-- A custom `NSView` adopts the right role behaviour and reports its role,
-  label, value and supported actions accurately.
-- Items with no view behind them use `NSAccessibilityElement`.
-- Post `NSAccessibility` notifications when a change must reach assistive
-  apps.
-
-The full custom-view example (a toggle-like `NSView` returning role, label,
-"On"/"Off" value and a press action, posting `.valueChanged` when its state
-changes) and `NSAccessibilityElement` usage are in
-[code patterns](references/a11y-patterns.md#appkit).
+Prefer standard controls; custom `NSView`s report role, label, value and actions, viewless items use `NSAccessibilityElement`, and changes post `NSAccessibility` notifications. Details: [Assistive technology review](references/assistive-tech-review.md).
 
 ## Custom content
 
-`.accessibilityCustomContent` attaches extra labelled facts to an element.
-By default VoiceOver offers them only on request (More Content rotor); with
-`importance: .high` they are read along with the element.
-
-```swift
-HotelCard(hotel: hotel)
-    .accessibilityCustomContent("Nightly rate", Text(hotel.rateText), importance: .high)
-    .accessibilityCustomContent("Guest score", Text(hotel.scoreText))
-```
-
-More UIKit, AppKit and custom-content examples:
-[code patterns](references/a11y-patterns.md).
+`.accessibilityCustomContent` adds labelled facts, offered on request unless `importance: .high`. Example: [Assistive technology review](references/assistive-tech-review.md).
 
 ## App Store Accessibility Nutrition Labels
 
@@ -396,41 +269,11 @@ only recommended after you:
 
 ### By hand
 
-| Tool | What to do | Where |
-|---|---|---|
-| Accessibility Inspector | Run an audit against the Simulator or a device; it reports contrast issues, absent labels and wrong traits | Xcode > Open Developer Tool |
-| VoiceOver | Swipe from the first element to the last on each screen | Settings > Accessibility > VoiceOver |
-| Voice Control | Say "Show Names", then "Show Numbers" | Settings > Accessibility > Voice Control |
-| Full Keyboard Access | Press Tab across each screen and confirm each control receives focus | Settings > Accessibility > Keyboards > Full Keyboard Access |
-| Switch Control | Watch the scan order; gesture features need custom actions | Settings > Accessibility > Switch Control |
-| Dynamic Type | Step through the whole size range | Settings > Accessibility > Display & Text Size > Larger Text |
+Accessibility Inspector, VoiceOver, Voice Control, Full Keyboard Access, Switch Control and the Dynamic Type range, each checked per screen. Tool table: [Assistive technology review](references/assistive-tech-review.md).
 
 ### With XCTest
 
-UI tests can assert accessibility through `XCUIElement` attributes. The useful
-ones in `XCUIElementAttributes` are `identifier`, `label`, `title`, `value`,
-`placeholderValue`, `isSelected`, `isEnabled` and `hasFocus`.
-
-```swift
-@MainActor
-func testFocusReturnsAfterSheet() {
-    let app = XCUIApplication()
-    app.launch()
-
-    let opener = app.buttons["Seat map"]
-    opener.tap()
-    app.buttons["Done"].tap()
-    XCTAssertTrue(opener.hasFocus)
-}
-```
-
-A row test (querying `app.cells["id"]`, asserting `exists`, `isEnabled`, a
-non-empty `label` and a nested `buttons[...]` query) is in
-[code patterns](references/a11y-patterns.md#automated-checks-with-xctest).
-
-`hasFocus` reports keyboard focus (Full Keyboard Access, hardware keyboard),
-not the VoiceOver cursor, which XCTest cannot observe. Confirm VoiceOver focus
-restoration by hand as well.
+`XCUIElement` attributes assert identifiers, labels, values and keyboard focus; `hasFocus` does not see the VoiceOver cursor, so confirm that by hand. Example: [Assistive technology review](references/assistive-tech-review.md).
 
 ## Mistakes seen most often
 

package/pipeline/skills/shared/external/ios-accessibility/references/assistive-tech-review.md

@@ -0,0 +1,224 @@
+# Assistive technology review
+
+<!-- toc -->
+- [Reduce Motion](#reduce-motion)
+- [Transparency, contrast, bold text](#transparency-contrast-bold-text)
+- [Voice Control](#voice-control)
+- [Switch Control](#switch-control)
+- [Full Keyboard Access](#full-keyboard-access)
+- [Assistive Access (iOS 18+)](#assistive-access-ios-18)
+- [UIKit](#uikit)
+- [AppKit](#appkit)
+- [Custom content](#custom-content)
+<!-- /toc -->
+
+Reduce Motion and appearance code, the review rules for Voice Control, Switch Control, Full Keyboard Access and Assistive Access, the UIKit and AppKit specifics, custom content, and the manual and XCTest testing steps. SKILL.md keeps the ground rules, focus, traversal order and the review checklist.
+
+## Reduce Motion
+
+With Reduce Motion on, replace movement with a crossfade or with no animation.
+
+```swift
+struct FilterDrawer: View {
+    @Environment(\.accessibilityReduceMotion) private var reduceMotion
+    @State private var isExpanded = false
+
+    var body: some View {
+        VStack {
+            Button("Filters") {
+                withAnimation(reduceMotion ? nil : .spring()) { isExpanded.toggle() }
+            }
+            if isExpanded {
+                PanelView()
+                    .transition(reduceMotion ? .opacity : .move(edge: .bottom))
+            }
+        }
+    }
+}
+```
+
+Go through every moving transition, not just the obvious one: row removal,
+quantity changes, presenting a sheet or checkout, dismissing a modal. Slides,
+bounces, parallax, springs and big spatial moves become fades, an immediate
+jump to the end state, or no animation at all.
+
+## Transparency, contrast, bold text
+
+```swift
+@Environment(\.accessibilityReduceTransparency) private var reduceTransparency
+@Environment(\.colorSchemeContrast) private var contrast
+@Environment(\.legibilityWeight) private var legibilityWeight
+
+private let base = Color(uiColor: .systemBackground)
+
+var body: some View {
+    Text(caption)
+        .foregroundStyle(contrast == .increased ? .primary : .secondary)
+        .fontWeight(legibilityWeight == .bold ? .bold : .regular)
+        .background(reduceTransparency ? base : base.opacity(0.8))
+}
+```
+
+## Voice Control
+
+Spoken commands find their target through its accessibility label: the label
+is the name a person says to tap the element. An element with no label, or a label nobody can say, cannot be
+targeted by voice.
+
+- Every interactive element needs a label a person can say aloud. No labels
+  made only of emoji or symbols.
+- Labels must differ among the elements on screen at the same time;
+  duplicates push users onto overlay numbers.
+- Add `accessibilityInputLabels` before feature freeze, not as late polish,
+  wherever a label is long, clumsy, localized, full of acronyms, or usually
+  shortened when spoken. Both Full Keyboard Access and Voice Control consume
+  them. List the entries most important first.
+- Good candidates: media controls, settings and account links, per-row
+  actions that repeat down a list, quantity steppers, localized labels that
+  contain product names or acronyms.
+- Turn Voice Control on and say "Show Names", then "Show Numbers". The names
+  overlay proves labels can be spoken; the numbers overlay proves every
+  visible target stays reachable even if its name is missing, duplicated or
+  awkward. A review
+  checks both overlays.
+
+Examples and speakable-label guidance: [code patterns](a11y-patterns.md).
+
+## Switch Control
+
+Switch Control steps through accessibility elements one at a time in reading
+order, so grouping and custom actions matter more here than anywhere else.
+
+- `.accessibilityElement(children: .combine)` merges related pieces and
+  removes scan stops. Each remaining stop should mean something and do
+  something.
+- Anything hidden from VoiceOver as decorative is skipped by Switch Control
+  too.
+- Multi-finger gestures, long presses and swipe-to-delete are out of reach
+  for switch users. Offer those operations as `.accessibilityAction(named:)`; Switch
+  Control lists them in a menu.
+- In point scanning mode, a custom control whose tappable area is unusual
+  must report an `accessibilityFrame` that matches that area.
+
+## Full Keyboard Access
+
+Available since iOS and iPadOS 13.4, Full Keyboard Access lets people run the
+app from a hardware keyboard. This skill owns the review: can everything be
+reached, is it clearly labelled, is focus visible, does it work without touch.
+`UIFocusGuide`, tvOS focus, scene-focused values, directional movement,
+`focusSection()`, `@FocusState`, `.focusable()`, custom cards that Tab jumps
+over, and Tab traversal bugs in general go to `hig-inputs` first; only the accessibility finding
+stays here.
+
+Audit:
+
+- the keyboard alone can reach and trigger every interactive element;
+- the traversal order makes sense and never traps focus;
+- focus indicators stay visible at every contrast and text-size setting;
+- anything that only works through a gesture has a keyboard route;
+- the app's own shortcuts leave system ones (Cmd+C, Cmd+V, Cmd+Tab) alone.
+
+## Assistive Access (iOS 18+)
+
+This pared-down system mode serves people with cognitive disabilities, and
+apps should behave well inside it.
+
+```swift
+struct LibraryScreen: View {
+    @Environment(\.accessibilityAssistiveAccessEnabled) private var assistiveAccess
+
+    var body: some View {
+        if assistiveAccess { SimpleLibraryView() } else { FullLibraryView() }
+    }
+}
+```
+
+- Less on screen: fewer controls, bigger targets, flatter navigation.
+- Literal, plain wording in labels and instructions.
+- Only a few choices at a time.
+- Try it under Settings > Accessibility > Assistive Access.
+
+From iOS 26 an app can also declare `UISupportsAssistiveAccess` in its
+Info.plist and provide a dedicated `AssistiveAccess` scene.
+
+## UIKit
+
+- `isAccessibilityElement = true` on custom views that carry meaning.
+- `accessibilityLabel` on every interactive element without visible text.
+- Change traits with `.insert()` and `.remove()` instead of assigning:
+  `badgeView.accessibilityTraits.insert(.button)`,
+  `badgeView.accessibilityTraits.remove(.staticText)`.
+- `accessibilityViewIsModal = true` on custom overlays to keep focus inside.
+- Post `.announcement` for passing status, `.layoutChanged` with a target for
+  partial updates, `.screenChanged` for full transitions.
+
+## AppKit
+
+AppKit accessibility rests on `NSAccessibilityProtocol` plus role-specific
+protocols. Standard controls already publish most of what assistive apps need,
+including notifications, so prefer them and customise only where the defaults
+fall short.
+
+- A custom `NSView` adopts the right role behaviour and reports its role,
+  label, value and supported actions accurately.
+- Items with no view behind them use `NSAccessibilityElement`.
+- Post `NSAccessibility` notifications when a change must reach assistive
+  apps.
+
+The full custom-view example (a toggle-like `NSView` returning role, label,
+"On"/"Off" value and a press action, posting `.valueChanged` when its state
+changes) and `NSAccessibilityElement` usage are in
+[code patterns](a11y-patterns.md#appkit).
+
+## Custom content
+
+`.accessibilityCustomContent` attaches extra labelled facts to an element.
+By default VoiceOver offers them only on request (More Content rotor); with
+`importance: .high` they are read along with the element.
+
+```swift
+HotelCard(hotel: hotel)
+    .accessibilityCustomContent("Nightly rate", Text(hotel.rateText), importance: .high)
+    .accessibilityCustomContent("Guest score", Text(hotel.scoreText))
+```
+
+More UIKit, AppKit and custom-content examples:
+[code patterns](a11y-patterns.md).
+
+### By hand
+
+| Tool | What to do | Where |
+|---|---|---|
+| Accessibility Inspector | Run an audit against the Simulator or a device; it reports contrast issues, absent labels and wrong traits | Xcode > Open Developer Tool |
+| VoiceOver | Swipe from the first element to the last on each screen | Settings > Accessibility > VoiceOver |
+| Voice Control | Say "Show Names", then "Show Numbers" | Settings > Accessibility > Voice Control |
+| Full Keyboard Access | Press Tab across each screen and confirm each control receives focus | Settings > Accessibility > Keyboards > Full Keyboard Access |
+| Switch Control | Watch the scan order; gesture features need custom actions | Settings > Accessibility > Switch Control |
+| Dynamic Type | Step through the whole size range | Settings > Accessibility > Display & Text Size > Larger Text |
+
+### With XCTest
+
+UI tests can assert accessibility through `XCUIElement` attributes. The useful
+ones in `XCUIElementAttributes` are `identifier`, `label`, `title`, `value`,
+`placeholderValue`, `isSelected`, `isEnabled` and `hasFocus`.
+
+```swift
+@MainActor
+func testFocusReturnsAfterSheet() {
+    let app = XCUIApplication()
+    app.launch()
+
+    let opener = app.buttons["Seat map"]
+    opener.tap()
+    app.buttons["Done"].tap()
+    XCTAssertTrue(opener.hasFocus)
+}
+```
+
+A row test (querying `app.cells["id"]`, asserting `exists`, `isEnabled`, a
+non-empty `label` and a nested `buttons[...]` query) is in
+[code patterns](a11y-patterns.md#automated-checks-with-xctest).
+
+`hasFocus` reports keyboard focus (Full Keyboard Access, hardware keyboard),
+not the VoiceOver cursor, which XCTest cannot observe. Confirm VoiceOver focus
+restoration by hand as well.

package/pipeline/skills/shared/external/ios-localization/SKILL.md

@@ -251,30 +251,7 @@ parsing, `Date.IntervalFormatStyle`, `URL.FormatStyle` and reusable formatter
 API design belong to `swift-formatstyle`. Here, only point out locale risks and
 testing for those, unless the user explicitly asks for an implementation.
 
-```swift
-let flight = Date.now
-flight.formatted(date: .long, time: .shortened)
-// en_US "June 3, 2026 at 4:05 PM", de_DE "3. Juni 2026 um 16:05"; ja_JP uses year-month-day order
-flight.formatted(.dateTime.month(.wide).day().year())
-Text(flight, format: .dateTime.weekday().hour().minute())
-
-let visitors = 1_284_503
-visitors.formatted()                                    // "1,284,503" / "1.284.503"
-3.14159.formatted(.number.precision(.fractionLength(2)))
-0.18.formatted(.percent)                                 // "18%"
-Decimal(59.9).formatted(.currency(code: "USD"))
-Decimal(59.9).formatted(.currency(code: "EUR"))          // symbol position follows locale
-
-Measurement(value: 42, unit: UnitLength.kilometers)
-    .formatted(.measurement(width: .wide))               // miles in en_US
-Measurement(value: 21, unit: UnitTemperature.celsius)
-    .formatted(.measurement(width: .abbreviated))        // Fahrenheit in en_US
-
-Duration.seconds(5_025).formatted(.time(pattern: .hourMinuteSecond))   // "1:23:45"
-var author = PersonNameComponents(); author.givenName = "Aiko"; author.familyName = "Tanaka"
-author.formatted(.name(style: .long))                    // order differs en_US vs ja_JP
-["tea", "coffee", "juice"].formatted(.list(type: .and))  // "tea, coffee, and juice"; French joins with "et" and no serial comma
-```
+Code: [Locale-Aware Formatting with FormatStyle](references/code-examples.md#locale-aware-formatting-with-formatstyle).
 
 Full coverage of every style is in
 [references/formatstyle-locale.md](references/formatstyle-locale.md).
@@ -363,3 +340,4 @@ Rules: prefer `.leading` and `.trailing` (they flip) over `.left` and `.right`
 - [references/formatstyle-locale.md](references/formatstyle-locale.md):
   FormatStyle per value type, forcing a locale, RTL, `@ScaledMetric` and
   Accessibility Inspector.
+- [Code examples](references/code-examples.md): open for the full code behind Locale-Aware Formatting with FormatStyle.

package/pipeline/skills/shared/external/ios-localization/references/code-examples.md

@@ -0,0 +1,30 @@
+# iOS Localization Code Examples
+
+Full code samples for the SKILL.md sections that link here. The rules and the decision guidance stay in SKILL.md; each heading below matches the SKILL.md section the code belongs to.
+
+## Locale-Aware Formatting with FormatStyle
+
+```swift
+let flight = Date.now
+flight.formatted(date: .long, time: .shortened)
+// en_US "June 3, 2026 at 4:05 PM", de_DE "3. Juni 2026 um 16:05"; ja_JP uses year-month-day order
+flight.formatted(.dateTime.month(.wide).day().year())
+Text(flight, format: .dateTime.weekday().hour().minute())
+
+let visitors = 1_284_503
+visitors.formatted()                                    // "1,284,503" / "1.284.503"
+3.14159.formatted(.number.precision(.fractionLength(2)))
+0.18.formatted(.percent)                                 // "18%"
+Decimal(59.9).formatted(.currency(code: "USD"))
+Decimal(59.9).formatted(.currency(code: "EUR"))          // symbol position follows locale
+
+Measurement(value: 42, unit: UnitLength.kilometers)
+    .formatted(.measurement(width: .wide))               // miles in en_US
+Measurement(value: 21, unit: UnitTemperature.celsius)
+    .formatted(.measurement(width: .abbreviated))        // Fahrenheit in en_US
+
+Duration.seconds(5_025).formatted(.time(pattern: .hourMinuteSecond))   // "1:23:45"
+var author = PersonNameComponents(); author.givenName = "Aiko"; author.familyName = "Tanaka"
+author.formatted(.name(style: .long))                    // order differs en_US vs ja_JP
+["tea", "coffee", "juice"].formatted(.list(type: .and))  // "tea, coffee, and juice"; French joins with "et" and no serial comma
+```

package/pipeline/skills/shared/external/ios-networking/SKILL.md

@@ -101,42 +101,7 @@ for try await line in stream.lines {
 Put the client behind a protocol. Tests then substitute a double instead of
 mocking URLSession.
 
-```swift
-protocol APIClientProtocol: Sendable {
-    func fetch<Reply: Decodable & Sendable>(_ endpoint: Endpoint, as kind: Reply.Type) async throws -> Reply
-    func send<Reply: Decodable & Sendable>(_ endpoint: Endpoint, json payload: some Encodable & Sendable,
-                                           as kind: Reply.Type) async throws -> Reply
-    func perform(_ endpoint: Endpoint) async throws
-    func upload<Reply: Decodable & Sendable>(_ endpoint: Endpoint, bytes: Data,
-                                             as kind: Reply.Type) async throws -> Reply
-}
-
-struct Endpoint: Sendable {
-    enum HTTPMethod: String, Sendable { case get, post, put, patch, delete }
-
-    var path: String
-    var method: HTTPMethod = .get
-    var queryItems: [URLQueryItem] = []
-    var headers: [String: String] = [:]
-    var body: Data? = nil
-    var cachePolicy: URLRequest.CachePolicy = .useProtocolCachePolicy
-    var timeoutInterval: TimeInterval = 30
-
-    func urlRequest(relativeTo baseURL: URL) throws -> URLRequest {
-        guard var parts = URLComponents(url: baseURL.appending(path: path),
-                                        resolvingAgainstBaseURL: true) else {
-            throw NetworkError.invalidURL
-        }
-        if !queryItems.isEmpty { parts.queryItems = queryItems }
-        guard let url = parts.url else { throw NetworkError.invalidURL }
-        var request = URLRequest(url: url, cachePolicy: cachePolicy, timeoutInterval: timeoutInterval)
-        request.httpMethod = method.rawValue.uppercased()
-        request.httpBody = body
-        request.allHTTPHeaderFields = headers
-        return request
-    }
-}
-```
+Code: [Protocol-based client](references/code-examples.md#protocol-based-client).
 
 A bad URL is a thrown `NetworkError.invalidURL`, never a crash; nothing in
 this skill force-unwraps.
@@ -269,28 +234,7 @@ Retry inside structured concurrency so cancellation stops the loop. Never
 retry cancellation or a 4xx, with 429 as the exception; 5xx and transient
 transport errors are fair game.
 
-```swift
-func withRetry<T: Sendable>(
-    maxAttempts: Int = 3,
-    initialDelay: Duration = .seconds(1),
-    maxDelay: Duration = .seconds(30),
-    shouldRetry: @Sendable (any Error) -> Bool = isTransient,
-    operation: @Sendable () async throws -> T
-) async throws -> T {
-    precondition(maxAttempts > 0, "maxAttempts must be at least 1")
-    for attempt in 0..<maxAttempts {
-        try Task.checkCancellation()
-        do {
-            return try await operation()
-        } catch {
-            guard attempt < maxAttempts - 1, shouldRetry(error) else { throw error }
-            let capped = min(initialDelay * (1 << attempt), maxDelay)
-            try await Task.sleep(for: capped + capped * Double.random(in: 0...0.1))
-        }
-    }
-    preconditionFailure("the last attempt always returns or throws")
-}
-```
+Code: [Retry with exponential backoff](references/code-examples.md#retry-with-exponential-backoff).
 
 There is no sleep after the last attempt: its error is rethrown at once. The
 `isTransient` predicate is in
@@ -412,3 +356,4 @@ path instead of failing immediately. Implement
 - [lightweight clients](references/lightweight-clients.md): struct-of-closures client injected through `init` for tests and previews.
 - [Network framework guide](references/network-framework.md): `NWConnection`, `NWListener`, `NWBrowser`, `NWPathMonitor`, raw TCP, UDP and WebSocket, iOS 26 `NetworkConnection`.
 - [file storage patterns](references/file-storage-patterns.md): directory choice, `FileProtectionType`, backup exclusion, low-storage handling.
+- [Code examples](references/code-examples.md): open for the full code behind Protocol-based client, Retry with exponential backoff.