From 10d0b950c2f8b509e80a654bde9500c8a69c71e3 Mon Sep 17 00:00:00 2001 From: hugocasa Date: Thu, 11 Jun 2026 14:57:45 +0200 Subject: [PATCH] docs(skills): reconcile raw-app generate-metadata stance (agent offers+runs) Co-Authored-By: Claude Opus 4.8 (1M context) --- cli/src/guidance/skills.gen.ts | 7 ++++--- system_prompts/auto-generated/skills/raw-app/SKILL.md | 7 ++++--- system_prompts/base/raw-app-cli.md | 7 ++++--- 3 files changed, 12 insertions(+), 9 deletions(-) diff --git a/cli/src/guidance/skills.gen.ts b/cli/src/guidance/skills.gen.ts index f16584d005..c1c882993e 100644 --- a/cli/src/guidance/skills.gen.ts +++ b/cli/src/guidance/skills.gen.ts @@ -5061,15 +5061,16 @@ data: ## CLI Commands -\`wmill app new\` is the exception: you run it yourself, with flags, per the "Creating a Raw App" section above. +Two commands you run yourself, not the user: +- \`wmill app new\` — run it with flags, per the "Creating a Raw App" section above. +- \`wmill generate-metadata\` — generates local lock files; offer it and run it on consent, per "After creating a runnable" above (it writes local lock files, not a deploy). -For everything else, tell the user which command fits their intent and let them run it — these touch the workspace or local lock files, and the user should consent each time: +For the rest, tell the user which command fits their intent and let them run it — these deploy to the workspace, overwrite local files, or launch a long-running server, so the user should consent each time: | Command | Description | |---------|-------------| | \`wmill app dev\` | Start dev server with live reload (see the \`preview\` skill for the full open-the-app-in-the-IDE-pane procedure). | | \`wmill app generate-agents\` | Refresh AGENTS.md and DATATABLES.md | -| \`wmill generate-metadata\` | Generate lock files for backend runnables | | \`wmill sync push\` | Deploy app to Windmill | | \`wmill sync pull\` | Pull latest from Windmill | diff --git a/system_prompts/auto-generated/skills/raw-app/SKILL.md b/system_prompts/auto-generated/skills/raw-app/SKILL.md index 8dc97b58ac..ad89af6159 100644 --- a/system_prompts/auto-generated/skills/raw-app/SKILL.md +++ b/system_prompts/auto-generated/skills/raw-app/SKILL.md @@ -217,15 +217,16 @@ data: ## CLI Commands -`wmill app new` is the exception: you run it yourself, with flags, per the "Creating a Raw App" section above. +Two commands you run yourself, not the user: +- `wmill app new` — run it with flags, per the "Creating a Raw App" section above. +- `wmill generate-metadata` — generates local lock files; offer it and run it on consent, per "After creating a runnable" above (it writes local lock files, not a deploy). -For everything else, tell the user which command fits their intent and let them run it — these touch the workspace or local lock files, and the user should consent each time: +For the rest, tell the user which command fits their intent and let them run it — these deploy to the workspace, overwrite local files, or launch a long-running server, so the user should consent each time: | Command | Description | |---------|-------------| | `wmill app dev` | Start dev server with live reload (see the `preview` skill for the full open-the-app-in-the-IDE-pane procedure). | | `wmill app generate-agents` | Refresh AGENTS.md and DATATABLES.md | -| `wmill generate-metadata` | Generate lock files for backend runnables | | `wmill sync push` | Deploy app to Windmill | | `wmill sync pull` | Pull latest from Windmill | diff --git a/system_prompts/base/raw-app-cli.md b/system_prompts/base/raw-app-cli.md index b9102e9753..70e6d8135f 100644 --- a/system_prompts/base/raw-app-cli.md +++ b/system_prompts/base/raw-app-cli.md @@ -212,15 +212,16 @@ data: ## CLI Commands -`wmill app new` is the exception: you run it yourself, with flags, per the "Creating a Raw App" section above. +Two commands you run yourself, not the user: +- `wmill app new` — run it with flags, per the "Creating a Raw App" section above. +- `wmill generate-metadata` — generates local lock files; offer it and run it on consent, per "After creating a runnable" above (it writes local lock files, not a deploy). -For everything else, tell the user which command fits their intent and let them run it — these touch the workspace or local lock files, and the user should consent each time: +For the rest, tell the user which command fits their intent and let them run it — these deploy to the workspace, overwrite local files, or launch a long-running server, so the user should consent each time: | Command | Description | |---------|-------------| | `wmill app dev` | Start dev server with live reload (see the `preview` skill for the full open-the-app-in-the-IDE-pane procedure). | | `wmill app generate-agents` | Refresh AGENTS.md and DATATABLES.md | -| `wmill generate-metadata` | Generate lock files for backend runnables | | `wmill sync push` | Deploy app to Windmill | | `wmill sync pull` | Pull latest from Windmill |