mirroir-mcp 0.15.0 → 0.16.0

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 (3) hide show
  1. package/install.js +1 -1
  2. package/package.json +1 -1
  3. package/prompts/diagnosis.md +5 -5
package/install.js CHANGED
@@ -9,7 +9,7 @@ const fs = require("fs");
9
9
  const path = require("path");
10
10
  const { execSync } = require("child_process");
11
11
 
12
- const VERSION = "0.14.1";
12
+ const VERSION = "0.16.0";
13
13
  const REPO = "jfarcand/mirroir-mcp";
14
14
  const BINARY = "mirroir-mcp";
15
15
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mirroir-mcp",
3
- "version": "0.15.0",
3
+ "version": "0.16.0",
4
4
  "description": "MCP server that controls a real iPhone through macOS iPhone Mirroring. Screenshot, tap, swipe, type — from any MCP client.",
5
5
  "mcpName": "io.github.jfarcand/mirroir-mcp",
6
6
  "license": "Apache-2.0",
package/prompts/diagnosis.md CHANGED
@@ -1,15 +1,15 @@
1
1
  # iOS UI Automation Failure Diagnosis
2
2
 
3
- You are an expert iOS UI automation debugger analyzing a failed test scenario
4
- from **mirroir-mcp**, a tool that replays YAML scenarios against
3
+ You are an expert iOS UI automation debugger analyzing a failed test skill
4
+ from **mirroir-mcp**, a tool that replays YAML skills against
5
5
  iPhone Mirroring on macOS.
6
6
 
7
7
  ## Context
8
8
 
9
9
  You will receive a JSON payload containing:
10
10
 
11
- - **scenarioName**: The name of the scenario that failed
12
- - **scenarioFilePath**: Path to the source YAML file
11
+ - **skillName**: The name of the skill that failed
12
+ - **skillFilePath**: Path to the source YAML file
13
13
  - **failedSteps**: Array of steps that failed, each with:
14
14
  - `stepIndex`: Zero-based step number
15
15
  - `stepType`: The action type (`tap`, `wait_for`, `assert_visible`, `scroll_to`, etc.)
@@ -31,7 +31,7 @@ Analyze the failure context and provide:
31
31
  2. **FIX** -- Concrete actionable fix:
32
32
  - Coordinate changes with specific values
33
33
  - Timing adjustments (increase delay, add wait_for step)
34
- - Scenario edits (add intermediate navigation, change step order)
34
+ - Skill edits (add intermediate navigation, change step order)
35
35
 
36
36
  3. **CONFIDENCE** -- `high`, `medium`, or `low`
37
37