@mmerterden/multi-agent-pipeline 20.7.0 → 20.8.1

package/pipeline/skills/shared/external/swift-charts/evals/evals.json

@@ -2,45 +2,42 @@
   "skill_name": "swift-charts",
   "evals": [
     {
-      "id": 0,
-      "name": "chart3d-surface-setup",
-      "prompt": "We are targeting iOS 26 and need an interactive scientific visualization for z-depth data: render y = sin(2x) * cos(2z) as a 3D surface, keep the axes stable, and let the user inspect the view. What Swift Charts API should we use and what code shape should I start from?",
-      "expected_output": "Recommends Chart3D with SurfacePlot, labels x/y/z correctly, sets explicit x/y/z scale domains, binds Chart3DPose for inspection, and avoids using a 2D LinePlot/AreaPlot for the bivariate surface.",
+      "id": 1,
+      "prompt": "For our iOS 26 soil-science app I need to show moisture as a function of two field coordinates, easting and northing, over a 0 to 100 metre grid, and let users rotate the view. Write the chart.",
+      "expected_output": "A Chart3D with a SurfacePlot whose closure computes the value from two inputs, explicit domains on all three axes, and a bound pose.",
       "files": [],
-      "expectations": [
-        "Uses Chart3D and SurfacePlot for the iOS 26 bivariate surface instead of a 2D Chart with LinePlot or AreaPlot.",
-        "Shows or describes SurfacePlot with x, y, and z labels and a closure of the form y = f(x, z).",
-        "Sets or recommends explicit chartXScale, chartYScale, and chartZScale domains for stable comparisons.",
-        "Mentions Chart3DPose or chart3DPose for interactive inspection.",
-        "Notes that Chart3D should be used for real spatial or surface data, not as decoration for ordinary 2D charts."
+      "assertions": [
+        "Uses Chart3D with SurfacePlot rather than a 2D LinePlot or AreaPlot.",
+        "Labels x, y and z and writes the closure as y = f(x, z).",
+        "Sets explicit domains with chartXScale, chartYScale and chartZScale.",
+        "Binds a Chart3DPose state value through chart3DPose.",
+        "Notes that Chart3D is meant for real spatial or surface data, not decoration of 2D data."
       ]
     },
     {
-      "id": 1,
-      "name": "angle-selection-review",
-      "prompt": "Review this Swift Charts donut snippet: `@State private var selectedProduct: String?`; each `SectorMark(angle: .value(\"Sales\", item.sales))` sets opacity by comparing `selectedProduct == item.name`; the chart ends with `.chartAngleSelection(value: $selectedProduct)`. It compiles strangely. What is wrong and how should we fix the selection model?",
-      "expected_output": "Explains that chartAngleSelection binds the selected plottable angle value, uses a numeric binding such as Double?, maps the value back to a category with cumulative sector ranges, and keeps normal SectorMark pie/donut readability guidance.",
+      "id": 2,
+      "prompt": "Review this donut chart: `@State var selected: String?` is bound with `.chartAngleSelection(value: $selected)`, the sectors come straight from 18 expense categories including some with zero or refund (negative) amounts, and the highlighted sector is the one whose name equals `selected`. Tapping never highlights anything.",
+      "expected_output": "A review that explains the angle binding, fixes the selection mapping and gives the sector-count and value guidance.",
       "files": [],
-      "expectations": [
-        "States that chartAngleSelection(value:) binds a Plottable angle value rather than the sector's category string.",
-        "Replaces the String? selection binding with a numeric angle binding such as Double?.",
-        "Maps the selected angle through cumulative sales/value ranges to derive the selected product/category.",
-        "Keeps SectorMark readability guidance such as positive values, limiting to 5-7 sectors, or grouping small slices into Other.",
-        "Does not route this bug to generic SwiftUI state management as the primary fix."
+      "assertions": [
+        "Explains that chartAngleSelection binds a plottable angle value, not the category string.",
+        "Replaces String? with Double? (matching the plotted value type).",
+        "Maps the selected value to a category through cumulative sector ranges.",
+        "Says sector values must be positive and recommends five to seven sectors with an Other group.",
+        "Does not frame the problem as a generic state-management bug."
       ]
     },
     {
-      "id": 2,
-      "name": "boundary-routing",
-      "prompt": "A dashboard request mixes Swift Charts, MapKit annotations, NavigationStack deep links, async data loading, @Observable model ownership, and a custom VoiceOver audit. Split what belongs in the swift-charts skill versus adjacent Apple skills, then give the chart-specific recommendations.",
-      "expected_output": "Keeps chart construction, marks, axes/scales, selection/scrolling, vectorized plots, Chart3D, and chart accessibility basics in swift-charts while routing map annotations, navigation, data loading, Observation architecture, and detailed accessibility audits to sibling skills.",
+      "id": 3,
+      "prompt": "We're building a delivery dashboard: a map with pins for each driver, a NavigationStack that deep-links into a driver's chart, an async loader with an @Observable store, a scrollable line chart of deliveries per hour with selection, and it must work well with VoiceOver. What should the chart code look like and what else do we need?",
+      "expected_output": "Chart guidance in depth, with the non-chart parts routed to other skills and chart accessibility still covered.",
       "files": [],
-      "expectations": [
-        "Keeps Swift Charts chart type selection, marks, axes/scales, legends, annotations, selection, scrolling, vectorized plots, and Chart3D guidance in swift-charts scope.",
-        "Routes MapKit annotations or map overlays to MapKit guidance rather than treating them as chart marks.",
-        "Routes NavigationStack/deep-link implementation to swiftui-navigation.",
-        "Routes async networking/data loading and @Observable model ownership details to the appropriate networking, concurrency, or SwiftUI architecture skills.",
-        "Routes a deep VoiceOver/accessibility audit to ios-accessibility while still giving chart-specific label, color, Dynamic Type, and audio graph considerations."
+      "assertions": [
+        "Covers the chart itself: marks, axes and scales, legend, annotations, selection and scrolling, and when vectorized plots or Chart3D would apply.",
+        "Routes map pins and overlays to MapKit guidance.",
+        "Routes NavigationStack and deep links to swiftui-navigation.",
+        "Routes the async loader and @Observable ownership to networking, concurrency or SwiftUI architecture skills.",
+        "Routes a full VoiceOver audit to ios-accessibility while still giving chart label, colour, Dynamic Type and audio graph advice."
       ]
     }
   ]