npm - @mmerterden/multi-agent-pipeline - Versions diffs - 8.6.1 → 10.0.6 - Mend

@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (928) hide show

package/pipeline/skills/shared/external/homekit-matter/references/matter-commissioning.md CHANGED Viewed

@@ -1,6 +1,6 @@
 # HomeKit + Matter Extended Patterns
-Overflow reference for the `homekit-matter` skill. Contains advanced patterns
+Overflow reference for the `homekit` skill. Contains advanced patterns
 that exceed the main skill file's scope.
 ## Contents
@@ -13,7 +13,7 @@ that exceed the main skill file's scope.
 ## SwiftUI HomeKit Integration
-### HomeKit Store with @Observable
+### HomeKit Store with `@Observable`
 ```swift
 import HomeKit
@@ -194,7 +194,7 @@ struct LightControlView: View {
     }
     var body: some View {
-        VStack(spacing: 20) {
+        VStack {
             Toggle("Power", isOn: $isOn)
                 .onChange(of: isOn) { _, newValue in
                     powerCharacteristic?.writeValue(newValue) { _ in }
@@ -366,7 +366,8 @@ import MatterSupport
 final class MyMatterHandler: MatterAddDeviceExtensionRequestHandler {
     override func validateDeviceCredential(
-        _ deviceCredential: DeviceCredential
+        _ deviceCredential:
+            MatterAddDeviceExtensionRequestHandler.DeviceCredential
     ) async throws {
         // Validate the Device Attestation Certificate (DAC) against
         // your Product Attestation Authority (PAA) root certificates.
@@ -415,15 +416,19 @@ final class MyMatterHandler: MatterAddDeviceExtensionRequestHandler {
     }
     override func selectWiFiNetwork(
-        from networks: [WiFiScanResult]
-    ) async throws -> WiFiNetworkAssociation {
+        from networks:
+            [MatterAddDeviceExtensionRequestHandler.WiFiScanResult]
+    ) async throws
+        -> MatterAddDeviceExtensionRequestHandler.WiFiNetworkAssociation {
         // Use the system default network or specify one
         return .defaultSystemNetwork
     }
     override func selectThreadNetwork(
-        from networks: [ThreadScanResult]
-    ) async throws -> ThreadNetworkAssociation {
+        from networks:
+            [MatterAddDeviceExtensionRequestHandler.ThreadScanResult]
+    ) async throws
+        -> MatterAddDeviceExtensionRequestHandler.ThreadNetworkAssociation {
         return .defaultSystemNetwork
     }
 }

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

@@ -1,4 +1,5 @@
 ---
+name: html-semantic
 description: "Semantic HTML5: elements, forms with validation and accessibility, SEO best practices, structured data, Open Graph, Twitter Cards"
 tags: [html, semantic, seo, forms, open-graph, structured-data, frontend]
 version: "2025.1"
@@ -19,7 +20,7 @@ improves accessibility, SEO, and maintainability. Style with CSS, not with HTML
 <head>
   <meta charset="UTF-8" />
   <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-  <title>Page Title — Site Name</title>
+  <title>Page Title  -  Site Name</title>
   <meta name="description" content="Concise description of the page (150-160 chars)" />
   <link rel="canonical" href="https://example.com/page" />
   <link rel="icon" href="/favicon.svg" type="image/svg+xml" />
@@ -62,7 +63,7 @@ improves accessibility, SEO, and maintainability. Style with CSS, not with HTML
         <p>More content...</p>
         <blockquote cite="https://source.com/quote">
           <p>A meaningful quote from a reference.</p>
-          <footer>— <cite>Author Name</cite></footer>
+          <footer> -  <cite>Author Name</cite></footer>
         </blockquote>
       </section>
@@ -167,7 +168,7 @@ improves accessibility, SEO, and maintainability. Style with CSS, not with HTML
   <div class="field">
     <label for="subject">Subject <span aria-hidden="true">*</span></label>
     <select id="subject" name="subject" required aria-required="true">
-      <option value="">— Choose a subject —</option>
+      <option value=""> -  Choose a subject  - </option>
       <option value="support">Technical Support</option>
       <option value="billing">Billing</option>
       <option value="other">Other</option>
@@ -205,7 +206,7 @@ improves accessibility, SEO, and maintainability. Style with CSS, not with HTML
 ```html
 <head>
   <!-- Essential meta -->
