@mmerterden/multi-agent-pipeline 16.18.0 → 16.19.0

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

@@ -1,6 +1,6 @@
 ---
 name: hig-inputs
-description: "Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered. Use when designing or reviewing input controls, forms or text entry on an Apple platform."
+description: "Apple Human Interface Guidelines for input methods: touch gestures, keyboards, Apple Pencil, pointing devices, game controllers, Digital Crown and spatial input. Use when designing or reviewing input controls, forms or text entry on an Apple platform."
 risk: unknown
 source: community
 date_added: '2026-02-27'
@@ -64,23 +64,23 @@ Check for `.claude/apple-design-context.md` before asking questions. Use existin
 
 15. **Gyroscope, accelerometer, UWB: use judiciously.** Suits gaming, fitness, AR. Not for essential tasks. Provide calibration and reset. For UWB, communicate distance and direction with visual or haptic cues.
 
-## Reference Index
-
-| Reference | Topic | Key content |
-|---|---|---|
-| [gestures.md](references/gestures.md) | Touch gestures | Tap, swipe, pinch, long press, drag, system gestures |
-| [apple-pencil-and-scribble.md](references/apple-pencil-and-scribble.md) | Apple Pencil | Precision, pressure, tilt, hover, handwriting |
-| [keyboards.md](references/keyboards.md) | Keyboards | Shortcuts, navigation, software keyboard, Command key |
-| [game-controls.md](references/game-controls.md) | Game controllers | MFi, extended gamepad, remapping, fallbacks |
-| [pointing-devices.md](references/pointing-devices.md) | Pointer/trackpad | Hover, cursor morphing, trackpad gestures |
-| [digital-crown.md](references/digital-crown.md) | Digital Crown | Scrolling, value adjustment, haptic detents |
-| [eyes.md](references/eyes.md) | Eye tracking | Look and tap, gaze targeting, hit target sizing |
-| [spatial-interactions.md](references/spatial-interactions.md) | Spatial input | Hand gestures, direct manipulation, immersive input |
-| [focus-and-selection.md](references/focus-and-selection.md) | Focus system | tvOS/visionOS navigation, focus indicators, groups |
-| [remotes.md](references/remotes.md) | Remotes | Touch surface, clickpad, simple interactions |
-| [gyro-and-accelerometer.md](references/gyro-and-accelerometer.md) | Motion sensors | Gyroscope, accelerometer, calibration, gaming |
-| [nearby-interactions.md](references/nearby-interactions.md) | Nearby interactions | U1 chip, directional finding, proximity triggers |
-| [camera-control.md](references/camera-control.md) | Camera Control | iPhone camera hardware button, quick launch |
+## Topics
+
+| Topic | Key content |
+|---|---|
+| Touch gestures | Tap, swipe, pinch, long press, drag, system gestures |
+| Apple Pencil | Precision, pressure, tilt, hover, handwriting |
+| Keyboards | Shortcuts, navigation, software keyboard, Command key |
+| Game controllers | MFi, extended gamepad, remapping, fallbacks |
+| Pointer/trackpad | Hover, cursor morphing, trackpad gestures |
+| Digital Crown | Scrolling, value adjustment, haptic detents |
+| Eye tracking | Look and tap, gaze targeting, hit target sizing |
+| Spatial input | Hand gestures, direct manipulation, immersive input |
+| Focus system | tvOS/visionOS navigation, focus indicators, groups |
+| Remotes | Touch surface, clickpad, simple interactions |
+| Motion sensors | Gyroscope, accelerometer, calibration, gaming |
+| Nearby interactions | U1 chip, directional finding, proximity triggers |
+| Camera Control | iPhone camera hardware button, quick launch |
 
 ## Output Format
 

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

@@ -28,35 +28,35 @@ Check for `.claude/apple-design-context.md` before asking questions. Use existin
 
 8. **Respect user attention.** Consolidate notifications, minimize interruptions, give users control over alerts. Never use notifications for marketing.
 
