@mmerterden/multi-agent-pipeline 20.2.1 → 20.3.1

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

@@ -1,125 +1,65 @@
 ---
 name: hig-technologies
-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'
+description: "Apple HIG for system technologies: Sign in with Apple, passkeys, Apple Pay, Wallet, Siri and App Intents, HealthKit, HomeKit, iCloud, Maps, SharePlay, CarPlay. Use when an app adopts an Apple technology."
+metadata:
+  risk: safe
+  source: multi-agent-pipeline
+  date_added: "2026-09-25"
 ---
 
-# Apple HIG: Technologies
-
-Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.
-
-## Key Principles
-
-### General
-
-1. **Apple technologies extend app capabilities through system integration.** Each technology has established user-facing patterns; deviating creates confusion and erodes trust.
-
-2. **Privacy and user control are paramount.** Especially for health, payment, and identity technologies. Request only needed data, explain why, respect choices.
-
-### Siri and Voice
-
-3. **Natural, predictable, recoverable.** Clear conversational intent phrases that complete quickly and confirm results. Support App Shortcuts for proactive suggestions. Handle errors with clear fallbacks.
-
-### Payments and Commerce
-
-4. **Transparent and frictionless.** Standard Apple Pay button styles. Never ask for card details when Apple Pay is available. Clearly describe what the user is buying, the price, and whether it's one-time or subscription.
-
-### Health and Fitness
-
-5. **Health data is deeply personal.** Explain the health benefit before requesting access. CareKit tasks should be encouraging. ResearchKit consent flows must be thorough, readable, and respect autonomy.
-
-### Smart Home
-
-6. **Simple and reliable.** Immediate response when controlling devices. Clear device state. Graceful handling of connectivity issues.
-
-### Augmented Reality
-
-7. **Genuine value, not gimmicks.** Use AR when spatial context improves understanding. Guide setup (surface, lighting, space). Provide clear exit back to standard interaction.
-
-### Machine Learning and Generative AI
-
-8. **Enhance without surprising.** Smart suggestions, image recognition, text prediction. Clearly attribute AI-generated content. Controls to edit, regenerate, or dismiss. Let users correct mistakes.
-
-### Identity and Authentication
-
-9. **Sign in with Apple as top option.** Standard button styles. Respect email hiding preference. ID Verifier: guided flows, don't store sensitive data beyond what verification requires.
-
-### Cloud and Data
-
-10. **Invisible and reliable sync.** Data appears on all devices without manual intervention. Handle conflicts gracefully. Never lose data.
-
-### Shared Experiences
-
-11. **Real-time participation.** SharePlay: support multiple participants, show presence, handle latency. AirPlay: appropriate Now Playing metadata.
-
-### Automotive
-
-12. **Driver safety first.** Minimize interaction complexity, large touch targets, no distracting content. Only permitted app types: audio, messaging, EV charging, navigation, parking, quick food ordering.
-
-### Accessibility
-
-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.
-
-## 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
-
-1. **Implementation checklist** -- step-by-step requirements per Apple's guidelines.
-2. **Required vs optional features** for approval.
-3. **Privacy and permission requirements** -- data access, usage descriptions.
-4. **User-facing flow** from permission prompt through task completion.
-5. **Testing guidance** -- key scenarios including edge cases.
-
-## Questions to Ask
-
-1. Which Apple technology?
-2. Core use case?
-3. Which platforms?
-4. API requirements and entitlements reviewed?
-5. What data or permissions needed?
-
-## Related Skills
-
-- **hig-inputs** -- Input methods interacting with technologies (voice for Siri, Pencil for AR, gestures for Maps)
-- **hig-components-system** -- Widgets, complications, Live Activities surfacing technology data
-- **hig-components-status** -- Progress indicators for technology operations (sync, payment, AR loading)
-
----
-
-*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*
-
-## When to Use
-This skill is applicable to execute the workflow or actions described in the overview.
+# HIG Technologies
+
+When an app uses an Apple technology, part of its interface is borrowed: a
+branded button, a system sheet, a Siri response, a pass in Wallet, a widget on
+the Home Screen. People already know how those behave. The job is to fit the
+borrowed part in cleanly, follow its brand rules, and keep your own screens
+consistent with it.
+
+## Three rules that apply to every technology
+
+1. **Use the system component.** Apple provides the button, sheet or view for
+   most technologies. Rebuilding it breaks trust and often breaks review rules.
+2. **Follow the brand guidance exactly.** Button titles, marks and colors are
+   specified; do not restyle, recolor or rename them.
+3. **Explain the value before the permission.** A short sentence of context
+   before a system prompt converts better than a surprise dialog.
+
+## Details on demand
+
+Load `references/technologies.md` for the rules for identity, payments, Wallet, App Intents, widgets, Health, Home, iCloud, Maps, SharePlay, CarPlay, AR and Apple Intelligence.
+
+## Review output
+
+```
+[Apple Pay] Checkout shows a custom black button titled "Apple Pay".
+Fix: replace with PayWithApplePayButton(.checkout) and hide it when
+the device cannot make payments.
+```
+
+## Related skills
+
+- `authentication`, `storekit`, `passkit-wallet`, `app-intents`, `widgetkit`,
+  `live-activities`, `healthkit`, `homekit-matter`, `mapkit-location`,
+  `shareplay-activities`, `realitykit-ar`, `apple-on-device-ai` for
+  implementation detail.
+- `hig-patterns` for account and permission flows.
+
+## References
+
+- https://developer.apple.com/design/human-interface-guidelines/technologies
+- https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple
+- https://developer.apple.com/design/human-interface-guidelines/apple-pay
+- https://developer.apple.com/design/human-interface-guidelines/in-app-purchase
+- https://developer.apple.com/design/human-interface-guidelines/wallet
+- https://developer.apple.com/design/human-interface-guidelines/siri
+- https://developer.apple.com/design/human-interface-guidelines/app-shortcuts
+- https://developer.apple.com/design/human-interface-guidelines/widgets
+- https://developer.apple.com/design/human-interface-guidelines/live-activities
+- https://developer.apple.com/design/human-interface-guidelines/healthkit
+- https://developer.apple.com/design/human-interface-guidelines/homekit
+- https://developer.apple.com/design/human-interface-guidelines/icloud
+- https://developer.apple.com/design/human-interface-guidelines/maps
+- https://developer.apple.com/design/human-interface-guidelines/shareplay
+- https://developer.apple.com/design/human-interface-guidelines/carplay
+- https://developer.apple.com/design/human-interface-guidelines/augmented-reality
+- https://developer.apple.com/design/human-interface-guidelines/generative-ai

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