-  <title>Primary Keyword — Brand Name</title>
+  <title>Primary Keyword  -  Brand Name</title>
   <meta name="description" content="Compelling description with primary keywords (150-160 chars)" />
   <meta name="robots" content="index, follow" />
   <link rel="canonical" href="https://example.com/current-page" />

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

@@ -16,7 +16,7 @@ You are a writing editor. Your job is to rewrite text so it reads like a human w
 1. Scan for the patterns below
 2. Rewrite problematic sections
-3. Keep the meaning — change the delivery
+3. Keep the meaning  -  change the delivery
 4. Do a final check: "Does this still sound like AI?" If yes, fix it
 ## Patterns to Fix
@@ -57,7 +57,7 @@ seamless, robust, comprehensive, innovative
 | Pattern | Example | Fix |
 |---------|---------|-----|
-| Em dash overuse | "tools—not the old ones—yet this continues—" | Use commas or periods |
+| Em dash overuse | "tools - not the old ones - yet this continues - " | Use commas or periods |
 | Bold overuse | "**OKRs**, **KPIs**, **BMC**" | Remove unnecessary bold |
 | Inline-header lists | "**Performance:** Performance improved" | Convert to prose |
 | Emoji decoration | "🚀 Launch Phase: 💡 Key Insight:" | Remove emojis |
@@ -79,7 +79,7 @@ seamless, robust, comprehensive, innovative
 |--------|-------|
 | "In order to" | "To" |
 | "Due to the fact that" | "Because" |
-| "It is important to note that" | Remove — just state it |
+| "It is important to note that" | Remove  -  just state it |
 | "could potentially possibly" | "may" |
 | "At this point in time" | "Now" |
 | "The future looks bright" | Specific plans or remove |
@@ -88,7 +88,7 @@ seamless, robust, comprehensive, innovative
 | Pattern | Example | Fix |
 |---------|---------|-----|
-| Over-hyphenation | "cross-functional, data-driven, client-facing" everywhere | Humans are inconsistent with hyphens — drop some |
+| Over-hyphenation | "cross-functional, data-driven, client-facing" everywhere | Humans are inconsistent with hyphens  -  drop some |
 | Authority tropes | "At its core", "The real question is" | State the point directly |
 ## Voice Guidelines

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

@@ -1,11 +1,11 @@
 ---
 name: ios-accessibility
-description: "Implement, review, or improve accessibility in iOS/macOS apps with SwiftUI and UIKit. Use when adding VoiceOver support with accessibility labels, hints, values, and traits; when grouping or reordering accessibility elements; when managing focus with @AccessibilityFocusState; when supporting Dynamic Type with @ScaledMetric; when building custom rotors or accessibility actions; when auditing a11y compliance; or when adapting UI for assistive technologies and system accessibility preferences."
+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."
 ---
-# iOS Accessibility — SwiftUI and UIKit
+# iOS/macOS Accessibility - SwiftUI, UIKit, and AppKit
-Every user-facing view must be usable with VoiceOver, Switch Control, Voice Control, Full Keyboard Access, and other assistive technologies. This skill covers the patterns and APIs required to build accessible iOS apps.
+Every user-facing view must be usable with VoiceOver, Switch Control, Voice Control, Full Keyboard Access, and other assistive technologies. This skill covers SwiftUI, UIKit, and AppKit patterns required to build accessible iOS, iPadOS, and macOS apps.
 ## Contents