-## Reference Index
-
-| Reference | Topic | Key content |
-|---|---|---|
-| [charting-data.md](references/charting-data.md) | Charting Data | Data visualization patterns, accessible charts, interactive elements |
-| [collaboration-and-sharing.md](references/collaboration-and-sharing.md) | Collaboration & Sharing | Share sheets, activity views, collaborative editing, SharePlay |
-| [drag-and-drop.md](references/drag-and-drop.md) | Drag and Drop | Drag sources, drop targets, spring loading, multi-item drag, visual feedback |
-| [entering-data.md](references/entering-data.md) | Entering Data | Text fields, pickers, steppers, input validation, keyboard types, autofill |
-| [feedback.md](references/feedback.md) | Feedback | Alerts, action sheets, haptic patterns, sound feedback, visual indicators |
-| [file-management.md](references/file-management.md) | File Management | Document browser, file providers, iCloud integration, document lifecycle |
-| [going-full-screen.md](references/going-full-screen.md) | Going Full Screen | Full-screen transitions, immersive content, exiting full screen |
-| [launching.md](references/launching.md) | Launching | Launch screens, state restoration, cold vs warm launch |
-| [live-viewing-apps.md](references/live-viewing-apps.md) | Live Viewing Apps | Live content display, real-time updates, Live Activities, Dynamic Island |
-| [loading.md](references/loading.md) | Loading | Activity indicators, progress views, skeleton screens, lazy loading, placeholders |
-| [managing-accounts.md](references/managing-accounts.md) | Managing Accounts | Sign in with Apple, passkeys, account creation, credential autofill, account deletion |
-| [managing-notifications.md](references/managing-notifications.md) | Managing Notifications | Permission requests, grouping, actionable notifications, provisional delivery |
-| [modality.md](references/modality.md) | Modality | Sheets, alerts, popovers, full-screen modals, when to use each |
-| [multitasking.md](references/multitasking.md) | Multitasking | iPad Split View, Slide Over, Stage Manager, responsive layout, size class transitions |
-| [offering-help.md](references/offering-help.md) | Offering Help | Contextual tips, onboarding hints, help menus, support links |
-| [onboarding.md](references/onboarding.md) | Onboarding | Welcome screens, feature highlights, progressive onboarding, skip options |
-| [playing-audio.md](references/playing-audio.md) | Playing Audio | Audio sessions, background audio, Now Playing, audio routing, interruptions |
-| [playing-haptics.md](references/playing-haptics.md) | Playing Haptics | Core Haptics, UIFeedbackGenerator, haptic patterns, custom haptics |
-| [playing-video.md](references/playing-video.md) | Playing Video | Video player controls, picture-in-picture, AirPlay, full-screen video |
-| [printing.md](references/printing.md) | Printing | Print dialogs, page setup, AirPrint integration |
-| [ratings-and-reviews.md](references/ratings-and-reviews.md) | Ratings & Reviews | SKStoreReviewController, timing, frequency limits, in-app feedback |
-| [searching.md](references/searching.md) | Searching | Search bars, suggestions, scoped search, results display, recents |
-| [settings.md](references/settings.md) | Settings | In-app vs Settings app, preference organization, toggles, defaults |
-| [undo-and-redo.md](references/undo-and-redo.md) | Undo and Redo | Shake to undo, undo/redo stack, multi-level undo |
-| [workouts.md](references/workouts.md) | Workouts | Workout sessions, live metrics, Always On display, summaries, HealthKit |
+## Topics
+
+| Topic | Key content |
+|---|---|
+| Charting Data | Data visualization patterns, accessible charts, interactive elements |
+| Collaboration & Sharing | Share sheets, activity views, collaborative editing, SharePlay |
+| Drag and Drop | Drag sources, drop targets, spring loading, multi-item drag, visual feedback |
+| Entering Data | Text fields, pickers, steppers, input validation, keyboard types, autofill |
+| Feedback | Alerts, action sheets, haptic patterns, sound feedback, visual indicators |
+| File Management | Document browser, file providers, iCloud integration, document lifecycle |
+| Going Full Screen | Full-screen transitions, immersive content, exiting full screen |
+| Launching | Launch screens, state restoration, cold vs warm launch |
+| Live Viewing Apps | Live content display, real-time updates, Live Activities, Dynamic Island |
+| Loading | Activity indicators, progress views, skeleton screens, lazy loading, placeholders |
+| Managing Accounts | Sign in with Apple, passkeys, account creation, credential autofill, account deletion |
+| Managing Notifications | Permission requests, grouping, actionable notifications, provisional delivery |
+| Modality | Sheets, alerts, popovers, full-screen modals, when to use each |
+| Multitasking | iPad Split View, Slide Over, Stage Manager, responsive layout, size class transitions |
+| Offering Help | Contextual tips, onboarding hints, help menus, support links |
+| Onboarding | Welcome screens, feature highlights, progressive onboarding, skip options |
+| Playing Audio | Audio sessions, background audio, Now Playing, audio routing, interruptions |
+| Playing Haptics | Core Haptics, UIFeedbackGenerator, haptic patterns, custom haptics |
+| Playing Video | Video player controls, picture-in-picture, AirPlay, full-screen video |
+| Printing | Print dialogs, page setup, AirPrint integration |
+| Ratings & Reviews | SKStoreReviewController, timing, frequency limits, in-app feedback |
+| Searching | Search bars, suggestions, scoped search, results display, recents |
+| Settings | In-app vs Settings app, preference organization, toggles, defaults |
+| Undo and Redo | Shake to undo, undo/redo stack, multi-level undo |
+| Workouts | Workout sessions, live metrics, Always On display, summaries, HealthKit |
 
 ## Pattern Selection Guide
 
