flowy plugin
Build on Webflow with Claude Code. Routes every task to the right hand (Webflow MCP, the Chrome-driven Designer, or clipboard paste), enforces publish and destructive-operation guards as hooks, and ships a field manual of observed Webflow MCP behaviour where every claim carries a date.
How to install the flowy plugin
Run both commands inside Claude Code. The first adds the marketplace once; the second installs the plugin.
/plugin marketplace add yaroshidi/flowy
/plugin install flowy@flowyWhat's inside flowy
7 parts read from the plugin's own files.
Commands 2
Run as /flowy:name- /flowy:doctor
Check that flowy's dependencies, config and guard hooks are actually working
- /flowy:setup[optional: browser name, e.g. Comet]
Create or update the flowy config at ~/.claude/flowy.config.md
Skills 3
Claude loads it when the task matches- flowy
Use when starting or planning ANY Webflow build, design, styling, layout, CMS, component, or edit task — before choosing tools — and the moment you are about to reach for a Webflow MCP write tool to do VISUAL or detail work. Owns which-hand routing (Webflow MCP vs the Chrome-driven Designer), the session lifecycle for both new builds and already-built sites, and the paste-first rule for third-party components. Invoke FIRST, before flowy-manual or flowy-verify.
- flowy-manual
Use when building on Webflow and you need to know what is actually true — a verified-only field manual of directly-observed behaviours, traps, schema quirks and fixes. Covers what changed in MCP 2.0.1, element and style traps, CMS bindings and Collection Lists, components and props, responsive breakpoints, Designer-canvas behaviours, and live diagnostic probes. Use alongside the flowy skill (which hand) and flowy-verify (did it land).
- flowy-verify
Use after a batch of Webflow MCP writes (data_whtml_builder, data_element_builder, data_element_tool, data_element_settings_tool, data_style_tool, data_cms_tool, data_component_tool, data_component_props_tool, data_component_variants_tool, data_variable_tool, data_scripts_tool, asset_tool, data_sites_tool publish) to verify the writes actually landed — catching silently-dropped classes, Webflow-injected style defaults, bindings that only look broken, and stale live-page state. A PostToolUse hook shipped with the flowy plugin reminds the agent to invoke this skill.
Hooks 2
Runs on these events- PostToolUsecommand
mcp__\S*[Ww]ebflow\S*__(data_whtml_builder|data_element_buil
- PreToolUsecommand
mcp__\S*[Ww]ebflow\S*__data_sites_tool, mcp__claude-in-chrome__resize_window, mcp__\S*[Ww]ebflow\S*__(data_assets_tool|data_component_tool
Using flowy in Claude Code
Type a command in a Claude Code session:
/flowy:doctor
/flowy:setup [optional: browser name, e.g. Comet]Skills need no command. Claude reads them when your request matches what they describe.
Update, turn off or remove
- Update the plugin (shell)
- claude plugin update flowy@flowy
- Refresh the marketplace
- /plugin marketplace update flowy
- Turn it off for now
- /plugin disable flowy@flowy
- Remove it
- /plugin uninstall flowy@flowy
Skills in flowy
- flowyyaroshidi/flowy
Use when starting or planning ANY Webflow build, design, styling, layout, CMS, component, or edit task — before choosing tools — and the moment you are about to reach for a Webflow MCP write tool to do VISUAL or detail work. Owns which-hand routing (Webflow MCP vs the Chrome-driven Designer), the session lifecycle for both new builds and already-built sites, and the paste-first rule for third-party components. Invoke FIRST, before flowy-manual or flowy-verify.
24 files7stars - flowy-manualyaroshidi/flowy
Use when building on Webflow and you need to know what is actually true — a verified-only field manual of directly-observed behaviours, traps, schema quirks and fixes. Covers what changed in MCP 2.0.1, element and style traps, CMS bindings and Collection Lists, components and props, responsive breakpoints, Designer-canvas behaviours, and live diagnostic probes. Use alongside the flowy skill (which hand) and flowy-verify (did it land).
6 files7stars - flowy-verifyyaroshidi/flowy
Use after a batch of Webflow MCP writes (data_whtml_builder, data_element_builder, data_element_tool, data_element_settings_tool, data_style_tool, data_cms_tool, data_component_tool, data_component_props_tool, data_component_variants_tool, data_variable_tool, data_scripts_tool, asset_tool, data_sites_tool publish) to verify the writes actually landed — catching silently-dropped classes, Webflow-injected style defaults, bindings that only look broken, and stale live-page state. A PostToolUse hook shipped with the flowy plugin reminds the agent to invoke this skill.
7stars
flowy plugin questions
How do I install the flowy plugin?
In Claude Code run /plugin marketplace add yaroshidi/flowy, then /plugin install flowy@flowy.
What does the flowy plugin include?
flowy bundles 2 commands, 3 skills, hooks.
What commands does the flowy plugin add?
It adds /flowy:doctor, /flowy:setup. Run them in Claude Code with the plugin prefix, for example /flowy:doctor.
How do I update or remove the flowy plugin?
Update it with claude plugin update flowy@flowy in your shell, or from the Installed tab of /plugin. Remove it with /plugin uninstall flowy@flowy.
What license is the flowy plugin under?
MIT, as stated in the plugin's manifest.