Have the prototype checklist cd to the command directory
Check instruction packages / check (push) Successful in 4s
Check instruction packages / check (push) Successful in 4s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
a968e669c0
commit
87ebe1683e
2 files changed
+2
-2
No files matched your search
@@ -26,7 +26,7 @@ The Human answers the question by using the prototype the way the software's use
|
||||
|
||||
Work through this checklist, then give the Human the shell command and the first command to try:
|
||||
|
||||
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 it with an unknown option from the command directory and confirm its usage message names the command as the user types it.
|
||||
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.
|
||||
4. The command directory is set with `configure` to where the app's user runs the app.
|
||||
|
||||
@@ -9,7 +9,7 @@
|
||||
"files": [
|
||||
{
|
||||
"path": "SKILL.md",
|
||||
"sha256": "e3ce203d245e6a264a0159672610c84032c38bc1dd3892335561fed4e5531eb3"
|
||||
"sha256": "53faaae81e3ed97345a0887c7f6d6779f0f1de82d83697e4bf48d3250596658c"
|
||||
}
|
||||
]
|
||||
}
|
||||
Reference in new issue
Block a user