@@ -72,7 +72,7 @@ Check for `.claude/apple-design-context.md` before asking questions. Use existin
 
 ## Output Format
 
-1. **Recommended pattern with rationale**, citing the relevant reference file.
+1. **Recommended pattern with rationale**, citing the relevant HIG topic.
 2. **Step-by-step implementation** covering each screen or state.
 3. **Platform variations** for targeted platforms.
 4. **Common pitfalls** that violate HIG for this pattern.

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

@@ -28,17 +28,17 @@ Check for `.claude/apple-design-context.md` before asking questions. Use existin
 
 8. **Games: own paradigm.** Free to define in-game interaction models, but still respect platform conventions for system interactions (notifications, accessibility, controllers).
 
-## Reference Index
-
-| Reference | Topic | Key content |
-|---|---|---|
-| [designing-for-ios.md](references/designing-for-ios.md) | iOS | Touch, tab bars, navigation stacks, gestures, screen sizes, safe areas |
-| [designing-for-ipados.md](references/designing-for-ipados.md) | iPadOS | Multitasking, sidebars, pointer, keyboard, Apple Pencil, Stage Manager |
-| [designing-for-macos.md](references/designing-for-macos.md) | macOS | Menu bars, toolbars, window management, keyboard shortcuts, dense layouts, Dock |
-| [designing-for-tvos.md](references/designing-for-tvos.md) | tvOS | Focus engine, Siri Remote, lean-back experience, content-forward, parallax |
-| [designing-for-visionos.md](references/designing-for-visionos.md) | visionOS | Spatial computing, windows/volumes/spaces, eye tracking, hand gestures, depth |
-| [designing-for-watchos.md](references/designing-for-watchos.md) | watchOS | Glanceable UI, Digital Crown, complications, notifications, haptics |
-| [designing-for-games.md](references/designing-for-games.md) | Games | Controllers, immersive experiences, platform-specific conventions, accessibility |
+## Topics
+
+| Topic | Key content |
+|---|---|
+| iOS | Touch, tab bars, navigation stacks, gestures, screen sizes, safe areas |
+| iPadOS | Multitasking, sidebars, pointer, keyboard, Apple Pencil, Stage Manager |
+| macOS | Menu bars, toolbars, window management, keyboard shortcuts, dense layouts, Dock |
+| tvOS | Focus engine, Siri Remote, lean-back experience, content-forward, parallax |
+| visionOS | Spatial computing, windows/volumes/spaces, eye tracking, hand gestures, depth |
+| watchOS | Glanceable UI, Digital Crown, complications, notifications, haptics |
+| Games | Controllers, immersive experiences, platform-specific conventions, accessibility |
 
 ## Decision Framework
 

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

@@ -1,6 +1,6 @@
 ---
 name: hig-technologies
-description: "Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered. Use when designing or reviewing a feature built on an Apple technology such as Sign in with Apple, Wallet or Maps."
+description: "Apple Human Interface Guidelines for Apple technologies: Siri, Apple Pay, Wallet, HealthKit, CarPlay, iCloud, Maps, in-app purchase and Sign in with Apple. Use when designing or reviewing a feature built on an Apple technology such as Sign in with Apple, Wallet or Maps."
 risk: unknown
 source: community
 date_added: '2026-02-27'
@@ -62,38 +62,38 @@ Check for `.claude/apple-design-context.md` before asking questions. Use existin
 
 13. **Baseline requirement.** Every element has a meaningful VoiceOver label, trait, and action. Support Dynamic Type, Switch Control, and other assistive technologies. Test entirely with VoiceOver enabled.
 