@@ -0,0 +1,108 @@
+# Apple technologies in detail
+
+Companion to `../SKILL.md` for the `hig-technologies` skill.
+
+## Identity: Sign in with Apple and passkeys
+
+- Use `SignInWithAppleButton` with one of the permitted styles (black, white,
+  white outline) and a permitted label. Size it like the other sign-in options
+  and place it at least as prominently.
+- Request only the scopes you need; accept the relay email address.
+- Offer passkeys as the primary credential when you run your own accounts, and
+  support AutoFill for existing passwords.
+- Provide account deletion inside the app.
+
+## Payments: Apple Pay and in-app purchase
+
+- Apple Pay: use `PayWithApplePayButton` in SwiftUI, show it where checkout
+  begins, and include it as an option wherever you show other payment methods.
+  Display a clear order summary before the sheet appears.
+- Do not show an Apple Pay button when the device cannot pay; check
+  availability first.
+- In-app purchase: digital goods and subscriptions use StoreKit. `StoreView`,
+  `ProductView` and `SubscriptionStoreView` give compliant merchandising with
+  little code.
+- State price, period, trial terms and renewal plainly before purchase; make
+  restoring purchases and managing subscriptions easy to find.
+
+## Wallet
+
+- Passes (loyalty cards, tickets, coupons, store cards) are added with
+  `AddPassToWalletButton`. Keep the pass front minimal: the one number or code
+  people need at the counter.
+- Update passes when their information changes instead of issuing new ones.
+
+## Siri, Shortcuts, Spotlight and App Intents
+
+- Model the app's key actions and content as App Intents and entities; the same
+  definitions feed Siri, Shortcuts, Spotlight, widgets, controls and the Action
+  button.
+- Provide `AppShortcutsProvider` phrases that sound natural when spoken, such as
+  "Reorder my last purchase in AppName".
+- Keep responses short and useful without the screen; return a snippet view
+  when visual confirmation helps.
+- Confirm before intents that spend money or delete data.
+
+## Widgets, controls and Live Activities
+
+- Widgets show glanceable, timely content and deep link to the right place.
+  Support the families that fit the content, and accented and clear rendering
+  modes on iOS 18 and later; test tinted and glass appearances on iOS 26.
+- Controls in Control Center and on the Lock Screen perform one action or toggle
+  one state.
+- Live Activities track a single event with a clear end, such as an order out
+  for delivery. Keep compact and minimal Dynamic Island presentations
+  legible at a glance; end the activity promptly when the event finishes.
+
+## Health and fitness
+
+- Ask for HealthKit access only for the data types the feature uses, when the
+  feature is first used, and explain why.
+- Never use health data for advertising; be explicit about what leaves the
+  device.
+- Use Apple's terminology and units, respecting the person's locale settings.
+
+## Home
+
+- HomeKit and Matter accessories should use their system names and room
+  assignments. Let the Home app remain the source of truth for setup where
+  possible.
+
+## iCloud
+
+- Sync should be invisible: the same notes appear on every device without an
+  explicit sync button. Handle offline edits and conflicts gracefully.
+- Respect the person's choice to turn iCloud off for the app.
+
+## Maps and location
+
+- Use MapKit's `Map` with standard annotations and controls
+  (`MapUserLocationButton`, `MapCompass`) so it behaves like Maps.
+- Request "When In Use" location unless background tracking is essential, and
+  show the benefit before the prompt.
+
+## SharePlay
+
+- Offer SharePlay where a shared experience is natural, such as reviewing a
+  shopping list together. Use the system share and session UI; keep all
+  participants in sync and make leaving easy.
+
+## CarPlay
+
+- CarPlay apps use templates provided by the framework; there is no free-form
+  UI. Keep interactions few and glanceable, and never require reading long text
+  while driving.
+
+## Augmented reality
+
+- Coach people into a good session (surface detection, lighting) with the
+  system coaching view. Place content on real surfaces at believable scale and
+  give a way out of the AR view.
+
+## Apple Intelligence and generative features
+
+- Use system features (Writing Tools, Image Playground, Genmoji) through their
+  standard entry points; standard text views get Writing Tools automatically.
+- For custom on-device generation with the Foundation Models framework, make it
+  clear what is generated, let people edit or discard output, and handle
+  unavailability when the device or region does not support the model.

