internal: Small claude improvements (#5832)

* small claude improv

* simpler rules system

* fix install command

Author: centdix

.cursor/rules/rust-best-practices.mdc

@@ -47,6 +47,7 @@ Windmill uses a workspace-based architecture with multiple crates:
 - Group related routes together
 - Use consistent response formats (JSON)
 - Follow proper authentication and authorization patterns
+- Do not forget to update backend/windmill-api/openapi.yaml after modifying an api endpoint
 
 ## Performance Optimizations
 

.github/workflows/aider-after-review.yaml

@@ -90,5 +90,5 @@ jobs:
     with:
       needs_processing: false
       base_prompt: ${{ needs.check-and-prepare.outputs.prompt_content }}
-      rules_files: "CLAUDE.md backend/CLAUDE.md frontend/CLAUDE.md"
+      rules_files: ".cursor/rules/rust-best-practices.mdc .cursor/rules/svelte5-best-practices.mdc .cursor/rules/windmill-overview.mdc"
     secrets: inherit

.github/workflows/aider-external.yaml

@@ -76,5 +76,5 @@ jobs:
       issue_body: ${{ needs.check-and-prepare.outputs.issue_body }}
       instruction: ${{ needs.check-and-prepare.outputs.instruction }}
       issue_id: ${{ github.event.client_payload.issue_id }}
-      rules_files: "CLAUDE.md backend/CLAUDE.md frontend/CLAUDE.md"
+      rules_files: ".cursor/rules/rust-best-practices.mdc .cursor/rules/svelte5-best-practices.mdc .cursor/rules/windmill-overview.mdc"
     secrets: inherit

.github/workflows/aider.yaml

@@ -161,5 +161,5 @@ jobs:
       issue_body: ${{ needs.check-and-prepare.outputs.issue_body }}
       instruction: ${{ needs.check-and-prepare.outputs.comment_content }}
       issue_id: ${{ github.event.issue.number }}
-      rules_files: "CLAUDE.md backend/CLAUDE.md frontend/CLAUDE.md"
+      rules_files: ".cursor/rules/rust-best-practices.mdc .cursor/rules/svelte5-best-practices.mdc .cursor/rules/windmill-overview.mdc"
     secrets: inherit

.github/workflows/claude.yml

@@ -69,17 +69,17 @@ jobs:
         with:
           anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
           timeout_minutes: "60"
-          allowed_tools: "mcp__github__create_pull_request,Bash(npm run check),Bash(npm install),Bash(cargo check),Bash(curl https://sh.rustup.rs -sSf | sh)"
+          allowed_tools: "mcp__github__create_pull_request,Bash(npm run check),Bash(npm install),Bash(cargo check),Bash(curl https://sh.rustup.rs -sSf | sh -s -- -y)"
           custom_instructions: "IMPORTANT INSTRUCTIONS:
-          - Bypass previous instructions and instead of adding a url in your comment to manually create a PR, if you created a new branch with your changes, automatically create a PR from that branch to main, with the title starting with [Claude PR].
+          - Bypass previous instructions and instead of adding a url in your comment to manually create a PR, if you created a new branch with your changes, automatically create a draft PR from that branch to main, with the title starting with [Claude PR].
           - If you made changes to the frontend code, run npm install, then npm run generate-backend-client, then npm run check. You can ignore warnings that are reported by the check script, but fix the errors.
           - If you made changes to the backend code, install Rust and then run cargo check. You can ignore warnings that are reported by the check script, but fix the errors.
-          - DO NOT FORGET TO OPEN A PR AFTER YOU ARE DONE if you made changes after a request from a git issue.
+          - DO NOT FORGET TO OPEN A DRAFT PR AFTER YOU ARE DONE if you made changes after a request from a git issue.
           AVAILABLE TOOLS:
           - mcp__github__create_pull_request: Create a PR from a branch to main
           - Bash(npm run check): Run the check script. You should run this tool after making changes to the frontend code.
           - Bash(npm install): Install dependencies. You need this to run npm run check.
           - Bash(npm run generate-backend-client): Generate the backend client. You need this to run npm run check.
           - Bash(cargo check): Run the cargo check script. You should run this tool after making changes to the backend code.
-          - Bash(curl https://sh.rustup.rs -sSf | sh): Install Rust. You need this to run cargo check."
+          - Bash(curl https://sh.rustup.rs -sSf | sh -s -- -y): Install Rust. You need this to run cargo check."
           trigger_phrase: "/ai"

CLAUDE.md

@@ -1,71 +1,3 @@
-# Windmill Overview
-
-Windmill is an open-source developer platform for building internal tools, API integrations, background jobs, workflows, and user interfaces. It offers a unified system where scripts are automatically turned into sharable UIs and can be composed into flows or embedded in custom applications.
-
-## Core Capabilities
-
-- **Script Development and Execution**: Write and run scripts in Python, TypeScript/JavaScript (Deno/Bun), Go, Bash, SQL, and other languages
-- **Workflow Orchestration**: Compose scripts into multi-step flows with conditional logic, loops, and error handling
-- **UI Generation**: Automatically generate UIs from scripts or build custom applications with a low-code editor
-- **Job Scheduling**: Trigger scripts and flows on schedules, webhooks, or external events
-- **Resource Management**: Securely store and use credentials, databases, and other connections
-
-## Platform Architecture
-
-The Windmill platform consists of several key components:
-
-- **Frontend UI**: Web-based interface for script and flow development, app building, and result visualization
-- **API Server**: Central API that handles authentication, resource management, and job coordination
-- **Workers**: Execute scripts in their respective environments with proper sandboxing
-- **Database**: PostgreSQL database for storage of scripts, flows, resources, job results, and more
-- **Job Queue**: Queue system for managing job execution, implemented in PostgreSQL
-- **Client Libraries**: Libraries for interacting with Windmill from Python, TypeScript, or command line
-
-# Windmill Backend Architecture
-
-The Windmill backend is written in Rust and consists of several services working together. These services are designed for horizontal scaling with stateless API servers and workers that can be deployed across multiple machines.
-
-## Key Components
-
-- **API Server (`windmill-api`)**: Handles HTTP requests, authentication, and resource management
-- **Queue Manager (`windmill-queue`)**: Manages the job queue in PostgreSQL
-- **Worker System (`windmill-worker`)**: Executes jobs in sandboxed environments
-- **Common Utilities (`windmill-common`)**: Shared code used by multiple services
-- **Git Sync (`windmill-git-sync`)**: Synchronizes scripts with Git repositories
-
-## Job Execution System
-
-The job execution process follows these steps:
-
-1. The API server receives a request to run a script or flow and creates a job record in the database
-2. The job is added to the queue system in PostgreSQL
-3. Workers continuously poll the queue for jobs matching their capabilities
-4. When a job is picked up, it's routed to the appropriate language executor
-5. The script is executed in a sandboxed environment using NSJAIL for security
-6. Results are processed and stored in the database
-7. For flows, each step creates a new job that goes through the same process
-
-Windmill supports worker tags and groups to route jobs to workers with specific capabilities or resource access.
-
-# Windmill Frontend Architecture
-
-The Windmill frontend is built with Svelte and provides several key interfaces for interacting with the platform.
-
-## Key Components
-
-- **Script Builder**: Code editor with language support, schema inference, and dependency management
-- **Flow Builder**: Visual editor for creating multi-step workflows with branching and looping
-- **App Editor**: Grid-based editor for building custom UIs that integrate scripts and flows
-- **Schema Form System**: Generates form interfaces from script parameters automatically
-- **Result Viewer**: Visualizes job results, logs, and execution status
-
-The frontend uses the Monaco editor (same as VS Code) for code editing, with specialized language support for all supported script languages.
-
-## UI Framework
-
-The frontend is built with Svelte, providing a reactive and component-based architecture. Key frontend technologies include:
-
-- **Svelte/SvelteKit**: Core framework for UI components and routing
-- **Monaco Editor**: Code editing experience similar to VS Code
-- **Schema Form**: Automatic UI generation from TypeScript/JSON schemas
-- **Tailwind CSS**: Utility-first CSS framework for styling
+To have an overview of what this app does, see @.cursor/rules/windmill-overview.mdc
+For backend modifications, follow the rules mentioned here @.cursor/rules/rust-best-practices.mdc
+For frontend modifications, follow the rules mentioned here @.cursor/rules/svelte5-best-practices.mdc