-## Reference Index
-
-| Reference | Topic | Key content |
-|---|---|---|
-| [siri.md](references/siri.md) | Siri | Intents, shortcuts, voice interaction, App Shortcuts |
-| [apple-pay.md](references/apple-pay.md) | Apple Pay | Payment buttons, checkout flow, security |
-| [tap-to-pay-on-iphone.md](references/tap-to-pay-on-iphone.md) | Tap to Pay | Merchant flows, contactless payment |
-| [in-app-purchase.md](references/in-app-purchase.md) | In-app purchase | Subscriptions, one-time purchases, transparency |
-| [healthkit.md](references/healthkit.md) | HealthKit | Health data access, privacy, permissions |
-| [carekit.md](references/carekit.md) | CareKit | Care plans, tasks, health management |
-| [researchkit.md](references/researchkit.md) | ResearchKit | Studies, informed consent, data collection |
-| [homekit.md](references/homekit.md) | HomeKit | Smart home control, device state, scenes |
-| [augmented-reality.md](references/augmented-reality.md) | ARKit | Spatial context, surface detection, setup |
-| [machine-learning.md](references/machine-learning.md) | Core ML | Predictions, smart features, confidence handling |
-| [generative-ai.md](references/generative-ai.md) | Generative AI | Attribution, editing, responsible AI, uncertainty |
-| [icloud.md](references/icloud.md) | iCloud | CloudKit, cross-device sync, conflict resolution |
-| [sign-in-with-apple.md](references/sign-in-with-apple.md) | Sign in with Apple | Authentication, privacy, button styles |
-| [id-verifier.md](references/id-verifier.md) | ID Verifier | Identity verification, document scanning |
-| [shareplay.md](references/shareplay.md) | SharePlay | Shared experiences, participant presence |
-| [airplay.md](references/airplay.md) | AirPlay | Media streaming, Now Playing, wireless display |
-| [carplay.md](references/carplay.md) | CarPlay | Driver safety, permitted app types, large targets |
-| [game-center.md](references/game-center.md) | Game Center | Achievements, leaderboards, multiplayer |
-| [voiceover.md](references/voiceover.md) | VoiceOver | Screen reader, labels, traits, accessibility |
-| [wallet.md](references/wallet.md) | Wallet | Passes, tickets, loyalty cards |
-| [nfc.md](references/nfc.md) | NFC | Tag reading, quick interactions, App Clips |
-| [maps.md](references/maps.md) | Maps | Location display, annotations, directions |
-| [mac-catalyst.md](references/mac-catalyst.md) | Mac Catalyst | iPad to Mac, menu bar, keyboard, pointer |
-| [live-photos.md](references/live-photos.md) | Live Photos | Motion capture, playback, editing |
-| [imessage-apps-and-stickers.md](references/imessage-apps-and-stickers.md) | iMessage apps | Messages extension, stickers, compact UI |
-| [shazamkit.md](references/shazamkit.md) | ShazamKit | Audio recognition, music identification |
-| [always-on.md](references/always-on.md) | Always-on display | Dimmed state, power efficiency, reduced updates |
-| [photo-editing.md](references/photo-editing.md) | Photo editing | System photo editor, filters, adjustments |
+## Topics
+
+| Topic | Key content |
+|---|---|
+| Siri | Intents, shortcuts, voice interaction, App Shortcuts |
+| Apple Pay | Payment buttons, checkout flow, security |
+| Tap to Pay | Merchant flows, contactless payment |
+| In-app purchase | Subscriptions, one-time purchases, transparency |
+| HealthKit | Health data access, privacy, permissions |
+| CareKit | Care plans, tasks, health management |
+| ResearchKit | Studies, informed consent, data collection |
+| HomeKit | Smart home control, device state, scenes |
+| ARKit | Spatial context, surface detection, setup |
+| Core ML | Predictions, smart features, confidence handling |
+| Generative AI | Attribution, editing, responsible AI, uncertainty |
+| iCloud | CloudKit, cross-device sync, conflict resolution |
+| Sign in with Apple | Authentication, privacy, button styles |
+| ID Verifier | Identity verification, document scanning |
+| SharePlay | Shared experiences, participant presence |
+| AirPlay | Media streaming, Now Playing, wireless display |
+| CarPlay | Driver safety, permitted app types, large targets |
+| Game Center | Achievements, leaderboards, multiplayer |
+| VoiceOver | Screen reader, labels, traits, accessibility |
+| Wallet | Passes, tickets, loyalty cards |
+| NFC | Tag reading, quick interactions, App Clips |
+| Maps | Location display, annotations, directions |
+| Mac Catalyst | iPad to Mac, menu bar, keyboard, pointer |
+| Live Photos | Motion capture, playback, editing |
+| iMessage apps | Messages extension, stickers, compact UI |
+| ShazamKit | Audio recognition, music identification |
+| Always-on display | Dimmed state, power efficiency, reduced updates |
+| Photo editing | System photo editor, filters, adjustments |
 
 ## Output Format
 

package/pipeline/skills/shared/external/ios-coding-standard/references/STANDARD.md

@@ -44,19 +44,19 @@ Most sensitive values in a flow are used and dropped, and those must not be pers
 // ✗ over-persistence  -  a value the flow throws away in 30 seconds now outlives logout
 //   and nobody owns deleting it
 try credentialStore.save(oneTimeCode, for: .verificationCode)
-UserDefaults.standard.set(passportNumber, forKey: "apisPassport")
+UserDefaults.standard.set(cardNumber, forKey: "checkoutCard")
 ```
 ```swift
 // ✓ transient: held by the flow's model, gone when the flow ends