package/pipeline/skills/shared/external/homekit-matter/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: homekit-matter
 description: "Control smart-home accessories and commission Matter devices using HomeKit and MatterSupport. Use when managing homes/rooms/accessories, creating action sets or triggers, reading accessory characteristics, onboarding Matter devices, or building a third-party smart-home ecosystem app."
+metadata:
+  source: "dpearson2699/swift-ios-skills (PolyForm Perimeter 1.0.0)"
 ---
 
 # HomeKit

package/pipeline/skills/shared/external/homekit-matter/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "homekit",
+  "skill_name": "homekit-matter",
   "evals": [
     {
       "id": 0,

package/pipeline/skills/shared/external/html-semantic/SKILL.md

@@ -1,8 +1,9 @@
 ---
 name: html-semantic
 description: "Semantic HTML5: elements, forms with validation and accessibility, SEO best practices, structured data, Open Graph, Twitter Cards. Use when writing or reviewing markup, forms or document structure for semantics, accessibility and SEO."
-tags: [html, semantic, seo, forms, open-graph, structured-data, frontend]
-version: "2025.1"
+metadata:
+  tags: [html, semantic, seo, forms, open-graph, structured-data, frontend]
+  version: "2025.1"
 ---
 
 # Semantic HTML5

package/pipeline/skills/shared/external/humanizer/SKILL.md

@@ -1,11 +1,12 @@
 ---
 name: humanizer
-version: 1.2.0
 description: |
   Remove AI-generated writing patterns from text. Makes output sound natural
   and human-written. Detects inflated language, filler phrases, AI vocabulary,
   mechanical structure, and sycophantic tone. Use when editing text, writing
   documentation, commit messages, PR descriptions, or any user-facing content.
+metadata:
+  version: 1.2.0
 ---
 
 # Humanizer

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

@@ -1,6 +1,8 @@
 ---
 name: ios-accessibility
 description: "Implements, reviews, or improves accessibility in iOS/macOS apps with SwiftUI, UIKit, and AppKit. Use when adding VoiceOver, Voice Control, Switch Control, or Full Keyboard Access support; when working with accessibility labels, hints, values, traits, accessibilityInputLabels, NSAccessibility, grouping, reading order, accessibility focus restoration with @AccessibilityFocusState, Dynamic Type, @ScaledMetric, custom rotors, accessibility actions, XCTest accessibility checks, App Store Accessibility Nutrition Labels, App Store Connect accessibility answers, a11y compliance audits, or system accessibility preferences."
+metadata:
+  source: "dpearson2699/swift-ios-skills (PolyForm Perimeter 1.0.0)"
 ---
 
 # iOS/macOS Accessibility - SwiftUI, UIKit, and AppKit

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

@@ -2,7 +2,8 @@
 name: ios-coding-standard
 description: "The iOS coding-standard rule registry: 99 stable-ID rules across readability, security, service layer, business rules, concurrency, testing, module boundaries, naming and visibility, each with a severity and enforcement kind. Use when writing or reviewing Swift and you need the project rule rather than an opinion, or on a persistence, logging or business-rule-placement question."
 user-invocable: true
-standards-registry: references/rules.yml
+metadata:
+  standards-registry: references/rules.yml
 ---
 
 # iOS coding standard

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

@@ -8,6 +8,18 @@ win where they differ  -  this is the floor, not the ceiling.
 Five principles, in the order they break things: **security · testability · readability ·
 flexibility · consistency.**
 
+## Contents
+
+- [0. The ten lines](#0-the-ten-lines)
+- [1. Security](#1-security)
+- [2. Testability](#2-testability)
+- [3. Readability](#3-readability)
+- [4. Flexibility](#4-flexibility)
+- [5. Concurrency](#5-concurrency)
+- [6. Accessibility](#6-accessibility)
+- [7. Performance](#7-performance-----the-four-that-are-also-readability)
+- [8. Exceptions](#8-exceptions)
+
 ---
 
 ## 0. The ten lines
@@ -31,8 +43,8 @@ flexibility · consistency.**
 ## 1. Security
 
 Work out which **data class** a value belongs to before you decide where it goes.
-`rules.yml → sensitive_data_classes` is the list: auth token, credential, government ID, travel
-document, booking reference, membership identity, payment instrument, personal contact,
+`rules.yml → sensitive_data_classes` is the list: auth token, credential, government ID, identity
+document, order reference, membership identity, payment instrument, personal contact,
 biometric/health, precise location. The class decides the storage, not convenience.
 
 ### Storage `[SEC-01]`  -  ask "does it persist?" before "where does it go?"

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

@@ -193,11 +193,11 @@ sensitive_data_classes:
       covers: national identity number, tax number, driving licence number
       at_rest: keychain-required
       loggable: never
-    - id: travel-document
+    - id: identity-document
       covers: passport number and expiry, visa data, residence permit
       at_rest: keychain-required
       loggable: never
-    - id: booking-reference
+    - id: order-reference
       covers: order number, reservation code, ticket number, confirmation barcode payload
       at_rest: keychain-or-protected
       loggable: never

package/pipeline/skills/shared/external/ios-debugger-agent/SKILL.md

@@ -1,9 +1,10 @@
 ---
 name: ios-debugger-agent
 description: "Debug the current iOS project on a booted simulator with XcodeBuildMCP. Use when an iOS bug has to be reproduced and diagnosed on a booted simulator."
-risk: safe
-source: "Dimillian/Skills (MIT)"
-date_added: "2026-03-25"
+metadata:
+  risk: safe
+  source: "Dimillian/Skills (MIT)"
+  date_added: "2026-03-25"
 ---
 
 # iOS Debugger Agent

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

@@ -1,6 +1,8 @@
 ---
 name: ios-localization
 description: "Implement, review, or improve localization and internationalization in iOS/macOS apps  -  String Catalogs (.xcstrings), generated localizable symbols, stable key naming, LocalizedStringKey, LocalizedStringResource, pluralization, FormatStyle for numbers/dates/measurements, right-to-left layout, Dynamic Type, and locale-aware formatting. Use when adding multi-language support, setting up String Catalogs, enabling generated symbols for compile-time-safe localization keys, handling plural forms, formatting dates/numbers/currencies for different locales, testing localizations, or making UI work correctly in RTL languages like Arabic and Hebrew."
+metadata:
+  source: "dpearson2699/swift-ios-skills (PolyForm Perimeter 1.0.0)"
 ---
 
 # iOS Localization & Internationalization
@@ -61,14 +63,14 @@ For generated-symbol or migration answers, start by stating: "String Catalogs ar
 **Workflow:** Add a key manually via the (+) button in the String Catalog editor  -  manual keys have the **Generate Swift Symbol** checkbox enabled by default. Auto-extracted keys can also opt in via Refactor > Convert Strings to Symbols. Use stable manual keys for generated-symbol strings. Avoid source-copy-derived keys for API-facing strings because wording edits can rename generated identifiers and churn call sites.
 
 ```swift
-// Generated from key "room_available" in Localizable.xcstrings
-Text(.roomAvailable)
+// Generated from key "item_available" in Localizable.xcstrings
+Text(.itemAvailable)
 
-// Parameterized key "landmarks_count" with %1$(count)lld
-Text(.landmarksCount(count: 42))
+// Parameterized key "products_count" with %1$(count)lld
+Text(.productsCount(count: 42))
 
-// Non-default table "Booking.xcstrings"
-Text(.Booking.confirmBookingCta)
+// Non-default table "Checkout.xcstrings"
+Text(.Checkout.confirmOrderCta)
 ```
 
 Xcode derives symbol names by camelCasing the key: `settings.notifications.toggle` → `.settingsNotificationsToggle`. You can convert existing extracted strings to symbols via Refactor > Convert Strings to Symbols (reversible).

package/pipeline/skills/shared/external/ios-localization/evals/evals.json

@@ -4,13 +4,13 @@
     {
       "id": 0,
       "name": "generated-symbols-plurals",
-      "prompt": "I am updating an iOS 26 SwiftUI booking app for localization. We have a new Localizable.xcstrings file, a manually managed key named room_available whose English value is \"Book this room\", and a parameterized key named landmarks_count for \"42 landmarks\". Give me a concise migration plan and Swift snippets that use Xcode generated localizable symbols, plural-friendly placeholders, and modern string APIs. Also say what to do with old NSLocalizedString calls.",
+      "prompt": "I am updating an iOS 26 SwiftUI shop app for localization. We have a new Localizable.xcstrings file, a manually managed key named item_available whose English value is \"Add this item\", and a parameterized key named products_count for \"42 products\". Give me a concise migration plan and Swift snippets that use Xcode generated localizable symbols, plural-friendly placeholders, and modern string APIs. Also say what to do with old NSLocalizedString calls.",
       "expected_output": "A concise migration plan that uses String Catalogs, generated symbols, correct positional named placeholders, modern String(localized:) / LocalizedStringResource guidance, plural variants, and legacy NSLocalizedString migration notes.",
       "files": [],
       "expectations": [
         "Frames String Catalogs as the Xcode 15+ recommended workflow and does not claim they require iOS 17.",
         "Mentions enabling Generate String Catalog Symbols and using stable manually managed keys.",
-        "Uses generated symbol examples such as Text(.roomAvailable) and Text(.landmarksCount(count: 42)).",
+        "Uses generated symbol examples such as Text(.itemAvailable) and Text(.productsCount(count: 42)).",
         "Uses a positional named placeholder such as %1$(count)lld for the parameterized generated symbol.",
         "Distinguishes String(localized:) for resolved strings from LocalizedStringResource for deferred or system-framework resolution.",
         "Treats NSLocalizedString as legacy for new Swift code while acknowledging literal keys can still be exported or migrated."

package/pipeline/skills/shared/external/ios-localization/references/string-catalogs.md

@@ -335,14 +335,14 @@ The `.xcstrings` file is Xcode-managed JSON. Understanding the observed structur
         }
       }
     },
-    "room_available": {
-      "comment": "Button label on room search results",
+    "item_available": {
+      "comment": "Button label on product search results",
       "extractionState": "manual",
       "localizations": {
         "en": {
           "stringUnit": {
             "state": "translated",
-            "value": "Book this room"
+            "value": "Add this item"
           }
         }
       }
@@ -373,7 +373,7 @@ The `.xcstrings` file is Xcode-managed JSON. Understanding the observed structur
 }
 ```
 
-Note the `"room_available"` key above: it uses `"extractionState": "manual"` and a stable symbol-style key with the English text in `"value"`, not in the key itself. Use stable manual keys for generated-symbol strings. Avoid source-copy-derived keys for API-facing strings because wording edits can rename generated identifiers and churn call sites.
+Note the `"item_available"` key above: it uses `"extractionState": "manual"` and a stable symbol-style key with the English text in `"value"`, not in the key itself. Use stable manual keys for generated-symbol strings. Avoid source-copy-derived keys for API-facing strings because wording edits can rename generated identifiers and churn call sites.
 
 ### Translation states
 - `"new"` -- Xcode extracted the key but no translation exists
@@ -410,7 +410,7 @@ Xcode camelCases the key name, lowercasing the first segment:
 
 | Catalog key | Generated symbol |
 |-------------|-----------------|
-| `room_available` | `.roomAvailable` |
+| `item_available` | `.itemAvailable` |
 | `settings.notifications.toggle` | `.settingsNotificationsToggle` |
 | `TITLE` | `.title` |
 
@@ -418,7 +418,7 @@ Keys with format specifiers become functions. Use positional named placeholders
 
 | Catalog key | Format | Generated symbol |
 |-------------|--------|-----------------|
-| `landmarks_count` | `%1$(count)lld` | `.landmarksCount(count: Int)` |
+| `products_count` | `%1$(count)lld` | `.productsCount(count: Int)` |
 | `greeting` | `%@` | `.greeting(_ param1: String)` |
 
 You can rename parameters during refactoring for more descriptive signatures.
@@ -427,16 +427,16 @@ You can rename parameters during refactoring for more descriptive signatures.
 
 ```swift
 // Simple key  -  static property
-Text(.roomAvailable)
+Text(.itemAvailable)
 
 // Parameterized key  -  function
-Text(.landmarksCount(count: 42))
+Text(.productsCount(count: 42))
 
-// Non-default table (Booking.xcstrings)
-Text(.Booking.confirmBookingCta)
+// Non-default table (Checkout.xcstrings)
+Text(.Checkout.confirmOrderCta)
 
 // In non-SwiftUI code
-let title = String(localized: .roomAvailable)
+let title = String(localized: .itemAvailable)
 let attributed = AttributedString(localized: .greeting(userName))
 ```
 

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

@@ -2,7 +2,8 @@
 name: ios-module-structure
 description: "The ios-module-structure rule registry: stable-ID rules over where a declaration lives, what its file is called and what its folder must contain beside it, plus a checker that runs them against one module. Use when auditing or refactoring a module's tree, or when a review wants a rule ID rather than a preference about layout."
 user-invocable: true
-standards-registry: references/rules.yml
+metadata:
+  standards-registry: references/rules.yml
 ---
 
 # Module structure

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

@@ -1,6 +1,8 @@
 ---
 name: ios-networking
 description: "Build, review, or improve networking code in iOS/macOS apps using URLSession with async/await, structured concurrency, and modern Swift patterns. Use when working with REST APIs, downloading files, uploading data, WebSocket connections, pagination, retry logic, request middleware, caching, background transfers, or network reachability monitoring. Also use when handling HTTP requests, API clients, network error handling, or data fetching in Swift apps."
+metadata:
+  source: "dpearson2699/swift-ios-skills (PolyForm Perimeter 1.0.0)"
 ---
 
 # iOS Networking

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

@@ -1,6 +1,8 @@
 ---
 name: ios-simulator
 description: "Manages iOS Simulator devices and tests app behaviour with xcrun simctl: device lifecycle, app install and launch, push notification and location simulation, privacy permission grants, deep links via openurl, status bar overrides, screenshot and video capture, os_log streaming, app container paths, and targetEnvironment(simulator) checks. Use when managing simulator devices, testing push without APNs, simulating GPS, resetting permissions, capturing screens from the command line, streaming device logs, or debugging simulator boot and CoreSimulator failures."
+metadata:
+  source: "dpearson2699/swift-ios-skills (PolyForm Perimeter 1.0.0)"
 ---
 
 # iOS Simulator