@@ -17,9 +17,14 @@ Every user-facing view must be usable with VoiceOver, Switch Control, Voice Cont
 - [Custom Rotors](#custom-rotors)
 - [System Accessibility Preferences](#system-accessibility-preferences)
 - [Decorative Content](#decorative-content)
+- [Voice Control](#voice-control)
+- [Switch Control](#switch-control)
+- [Full Keyboard Access](#full-keyboard-access)
 - [Assistive Access (iOS 18+)](#assistive-access-ios-18)
 - [UIKit Accessibility Patterns](#uikit-accessibility-patterns)
+- [AppKit Accessibility Patterns](#appkit-accessibility-patterns)
 - [Accessibility Custom Content](#accessibility-custom-content)
+- [App Store Accessibility Nutrition Labels](#app-store-accessibility-nutrition-labels)
 - [Testing Accessibility](#testing-accessibility)
 - [Common Mistakes](#common-mistakes)
 - [Review Checklist](#review-checklist)
@@ -30,13 +35,14 @@ Every user-facing view must be usable with VoiceOver, Switch Control, Voice Cont
 ## Core Principles
 1. Every interactive element MUST have an accessible label. If no visible text exists, add `.accessibilityLabel`.
-2. Every custom control MUST have correct traits via `.accessibilityAddTraits` (never direct assignment).
-3. Decorative images MUST be hidden from assistive technologies.
-4. Sheet and dialog dismissals MUST return VoiceOver focus to the trigger element.
-5. All tap targets MUST be at least 44x44 points.
-6. Dynamic Type MUST be supported everywhere (system fonts, `@ScaledMetric`, adaptive layouts).
-7. No information conveyed by color alone -- always provide text or icon alternatives.
-8. System accessibility preferences MUST be respected: Reduce Motion, Reduce Transparency, Bold Text, Increase Contrast.
+2. Every custom control MUST have correct traits via `.accessibilityAddTraits` (never direct assignment). For binary custom controls such as favorite/star buttons, prefer a real `Toggle`; otherwise expose toggle behavior with `.accessibilityAddTraits(.isToggle)` and a current state value without putting the control type in the label.
+3. Custom adjustable controls such as quantity steppers MUST expose adjustable behavior with `.accessibilityAdjustableAction`; UIKit custom adjustable controls also need the `.adjustable` trait.
+4. Decorative images MUST be hidden from assistive technologies.
+5. Sheet and dialog dismissals MUST return VoiceOver focus to the trigger element.
+6. All tap targets MUST be at least 44x44 points.
+7. Dynamic Type MUST be supported everywhere (system fonts, `@ScaledMetric`, adaptive layouts).
+8. No information conveyed by color alone -- always provide text or icon alternatives.
+9. System accessibility preferences MUST be respected: Reduce Motion, Reduce Transparency, Bold Text, Increase Contrast.
 ## How VoiceOver Reads Elements
@@ -48,13 +54,17 @@ Design your labels, values, and hints with this reading order in mind.
 ## SwiftUI Accessibility Modifiers
-See `references/a11y-patterns.md` for detailed SwiftUI modifier examples (labels, hints, traits, grouping, custom controls, adjustable actions, and custom actions).
+See [references/a11y-patterns.md](references/a11y-patterns.md) for detailed SwiftUI modifier examples (labels, hints, traits, grouping, custom controls, adjustable actions, and custom actions).
 ## Focus Management
 Focus management is where most apps fail. When a sheet, alert, or popover is dismissed, VoiceOver focus MUST return to the element that triggered it.
-### @AccessibilityFocusState (iOS 15+)
+This section is about accessibility focus for assistive technologies. For keyboard focus, directional focus, `focusSection()`, scene-focused values, and `UIFocusGuide`, use the `focus-engine` skill.
+When triaging broad focus bugs, still call out accessibility traversal separately: accessibility element order and grouping in the view hierarchy directly affect VoiceOver swipe order, Switch Control scan order, Voice Control overlay targeting, and Full Keyboard Access reachability review. Route keyboard-focus implementation to `focus-engine`, but keep this traversal impact in `ios-accessibility`.
+### `@AccessibilityFocusState` (iOS 15+)
 `@AccessibilityFocusState` is a property wrapper that reads and writes the current accessibility focus. It works with `Bool` for single-target focus or an optional `Hashable` enum for multi-target focus.
@@ -121,6 +131,8 @@ CustomDialog()
     .accessibilityAction(.escape) { dismiss() }
 ```
+Test dismissal as part of the modal contract: users must be able to dismiss the overlay with the relevant assistive-technology escape gesture or keyboard escape path, and focus should return to the trigger or next logical target.
 ### Accessibility Notifications (UIKit)
 When you need to announce changes or move focus imperatively in UIKit contexts:
@@ -138,11 +150,13 @@ UIAccessibility.post(notification: .screenChanged, argument: newScreenView)
 ## Dynamic Type
-See `references/a11y-patterns.md` for Dynamic Type and adaptive layout examples, including @ScaledMetric and minimum tap target patterns.
+Scale text with system text styles. Scale non-text dimensions too: icon sizes, spacing, control heights, and custom hit-region dimensions should use `@ScaledMetric(relativeTo:)` where they need to track text size.
+See [references/a11y-patterns.md](references/a11y-patterns.md) for Dynamic Type and adaptive layout examples, including `@ScaledMetric` and minimum tap target patterns.
 ## Custom Rotors
-Rotors let VoiceOver users quickly navigate to specific content types. Add custom rotors for content-heavy screens. See `references/a11y-patterns.md` for complete rotor examples.
+Rotors let VoiceOver users quickly navigate to specific content types. Add custom rotors for content-heavy screens. See [references/a11y-patterns.md](references/a11y-patterns.md) for complete rotor examples.
 ## System Accessibility Preferences
@@ -166,6 +180,8 @@ withAnimation(reduceMotion ? nil : .spring()) {
 content.transition(reduceMotion ? .opacity : .slide)
 ```
+Review every moving transition, including row deletion, quantity changes, sheet or checkout presentation, and modal dismissal. Under Reduce Motion, replace slide, bounce, parallax, spring, and large spatial transitions with opacity changes, instant state changes, or no animation.
 ### Reduce Transparency, Increase Contrast, Bold Text
 ```swift
@@ -196,6 +212,50 @@ Button(action: { }) {
 .accessibilityLabel("Settings")
 ```
+Treat an image as decorative only when it adds no information beyond adjacent accessible text. If it communicates a product variant, state, chart point, user-generated content, or another distinguishing detail, provide a meaningful description instead of hiding it.
+## Voice Control
+Voice Control relies on accessibility labels to generate spoken tap targets. If a label is missing or unspeakable, Voice Control cannot target the element.
+- Every interactive element MUST have a speakable accessibility label (no emoji-only, no symbol-only).
+- Labels must be unique within the visible screen  -  duplicate labels force users to disambiguate with overlay numbers.
+- Treat `accessibilityInputLabels` as pre-freeze accessibility work for long, awkward, localized, acronym-heavy, or commonly shortened spoken labels; do not defer it as polish. Voice Control and Full Keyboard Access use these. List alternatives in descending order of importance.
+- Apply `accessibilityInputLabels` broadly to any visible target whose primary label is hard to say, including repeated row actions, quantity controls, account/settings links, media controls, and localized labels with acronyms or product names.
+- Test with Voice Control enabled: say "Show Names" and "Show Numbers" to verify all interactive elements are targetable.
+- For Voice Control reviews, verify both overlays: "Show Names" confirms speakable labels, and "Show Numbers" confirms every visible interactive target can still be reached when names are missing, duplicated, or awkward.
+See [references/a11y-patterns.md](references/a11y-patterns.md) for `accessibilityInputLabels` examples and speakable label guidelines.
+## Switch Control
+Switch Control scans accessibility elements sequentially in reading order. Proper grouping and custom actions are critical for usability.
+- Group related content with `.accessibilityElement(children: .combine)` to reduce scan stops.
+- Every scan target should be meaningful and actionable. Decorative elements hidden from VoiceOver are also hidden from Switch Control.
+- Switch Control users cannot perform swipe-to-delete, long-press, or multi-finger gestures. Expose these interactions as `.accessibilityAction(named:)` custom actions instead  -  Switch Control presents them as a menu.
+- Custom controls with non-standard hit areas should ensure `accessibilityFrame` accurately reflects the tappable region (for point scanning mode).
+See [references/a11y-patterns.md](references/a11y-patterns.md) for custom action and grouping examples.
+## Full Keyboard Access
+Full Keyboard Access (iOS/iPadOS 13.4+) lets users navigate and operate an app with a hardware keyboard.
+This skill covers the accessibility review surface: whether all controls are reachable, clearly labeled, visibly focused, and operable without touch. If the bug is Tab traversal, skipped custom cards, `.focusable()`, `@FocusState`, `focusSection()`, directional movement, scene-focused values, tvOS focus behavior, or `UIFocusGuide`, route implementation to the `focus-engine` skill first. Keep only the accessibility finding here.
+- Every interactive element can be reached and activated with the keyboard.
+- Traversal order is logical and does not trap focus.
+- Focus indicators remain visible at all contrast and text-size settings.
+- Gesture-only behavior has a keyboard-operable alternative.
+- App shortcuts do not override system-defined shortcuts such as Cmd+C, Cmd+V, or Cmd+Tab.
+See [references/a11y-patterns.md](references/a11y-patterns.md) for Full Keyboard Access audit checks.
+## Traversal Order
+Explicitly assess how accessibility element order and grouping affect traversal outcomes: VoiceOver swipe order, Switch Control scan order, Voice Control overlay targeting, and Full Keyboard Access reachability review can all break when grouping/order differs from visual or task order. Missing labels, duplicate labels, excessive row children, hidden custom controls, or grouping that does not match the visual/task order can make traversal confusing across all of them. Keep implementation mechanics for keyboard or directional routing in `focus-engine`; keep the accessibility impact and ordering audit here.
 ## Assistive Access (iOS 18+)
 Assistive Access provides a simplified interface for users with cognitive disabilities. Apps should support this mode:
@@ -240,9 +300,40 @@ customButton.accessibilityTraits.remove(.staticText)
 overlayView.accessibilityViewIsModal = true
 ```
+## AppKit Accessibility Patterns
+AppKit accessibility uses `NSAccessibilityProtocol` and related role-specific protocols to describe accessible elements. Standard AppKit controls already provide much of this behavior; customize labels, values, roles, and actions only when the defaults are insufficient.
+- Prefer standard AppKit controls first  -  they already expose accessibility metadata and notifications.
+- For custom `NSView` subclasses, adopt the appropriate role-specific accessibility behavior and return the correct role, label, value, and actions.
+- Use `NSAccessibilityElement` for accessible items that are not backed by their own `NSView`.
+- Post `NSAccessibility` notifications when state changes need to be announced to assistive apps.
+```swift
+final class FavoriteToggleView: NSView {
+    var isFavorite = false {
+        didSet {
+            NSAccessibility.post(element: self, notification: .valueChanged)
+        }
+    }
+    override func isAccessibilityElement() -> Bool { true }
+    override func accessibilityRole() -> NSAccessibility.Role? { .button }
+    override func accessibilityLabel() -> String? { "Favorite" }
+    override func accessibilityValue() -> Any? { isFavorite ? "On" : "Off" }
+    override func accessibilityPerformPress() -> Bool {
+        isFavorite.toggle()
+        return true
+    }
+}
+```
+See [references/a11y-patterns.md](references/a11y-patterns.md) for AppKit examples including `NSAccessibilityElement` and announcement notifications.
 ## Accessibility Custom Content
-See `references/a11y-patterns.md` for UIKit accessibility patterns and custom content examples.
+See [references/a11y-patterns.md](references/a11y-patterns.md) for UIKit and AppKit accessibility patterns and custom content examples.
 ```swift
 ProductRow(product: product)
@@ -255,15 +346,70 @@ ProductRow(product: product)
     )
 ```
+## App Store Accessibility Nutrition Labels
+For App Store accessibility nutrition labels, product-page claims, or App Store Connect accessibility answers, read [references/nutrition-labels.md](references/nutrition-labels.md).
+Before recommending a claim, require evidence that users can complete all common tasks with that feature on the relevant device type. Use a structured common-task by accessibility-feature matrix, include media transcripts when captions for audio-only content are relevant, and explicitly warn that App Store accessibility answers must stay accurate and must not be treated as marketing claims.
 ## Testing Accessibility
+### Manual Testing
 - **Accessibility Inspector** (Xcode > Open Developer Tool): Audit views for missing labels, traits, and contrast issues. Run audits against the Simulator or connected device.
 - **VoiceOver testing**: Enable in Settings > Accessibility > VoiceOver. Navigate every screen with swipe gestures.
+- **Voice Control testing**: Enable in Settings > Accessibility > Voice Control. Say both "Show Names" and "Show Numbers"; names verify speakable labels, while numbers verify every visible interactive target is reachable even when names are duplicated, missing, or awkward.
+- **Full Keyboard Access testing**: Enable in Settings > Accessibility > Keyboards > Full Keyboard Access. Tab through every screen and verify all interactive elements receive focus.
+- **Switch Control testing**: Enable in Settings > Accessibility > Switch Control. Verify scan order is logical and custom actions appear for gesture-based interactions.
 - **Dynamic Type**: Test with all text sizes in Settings > Accessibility > Display & Text Size > Larger Text.
+### Automated Testing with XCTest
+Use `XCUIElement` accessibility attributes to write UI tests that verify accessibility properties:
+```swift
+func testProductRowAccessibility() throws {
+    let app = XCUIApplication()
+    app.launch()
+    let productCell = app.cells["product-organic-apples"]
+    XCTAssertTrue(productCell.exists)
+    XCTAssertTrue(productCell.isEnabled)
+    // Verify the label is set and meaningful
+    XCTAssertFalse(productCell.label.isEmpty)
+    // Verify a specific element has the expected label
+    let favoriteButton = productCell.buttons["Favorite"]
+    XCTAssertTrue(favoriteButton.exists)
+    XCTAssertTrue(favoriteButton.isEnabled)
+}
+```
+Key `XCUIElementAttributes` properties for accessibility verification: `label`, `identifier`, `value`, `isEnabled`, `hasFocus`, `isSelected`, `placeholderValue`, `title`.
+Test dismissal focus restoration:
+```swift
+func testSheetDismissReturnsFocus() throws {
+    let app = XCUIApplication()
+    app.launch()
+    let triggerButton = app.buttons["Open Settings"]
+    triggerButton.tap()
+    // Dismiss the sheet
+    let doneButton = app.buttons["Done"]
+    doneButton.tap()
+    // Verify focus returns to trigger (in accessibility-focused testing)
+    XCTAssertTrue(triggerButton.hasFocus)
+}
+```
 ## Common Mistakes
-1. **Direct trait assignment**: `.accessibilityTraits(.isButton)` overwrites all existing traits. Use `.accessibilityAddTraits(.isButton)`.
+1. **Direct trait assignment**: UIKit trait mutation or incorrect SwiftUI trait APIs can overwrite existing behavior. In SwiftUI, use `.accessibilityAddTraits(.isButton)`.
 2. **Missing focus restoration**: Dismissing sheets without returning VoiceOver focus to the trigger element.
 3. **Ungrouped list rows**: Multiple text elements per row create excessive swipe stops. Use `.accessibilityElement(children: .combine)`.
 4. **Redundant trait in labels**: `.accessibilityLabel("Settings button")` reads as "Settings button, button." Omit the type.
@@ -280,6 +426,7 @@ For every user-facing view, verify:
 - [ ] Every interactive element has an accessible label
 - [ ] Custom controls use correct traits via `.accessibilityAddTraits`
+- [ ] Adjustable custom controls expose adjustable behavior with `.accessibilityAdjustableAction` or UIKit `.adjustable`
 - [ ] Decorative images are hidden (`Image(decorative:)` or `.accessibilityHidden(true)`)
 - [ ] List rows group content with `.accessibilityElement(children: .combine)`
 - [ ] Sheets and dialogs return focus to the trigger on dismiss
@@ -287,6 +434,7 @@ For every user-facing view, verify:
 - [ ] All tap targets are at least 44x44 points
 - [ ] Dynamic Type supported (`@ScaledMetric`, system fonts, adaptive layouts)
 - [ ] Reduce Motion respected (no movement animations when enabled)
+- [ ] Row, checkout, sheet, and modal animations have Reduce Motion alternatives
 - [ ] Reduce Transparency respected (solid backgrounds when enabled)
 - [ ] Increase Contrast respected (stronger foreground colors)
 - [ ] No information conveyed by color alone
@@ -294,8 +442,16 @@ For every user-facing view, verify:
 - [ ] Icon-only buttons have labels
 - [ ] Heading traits set on section headers
 - [ ] Custom accessibility types and notification payloads are `Sendable` when passed across concurrency boundaries
+- [ ] Labels are speakable and unique for Voice Control (no emoji-only or duplicate labels on screen)
+- [ ] Voice Control testing covers both "Show Names" and "Show Numbers"
+- [ ] `accessibilityInputLabels` provided for elements with long or awkward primary labels
+- [ ] Gesture-based interactions (swipe-to-delete, long-press) have accessibility custom action equivalents for Switch Control
+- [ ] Full Keyboard Access reaches and activates every control without focus traps
+- [ ] Element order and grouping are checked for traversal impact across VoiceOver, Switch Control, Voice Control overlays, and Full Keyboard Access review
+- [ ] System keyboard shortcuts are not overridden
 ## References
-- Detailed patterns: `references/a11y-patterns.md`
+- [references/a11y-patterns.md](references/a11y-patterns.md)  -  SwiftUI and UIKit modifier examples, grouping, custom actions, rotors, Dynamic Type
+- [references/nutrition-labels.md](references/nutrition-labels.md)  -  App Store Accessibility Nutrition Labels: current categories with pass/fail criteria
+- [references/media-accessibility.md](references/media-accessibility.md)  -  Captions, audio descriptions, AVMediaCharacteristic, SDH

package/pipeline/skills/shared/external/ios-accessibility/evals/evals.json ADDED Viewed

@@ -0,0 +1,49 @@
+{
+  "skill_name": "ios-accessibility",
+  "evals": [
+    {
+      "id": 0,
+      "name": "assistive-technology-review",
+      "prompt": "Review this SwiftUI shopping cart screen for accessibility before implementation: each row has an icon, product name, price, stepper-like +/- icons built with tap gestures, a swipe-to-delete action, duplicate \"Edit\" buttons, a favorite heart-only button, a checkout sheet, and product photos. Product wants VoiceOver, Voice Control, Switch Control, Dynamic Type, and Reduce Motion support. What should we fix?",
+      "expected_output": "A practical accessibility review that covers labels, values, traits, grouping, gesture alternatives, Voice Control input labels, Switch Control custom actions, focus restoration, Dynamic Type, decorative/content images, and Reduce Motion.",
+      "files": [],
+      "assertions": [
+        "Requires meaningful accessibility labels, values, and traits for icon-only buttons and custom stepper controls without putting control types like \"button\" in the label.",
+        "Recommends grouping each cart row with `accessibilityElement(children: .combine)` or an equivalent pattern to reduce VoiceOver and Switch Control scan stops.",
+        "Provides `.accessibilityAction(named:)` custom actions for swipe-to-delete, favorite, quantity changes, or other gesture-only behavior so Switch Control and VoiceOver can operate them.",
+        "Mentions Voice Control testing with \"Show Names\" and/or \"Show Numbers\" and recommends unique, speakable labels plus `accessibilityInputLabels` for long or awkward names.",
+        "Requires returning accessibility focus to the checkout trigger after dismissing the sheet with `@AccessibilityFocusState` or an equivalent UIKit notification.",
+        "Covers Dynamic Type and Reduce Motion using system text styles, adaptive layout, `@ScaledMetric`, and `accessibilityReduceMotion` rather than fixed fonts or motion-only feedback."
+      ]
+    },
+    {
+      "id": 1,
+      "name": "nutrition-labels-current-categories",
+      "prompt": "We're preparing App Store Accessibility Nutrition Labels for a media-heavy iOS 26 app. The team wants to claim VoiceOver, Switch Control, Full Keyboard Access, Closed Captions / SDH, Audio Descriptions, Larger Text, Reduce Motion, and Increase Contrast. Audit this list against Apple's current label categories and tell us what evidence to collect before answering in App Store Connect.",
+      "expected_output": "A source-grounded label audit that corrects stale category names, routes non-label assistive technology work appropriately, and describes evidence needed for common-task claims.",
+      "files": [],
+      "assertions": [
+        "Lists the current App Store Accessibility Nutrition Label categories as VoiceOver, Voice Control, Larger Text, Dark Interface, Differentiate Without Color Alone, Sufficient Contrast, Reduced Motion, Captions, and Audio Descriptions.",
+        "States that Switch Control and Full Keyboard Access are important accessibility work but are not current App Store Accessibility Nutrition Label categories.",
+        "Renames Closed Captions / SDH to Captions and Increase Contrast to Sufficient Contrast, while also covering Audio Descriptions and Reduced Motion.",
+        "Explains that labels should be claimed only when users can complete all common tasks with that feature on the relevant device type.",
+        "Calls for evidence such as a common-task test matrix, VoiceOver and Voice Control testing, text-size testing to at least 200% where supported, contrast checks, Reduce Motion checks, and caption/audio-description track or transcript review.",
+        "Warns that App Store accessibility label answers must remain accurate and should not be treated as marketing claims."
+      ]
+    },
+    {
+      "id": 2,
+      "name": "focus-boundary-routing",
+      "prompt": "A team asks the iOS accessibility skill to fix all focus bugs in a SwiftUI iPad app: VoiceOver focus is lost after closing a custom modal, Tab order skips a custom card, arrow-key movement between panels feels wrong, a tvOS build needs UIFocusGuide routing, and Voice Control names are duplicated. Give a concise scope review and the first fixes.",
+      "expected_output": "A boundary-aware accessibility focus answer that fixes assistive-technology focus and Voice Control issues while routing keyboard, directional, tvOS, and UIFocusGuide work to the focus-engine skill.",
+      "files": [],
+      "assertions": [
+        "Keeps VoiceOver/accessibility focus restoration after modal dismissal in ios-accessibility scope and recommends `@AccessibilityFocusState` or accessibility notifications.",
+        "Keeps duplicate Voice Control names in ios-accessibility scope and recommends unique, speakable labels and `accessibilityInputLabels` where appropriate.",
+        "Routes Tab order, `.focusable()`, `@FocusState`, arrow-key movement, focus sections, tvOS directional focus, and `UIFocusGuide` details to the focus-engine skill rather than expanding the accessibility skill into that domain.",
+        "Explains the distinction between accessibility focus for assistive technologies and keyboard/directional focus in the scene.",
+        "Still notes that accessibility element order can affect VoiceOver, Switch Control, Voice Control, and Full Keyboard Access traversal when reviewing user-facing UI."
+      ]
+    }
+  ]
+}