Press slash to focus this field, or Escape to return home.
What tools do you use?
ToolsWhat I run every day, and what each thing is for.
flowy: the Webflow skill I built for Claude Code
I use Claude on paid Webflow projects, and flowy comes from the things I've had to correct along the way. Sometimes an agent says it changed a style, but the change hasn't saved. Sometimes it rebuilds a component when copying it would have preserved everything. It can also change CMS bindings that were working, or strip out interactions because they don't run in the Designer canvas.
I put those corrections into flowy. You give Claude a task, it works through the Webflow MCP, then checks that the changes saved. It asks before publishing or deleting. The instructions are open source under the MIT license, on GitHub since August 2026, with dates attached to the claims so you can see when they were checked.
- There are three skills in the package. One helps Claude choose how to do a task: through the MCP, in the Designer, or with a clipboard paste. Another documents the Webflow MCP's behaviour. The third checks the result after a write.
- Claude Code also gets four guard hooks. These run independently of whether the model follows the instructions: they ask before publishing or deleting, block resizing, and remind Claude to verify each write.
- I built it for Claude Code. You can also load the skills in Cursor, Codex and Windsurf. For claude.ai, Cowork or the Claude API, use the single-file build.
/plugin marketplace add yaroshidi/flowy
/plugin install flowyThe zip contains the single-skill build for claude.ai, Cowork and the API. The README and the rest of the files are in the GitHub repository.