Add a prototype reset command only when the scenario changes

A read-only command such as a dry-run leaves nothing to restore, yet naming a
reset command as the example helper led Designers to build one for every
prototype. The method and checklist now ask for a reset command only when a
command the Human will try changes the scenario.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

packages/designer-prototype/SKILL.md

@@ -19,7 +19,7 @@ The Human answers the question by using the prototype the way the software's use
 - Put the scenario's data where the app finds it by default, such as its default config or source directory under HOME, so the user's command needs no extra options.
 - Make the Human's first command one the software's user will type: the real command name, the syntax this change proposes, and the arguments a user would pass, run from the directory where a user would be.
 - Give each command to try exactly as that user types it, and say what it shows.
-- When the scenario needs restoring between tries, give a reset command by its name alone, followed by the user's command to try again.
+- Add a reset command only when a command the Human will try changes the scenario, such as a real update; then put it in `/scratch/bin` and give it by its name alone, followed by the command to try again.
 - Ask the Human about what they saw as a user of the software, in terms of the design question.
 
 ## Before handing over
@@ -28,6 +28,6 @@ Work through this checklist, then give the Human the shell command and the first
 
 1. The app's command runs by its own name from `/scratch/bin`: a configured command the owner listed, or a launcher you wrote. Run `cd` to the command directory, then the command with an unknown option, and confirm its usage message names the command as the user types it.
 2. The scenario's data is where the app finds it by default under the workspace's HOME.
-3. Helper commands, such as a reset command, are in `/scratch/bin`, so the Human runs each by its name.
+3. Helper commands are in `/scratch/bin`, so the Human runs each by its name.
 4. The command directory is set with `configure` to where the app's user runs the app.
 5. You ran the first command to try yourself, exactly as the Human will type it, from that directory, and it showed what the question is about.

packages/designer-prototype/relayview-skill.json

@@ -9,7 +9,7 @@
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "53faaae81e3ed97345a0887c7f6d6779f0f1de82d83697e4bf48d3250596658c"
+      "sha256": "0f39f7db296649dba3024bbeaadac9124fdf04c99c246d1f91772bab51d2e795"
     }
   ]
 }