What problem does it solve? Writing frontend code in the Windmill repository requires following project-specific conventions: using the internal design-system components instead of raw HTML, Tailwind-only styling, lucide-svelte icons, and Svelte 5 runes syntax. This Skill ensures every Svelte change in the frontend directory follows those rules and is verified before finalizing. ## Core Features & Use Cases - Design-System Enforcement: Mandates Windmill components like Button, TextInput, and Select with documented props instead of raw HTML elements. - Styling & Icon Conventions: Enforces Tailwind CSS for styling, Windmill theming classes, and lucide-svelte for all icons. - Verification Workflow: Directs use of the Svelte MCP autofixer on all code and Playwright MCP to confirm changes in the running frontend. - Use Case: When adding a new settings form to the Windmill app, use this Skill to build it with TextInput and Select components at unified sizes, run the svelte-autofixer until clean, and verify the page in a browser via Playwright. ## Quick Start Use the svelte-frontend skill to add a new form with a text input and save button to the Windmill frontend settings page.
