docs: update VSCode extension documentation with new features (#1060)

* docs: update VSCode extension documentation with new features

- Add CLI workspace settings integration info
- Document wmill init command''s AI file creation features (cursor rules, CLAUDE.md)
- Add flow.yaml validation syntax feature

Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>

* better

* cleaning

---------

Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
Co-authored-by: centdix <[email protected]>

Author: 3 people

changelog/2025-08-12-vscode-syntax-and-config/index.md

@@ -0,0 +1,13 @@
+---
+slug: vscode-syntax-and-config
+version: v1.523.0
+title: VS Code improvements
+tags: ['VS Code']
+description: Two new improvements on the VS Code extension. It will now automatically sync its workspaces configuration with the windmill CLI ones, and has yaml syntax validation for flow.yaml files.
+features:
+  [
+    'Flow.yaml syntax validation',
+    'Workspace configuration sync with CLI',
+  ]
+docs: /docs/cli_local_dev/vscode-extension
+---

docs/advanced/4_local_development/index.mdx

@@ -302,6 +302,10 @@ Syncing directly from the CLI is great, but instead of using the CLI directly, y
 	/>
 </div>
 
+## LLMs rules for local development
+
+The `wmill init` command will create cursor rules and CLAUDE.md files to enhance your AI experience when working with scripts and flows. These files provide context and guidelines for AI assistants to better assist you in creating scripts and flows that match Windmill's guidelines. You can safely delete them if you do not use LLMs on your local development.
+
 ## Run locally
 
 Windmill has its [own integrated development environment](../../code_editor/index.mdx). But for iteration, integration with CI/CD and testing purposes you may need to run a script locally that also interacts with Windmill (for example, to retrieve resources). It will allow you to integrate Windmill with any testing framework.

docs/cli_local_dev/1_vscode-extension/index.mdx

@@ -58,13 +58,11 @@ First of all, have your workspace synced locally with [Windmill CLI](../../advan
 
 With [wmill sync pull](../../advanced/3_cli/sync.mdx#pulling) and [wmill sync push](../../advanced/3_cli/sync.mdx) you can synchronize your remote workspace to a local directory which you would version with GitHub / GitLab.
 
-In the settings menu, set the remote url, workspace name and [token](../../core_concepts/4_webhooks/index.mdx#user-token).
+Then you can:
 
 1. Install the [extension](https://marketplace.visualstudio.com/items?itemName=windmill-labs.windmill).
 
-2. Enter your Windmill remote URL and [token](../../core_concepts/4_webhooks/index.mdx#user-token), so the extension can execute scripts and flows on your workspace.
-
-3. From any script file, use `> Windmill: Run preview in the current editor` or Ctrl+Enter and Shift+Enter to generate the UI preview (provided that the script meets the [few rules](../../core_concepts/13_json_schema_and_parsing/index.mdx#json-schema-in-windmill) required by Windmill).
+2. From any script file, use `> Windmill: Run preview in the current editor` or Ctrl+Enter and Shift+Enter to generate the UI preview (provided that the script meets the [few rules](../../core_concepts/13_json_schema_and_parsing/index.mdx#json-schema-in-windmill) required by Windmill).
 
 All details to set up the workspace folder:
 
@@ -120,6 +118,10 @@ Editing the flow from the UI immediately modifies the YAML definition
 	src="/videos/yaml_to_ui.mp4"
 />
 
+### Flow YAML validation
+
+The VS Code extension includes syntax validation for flow.yaml files, making it easier to spot mistakes and ensure your flows are properly formatted before testing or deployment.
+
 ### Infer lockfile or use current lockfile
 
 With this toggle, you can choose to use the metadata lockfile ([derived from](../../advanced/3_cli/script.md#packagejson--requirementstxt) package.json or requirements.txt after [`wmill script generate-metadata`](../../advanced/3_cli/script.md#re-generating-a-script-metadata-file)) instead of inferring them directly from the script.
@@ -142,15 +144,18 @@ Access these commands through the Command Palette (Ctrl/Cmd+Shift+P):
 
 ## Settings
 
+The extension automatically uses workspace settings from your Windmill CLI configuration if available. This provides seamless integration between the CLI and VS Code extension without needing to configure settings separately.
+
 The extension provides the following settings:
 
 | Setting                         | Description                                                                                                  |
 | ------------------------------- | ------------------------------------------------------------------------------------------------------------ |
 | `windmill.remote`               | The full remote URL including http and trailing slash. By default, it's "https://app.windmill.dev/".         |
 | `windmill.workspaceId`          | The workspace id to use.                                                                                     |
-| `windmill.token`                | The token to use to authenticate with the remote and workspace.                                              |
+| `windmill.token`                | The [token](../../core_concepts/4_webhooks/index.mdx#user-token) to use to authenticate with the remote and workspace.                                              |
 | `windmill.additionalWorkspaces` | The list of additional remotes to use. This allows you to set up multiple workspaces for different projects. |
 | `windmill.currentWorkspace`     | The workspace name currently used (if multiple). main or empty is the default one.                           |
+| `windmill.configFolder`         | Override the CLI config folder path to fetch the workspace settings from.                                    |
 
 ![demo](./wm-settings.png.webp)