A relentless interview to sharpen a plan or design.
Skills in this repository
windmill-labs/windmill - Page 2
SkillsMP has collected 59 skills from windmill-labs/windmill. Open a skill to review its source and details.
windmill-labs/windmillShowing 19 of 59 collected skills.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
End-of-session reflection. Reviews friction encountered during the session and proposes updates to docs/ to capture lessons learned.
Rust coding guidelines for the Windmill backend. MUST use when writing or modifying Rust code in the backend directory.
How to safely update SQLx offline query cache. MUST use when SQL queries change.
MUST use when configuring schedules.
MUST use when configuring triggers.
Code review the current PR (or branch diff against main) for bugs, security, and AGENTS.md compliance. MUST use when asked to review code.
Create a git commit with conventional commit format. MUST use anytime you want to commit changes.
Checklist for adding a new TriggerCrud-based trigger type to Windmill (Azure, GCP, Kafka, etc.). Use when wiring a new trigger kind across backend, frontend, CLI, and capture infrastructure.
MUST use when opening the Windmill dev page / visual preview of a flow, script, or app. Triggers on words like preview, open, navigate to, visualize, see the flow/app/script, and after writing a flow/script/app for visual verification.
Guidance for adding native trigger services to Windmill. Use when implementing or modifying native trigger integrations across the backend and frontend.
Open a draft pull request on GitHub. MUST use when you want to create/open a PR.
Code review a pull request for bugs and CLAUDE.md compliance. MUST use when asked to review code.
End-of-session reflection. Reviews friction encountered during the session and proposes updates to docs/ to capture lessons learned.
Rust coding guidelines for the Windmill backend. MUST use when writing or modifying Rust code in the backend directory.
Svelte coding guidelines for the Windmill frontend. MUST use when writing or modifying code in the frontend directory.
Create a git commit with conventional commit format. MUST use anytime you want to commit changes.