-@Observable final class APISFormViewModel {
-    private var passportNumber: String = ""      // never leaves memory
+@Observable final class CheckoutFormViewModel {
+    private var cardNumber: String = ""          // never leaves memory
 }
 ```
 ```swift
 // ✓ persisted, because it must survive an app restart  -  Keychain, explicit accessibility,
 //   no iCloud sync
 try credentialStore.save(
-    membershipToken,
+    sessionToken,
     for: .authToken,
     accessibility: .whenUnlockedThisDeviceOnly
 )
@@ -129,19 +129,19 @@ Testability is a property of the production code. You cannot add it later by wri
 
 ```swift
 // ✗ untestable by construction  -  the assertion depends on today's date
-struct BoardingEligibility {
-    func canCheckIn(flight: Flight) -> Bool {
-        Date() > flight.departure.addingTimeInterval(-24 * 3600)
+struct ReturnEligibility {
+    func canReturn(order: Order) -> Bool {
+        Date() < order.deliveredAt.addingTimeInterval(30 * 24 * 3600)
     }
 }
 ```
 ```swift
 // ✓ the seam is one parameter wide
-struct BoardingEligibility {
+struct ReturnEligibility {
     let now: () -> Date
 
-    func canCheckIn(flight: Flight) -> Bool {
-        now() > flight.departure.addingTimeInterval(-24 * 3600)
+    func canReturn(order: Order) -> Bool {
+        now() < order.deliveredAt.addingTimeInterval(30 * 24 * 3600)
     }
 }
 ```
@@ -154,21 +154,21 @@ test can decide instead. A type that reaches for it has no seam, and no test dis
 ```swift
 // ✗ the rule is trapped inside the view model, behind a network call and a singleton
 func submit() async {
-    guard Session.shared.isLoggedIn, passengers.allSatisfy(\.hasDocument) else { return }
+    guard Session.shared.isLoggedIn, items.allSatisfy(\.isInStock) else { return }
     ...
 }
 ```
 ```swift
 // ✓ the decision is a value-returning function; the view model orchestrates
-func submitGate(for passengers: [Passenger], isLoggedIn: Bool) -> SubmitGate {
+func submitGate(for items: [CartItem], isLoggedIn: Bool) -> SubmitGate {
     guard isLoggedIn else { return .requiresLogin }
-    guard passengers.allSatisfy(\.hasDocument) else { return .missingDocuments }
+    guard items.allSatisfy(\.isInStock) else { return .outOfStock }
     return .allowed
 }
 ```
 **Why:** the second version is one line to test and reads as the business rule it is. The first
-needs a session, a network stub and a view model instance to answer "what happens when a document
-is missing".
+needs a session, a network stub and a view model instance to answer "what happens when an item
+is out of stock".
 
 Also: name test doubles for what they do  -  stub, spy, fake, mock, **builder**  -  one kind per file,
 and keep the signature identical to the real type, because a drifted double is the first thing the
@@ -185,22 +185,22 @@ answer is screen policy rather than entity state** → a named rule namespace.
 
 ```swift
 // ✗ a private computed property on the scene; the next screen needing this re-derives it
-private var showsStrikethrough: Bool { viewModel.segment.historyInfo?.crossed == true }
+private var showsStrikethrough: Bool { viewModel.item.priceInfo?.discounted == true }
 ```
 ```swift
 // ✓ a caseless enum of pure statics in the domain layer, each citing what it enforces
-enum ReservationRules {
-    /// BR-21: the overline strikes ONLY when `historyInfo.crossed` is true. When it is false the
-    /// history fields may still be populated (voluntary itinerary metadata)  -  do not strike then.
-    static func shouldRenderStrikethrough(_ segment: Segment) -> Bool {
-        segment.historyInfo?.crossed == true
+enum OrderRules {
+    /// BR-21: the list price strikes ONLY when `priceInfo.discounted` is true. When it is false the
+    /// price fields may still be populated (a list price with no promotion)  -  do not strike then.
+    static func shouldRenderStrikethrough(_ item: OrderItem) -> Bool {
+        item.priceInfo?.discounted == true
     }
 }
 ```
 ```swift
 // ✓ and the test repeats the citation token, so one grep reaches spec, code and test
-@Test("BR_21: no strikethrough when the segment is not crossed")
-func test_BR_21_noStrikethrough_whenNotCrossed() { ... }
+@Test("BR_21: no strikethrough when the item is not discounted")
+func test_BR_21_noStrikethrough_whenNotDiscounted() { ... }
 ```
 **Why:** the citation is not decoration, it is the rule's own measurement. A namespace whose
 functions cite nothing cannot be checked against anything, and a cited requirement with no test of
@@ -242,7 +242,7 @@ tangle  -  that reads worse, and it is a finding in the same way the opposite is
 
 ```swift
 // ✗ a date formatter living on the scene that happened to need it first
-extension PassengerAndFlightSelectionScene {
+extension OrderReviewScene {
     func formattedDate(_ raw: String?) -> String { ... }   // and again, later, in a mapper
 }
 ```
@@ -261,31 +261,31 @@ typed they get written a second time somewhere else, with a slightly different e
 ```swift
 // ✗ a component hiding as a computed property: cannot be previewed, cannot be reused,
 //   and it reads the whole view model so it never could be
-private var legSwitcher: some View {
+private var categoryTabs: some View {
     HStack {
-        ForEach(viewModel.segments) { segment in
-            Button { Task { await viewModel.onSegmentSelected(segment.segmentIndex) } } label: { ... }
+        ForEach(viewModel.categories) { category in
+            Button { Task { await viewModel.onCategorySelected(category.index) } } label: { ... }
         }
     }
 }
 ```
 ```swift
-// ✓ SeatMapLegSwitcher.swift  -  data in, callbacks out, previewable on its own
-struct SeatMapLegSwitcher: View {
-    let segments: [SeatMapSegment]
-    let activeSegmentIndex: Int
+// ✓ CategoryTabBar.swift  -  data in, callbacks out, previewable on its own
+struct CategoryTabBar: View {
+    let categories: [CatalogCategory]
+    let activeCategoryIndex: Int
     let onSelect: (Int) -> Void
     var body: some View { ... }
 }
 
 #Preview {
-    SeatMapLegSwitcher(segments: [.gidis, .donus], activeSegmentIndex: 0, onSelect: { _ in })
+    CategoryTabBar(categories: [.featured, .sale], activeCategoryIndex: 0, onSelect: { _ in })
 }
 
 // ✓ the scene keeps the composition  -  which component shows, in what order
 @ViewBuilder
 var content: some View {
-    if viewModel.loadError { errorRetryView } else { SeatMapLegSwitcher(...) }
+    if viewModel.loadError { errorRetryView } else { CategoryTabBar(...) }
 }
 ```
 **Why:** the canvas is the fastest way to check a visual piece, and it only works when the piece
@@ -298,22 +298,22 @@ it never gets looked at until the whole flow is run on a device.
 // ✗ a response model nested inside another  -  invisible to a filename search,
 //   and moving it later renames every reference
 struct OrderResponseModel {
-    struct PassengerModel { ... }
+    struct OrderItemModel { ... }
 }
 ```
 ```swift
 // ✓ data types are top level, one per file
 struct OrderResponseModel { let items: [OrderItemModel] }   // OrderResponseModel.swift
-struct PassengerModel { ... }                                      // PassengerModel.swift
+struct OrderItemModel { ... }                                     // OrderItemModel.swift
 
 // ✓ still fine  -  an owned detail with exactly one owner
-@Observable final class SeatMapViewModel {
+@Observable final class CatalogViewModel {
     enum ViewState { case loading, loaded, failed }
 }
 
 // ✓ also fine  -  a pure constants namespace; the nesting IS the grouping
 enum AppConstant {
-    enum Phone { static let defaultDialCode = "+90" }
+    enum Phone { static let defaultDialCode = "+1" }
     enum DeepLink { static let scheme = "myapp" }
 }
 ```
@@ -328,17 +328,17 @@ grouping and buys no discoverability.
 // ✗ transport verbs invented by the client  -  the name says what the code does
 //   (which the signature already says), not which service will fire
 func fetchOpenStatus(_ request: CheckOpenStatusRequestModel) async -> Result
-func loadPassengers(...) async -> Result
+func loadOrderItems(...) async -> Result
 ```
 ```swift
 // ✓ `send` + the endpoint path, segments in the backend's own order
 func sendCheckOpenStatus(_ request: CheckOpenStatusRequestModel) async -> Result  // check-open-status
 func sendOrderItemsSave(...) async -> Result                                      // order/items/save
-func sendSeatExtend() async -> Result                                             // seat/extend
+func sendSessionExtend() async -> Result                                          // session/extend
 
 // ✗ the generated client's method name is not the service name: `get` is the generator's
 //   HTTP-verb prefix and it reorders the path the backend chose
-func sendGetSeatMapPageInfo() async -> Result   // seat/map-page-info -> sendSeatMapPageInfo
+func sendGetCatalogPageInfo() async -> Result   // catalog/page-info -> sendCatalogPageInfo
 
 // ✓ variants over one service: the single caller is named, the variants sit above it
 func sendGetCountryList() async throws -> CountryLookupResponse   // private, the one call
@@ -365,7 +365,7 @@ struct SummaryMapper: Sendable {
     func map(dto: SummaryDto) -> SummaryData {
         SummaryData(
             sessionTimeout: dto.sessionTimeout.map { TimeInterval($0) / 1000.0 },
-            variant: dto.info?.status == .error ? .flightError : .standard,
+            variant: dto.info?.status == .error ? .orderError : .standard,
             otpTimeout: dto.timeout ?? 180
         )
     }
@@ -378,8 +378,8 @@ SummaryData(sessionTimeoutMs: dto.sessionTimeout, isFailure: dto.info?.status ==
 
 // ✓ the view model decides, in its own business-rules section
 var variant: SummaryVariant {
-    if data.isFailure { return anyApisRedirect ? .apisError : .flightError }
-    return data.isMultiSegment ? .oneStop : .standard
+    if data.isFailure { return anyPaymentRedirect ? .paymentError : .orderError }
+    return data.isMultiShipment ? .splitShipment : .standard
 }
 ```
 **Why:** the mapper is the one type with no screen context. A rule buried in it is invisible
@@ -398,12 +398,12 @@ every call site that reads it.
 
 ```swift
 // ✗ the parameter list is a request model nobody wrote
-func savePassengers(pnr: String, surname: String, passengers: [Passenger],
+func saveOrderItems(orderNumber: String, email: String, items: [CartItem],
                     contact: ContactInfo?, acceptsTerms: Bool) async throws -> Bool
 ```
 ```swift
 // ✓
-public func savePassengers(
+public func saveOrderItems(
     _ request: SaveOrderItemsRequestModel
 ) async -> OrderServiceResult<SaveOrderItemsResponseModel> {
 ```
@@ -420,8 +420,8 @@ func checkAccess(identifier: String) async throws -> AccessResponse
 ```swift
 // ✓ one type enumerating every outcome the caller must handle
 enum AccessOutcome: Equatable, Sendable {
-    case dashboard(pnr: String?)                 // a success case may name a DESTINATION
-    case ticketEntrance(pnr: String?)
+    case dashboard(orderNumber: String?)         // a success case may name a DESTINATION
+    case orderEntrance(orderNumber: String?)
     case serviceError(referenceCode: String?, message: String?)
     case offline
     case timeout
@@ -451,17 +451,17 @@ shape.
 ```swift
 // ✗ four properties; `isLoading` with data present and an error set is a state nothing rejects
 var isLoading = false
-var reservation: Reservation?
+var order: Order?
 var errorMessage: String?
 var isOffline = false
 ```
 ```swift
 // ✓ the payload hangs off the case, and the enum answers questions so the view never destructures
 struct LoadedContent: Hashable {
-    let reservation: Reservation
-    /// `nil` when the passenger request failed but the reservation loaded  -  the screen still
-    /// renders its flights, the passenger area is simply not drawn.
-    let passengerArea: PassengerArea?
+    let order: Order
+    /// `nil` when the recommendations request failed but the order loaded  -  the screen still
+    /// renders its items, the recommendation area is simply not drawn.
+    let recommendations: RecommendationArea?
 }
 
 enum ScreenState: Hashable {

package/pipeline/skills/shared/external/ios-coding-standard/references/lint-local.sh

@@ -91,7 +91,7 @@ if [ -f "$INVENTORY" ]; then
 fi
 
 # SENSITIVE / TRANSIENT: alternations of the module's own symbol names.
-: "${SENSITIVE:=token|password|passcode|secret|credential|passport|nationalId|identityNumber|pnr|reservationCode|ticketNumber|membershipNumber|cardNumber|cvv|dateOfBirth}"
+: "${SENSITIVE:=token|password|passcode|secret|credential|passport|nationalId|identityNumber|orderNumber|reservationCode|ticketNumber|membershipNumber|cardNumber|cvv|dateOfBirth}"
 : "${TRANSIENT:=oneTimeCode|otp|verificationCode|draft}"
 
 # SIBLINGS: every other module that lives beside this one  -  the MOD-01 import guard.

package/pipeline/skills/shared/external/ios-coding-standard/references/rules.yml

@@ -198,10 +198,10 @@ sensitive_data_classes:
       at_rest: keychain-required
       loggable: never
     - id: booking-reference
-      covers: reservation code, ticket number, boarding pass payload, barcode data
+      covers: order number, reservation code, ticket number, confirmation barcode payload
       at_rest: keychain-or-protected
       loggable: never
-      note: individually low-value, but it authorises access to a passenger record
+      note: individually low-value, but it authorises access to a customer record
     - id: membership-identity
       covers: loyalty or programme membership number, tier, account identifier
       at_rest: keychain-or-protected
@@ -338,7 +338,7 @@ rules:
     rationale: testability
     check: >
       A `private var x: Bool/String/Int` in a scene that reads the view model and decides
-      something  -  "is the header shown", "which leg is active", "what does the CTA say"  -  is a
+      something  -  "is the header shown", "which tab is active", "what does the CTA say"  -  is a
       business rule in the view layer. It belongs on the view model, in its business-rules
       section, where a unit test can reach it. The scene reads `viewModel.x`.
       Not this rule: building a design-system `Configuration` value. Moving those to the view
@@ -653,8 +653,8 @@ rules:
       Form/validation rules are the classic silent duplication: each one is small enough to
       re-type in ten seconds, so every module does, and the copies then drift. Before adding one,
       grep the shared rule library AND every sibling module for the CONCEPT, not the name  -  the
-      same rule appears as `EmailFormatRule` / `EmailRule`, `TCKNRule` / `TCKNChecksumRule` /
-      `NationalIdRule`, `PnrRule` / `PnrOrETicketFormatRule` / `<Screen>PnrOrETicketFormatRule`.
+      same rule appears as `EmailFormatRule` / `EmailRule`, `NationalIdRule` / `NationalIdChecksumRule` /
+      `IdentityNumberRule`, `OrderNumberRule` / `OrderNumberOrEmailFormatRule` / `<Screen>OrderNumberOrEmailFormatRule`.
       Name-matching alone finds none of those.
 
       Placement follows STRUCT-05, with one addition: the error copy is NOT part of the rule.
@@ -745,10 +745,10 @@ rules:
       `send` + the endpoint path, segments in their own order, camel-cased, path parameters
       dropped: `check-open-status` → `sendCheckOpenStatus`, `order/items/save` →
       `sendOrderItemsSave`, `session/extend` → `sendSessionExtend`,
-      `lookup/{airlineAlliance}/airline` → `sendLookupAirline`.
+      `lookup/{brand}/product` → `sendLookupProduct`.
       The path is the name, not the generated client method. A generator prefixes GET
-      endpoints with `get` and appends parameter suffixes (`getSeatMapPageInfo`,
-      `getAirlineListByAirlineAlliance`)  -  both are artifacts of the generator, and `get`
+      endpoints with `get` and appends parameter suffixes (`getCatalogPageInfo`,
+      `getProductListByBrand`)  -  both are artifacts of the generator, and `get`
       also reorders the segments the backend chose. Copying the generated name silently
       renames the service; copying the path keeps one spelling on both sides of the wire.
       The HTTP verb is never part of the name: the endpoint already implies it, and `send`
@@ -803,7 +803,7 @@ rules:
         A past deadline meaning "no countdown" is a product decision, not a cast.
       - **Choosing a screen state.** Resolving a variant, an enum case, or an error message
         from a combination of flags. Carry the flags; decide in the view model.
-      - **A policy default.** `?? 180` seconds, `?? passengers.count`. A number nobody can
+      - **A policy default.** `?? 180` seconds, `?? items.count`. A number nobody can
         derive from the payload is policy and belongs next to the code that lives with it.
       - **Dropping or promoting records.** Filtering a code out of a list, or turning one code
         into a different field, encodes what that code MEANS. That meaning belongs on the
@@ -824,7 +824,7 @@ rules:
       review is that deleting the decision also deletes the data it was computed from: the mapper
       stored `isFailure: Bool` and dropped `info.status`, so no later layer can re-derive it.
       So: first make the entity CARRY the raw inputs the decision reads (`info: Info?`,
-      `hasPrevention: Bool`, `apisCompletions: [Bool]`), then express the decision as a computed
+      `hasPrevention: Bool`, `stepCompletions: [Bool]`), then express the decision as a computed
       property. Where that property lives:
       - **On the entity**, under a `// MARK: - Derived`  -  when more than one screen, or the
         screen AND its mocks, ask the same question. This is also what keeps the mock
@@ -1332,7 +1332,7 @@ rules:
       removes it from the store build, and "it is only referenced by the mock path" is not an
       answer.
       Distinguish by payload, never by name: a `Mock` that returns nothing is a null object with
-      the wrong name (rename it), and a `Noop` that returns three sample bookings is a double in
+      the wrong name (rename it), and a `Noop` that returns three sample orders is a double in
       the wrong target (move it).
       **The measurement:** per module, the count of double-named types under the production source
       root, split into carries-payload and returns-empty. The first number is the finding; the

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

@@ -21,7 +21,6 @@ date_added: '2026-02-27'
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 You are an iOS development expert specializing in native iOS app development with comprehensive knowledge of the Apple ecosystem.
 

package/pipeline/skills/shared/external/ios-module-structure/SKILL.md

@@ -52,10 +52,14 @@ becoming a hundred findings.
 
 ## Running it
 
+Paths are relative to this skill's own directory (the directory this SKILL.md lives in, wherever
+the skill is installed); set `SKILL_DIR` to it first.
+
 ```bash
-python3 "$HOME/.claude/skills/ios-module-structure/scripts/check_structure.py" \
-  --rules   "$HOME/.claude/skills/ios-module-structure/references/rules.yml" \
-  --overlay "$HOME/.claude/skills/ios-module-structure/modules/<Module>.yml" \
+SKILL_DIR="<directory containing this SKILL.md>"
+python3 "$SKILL_DIR/scripts/check_structure.py" \
+  --rules   "$SKILL_DIR/references/rules.yml" \
+  --overlay "$SKILL_DIR/modules/<Module>.yml" \
   --root    "<path/to/module>"
 ```