Webflow skills for Claude Code.

Twenty Agent Skills for driving a Webflow site with Claude. They are the working instructions from a real Webflow operation, not a tutorial written for GitHub.

Why they exist

The same mistakes kept happening. An agent creating a CMS field it then cannot delete. Publishing to production without checking what had changed since the last publish. Assuming the Designer API can reach something only the Data API can, and burning twenty minutes finding out.

Each of these skills is a fix that got written down after it cost me time. That is the whole origin. They are not comprehensive documentation and they are not trying to be, because the parts of Webflow that are well documented did not need writing down.

Install

Download the pack and drop the skills into your skills directory. Project level:

unzip webflow-skills.zip
mkdir -p .claude/skills
cp -R skills/* .claude/skills/

Or into ~/.claude/skills/ instead, so they load in every project. Claude picks a skill up on its own when the task matches, and you can invoke one by name.

Start with webflow-mcp-guide. Most of the pack assumes the Webflow MCP server is connected, and that skill covers the two connection routes plus the split between what the Data API and the Designer API can each reach. That distinction wastes more time than anything else in Webflow automation.

What is in the pack

Publishing and safety. safe-publish runs a plan, confirm, publish loop that shows what changed since the last publish. It exists because an agent that can publish can put a half-finished change in front of your customers.

CMS. cms-best-practices for architecture and the decisions that are painful to reverse, cms-collection-setup for building one, bulk-cms-update for writing many items with a diff preview first.

Audits. Whole-site health, WCAG 2.1 accessibility, broken and insecure links across CMS content, asset alt text, and SEO titles and descriptions with a before and after table to approve.

Building. Components including the marketer-facing assembly workflow, Interactions recipes, Flowkit naming, AI-generated React components, custom code within Webflow's limits.

Platform. Webflow Cloud deployments, the CLI and DevLink, and Google Ads through the Webflow app.

Publishing is the dangerous verb. Everything else an agent gets wrong you can fix quietly. Keep a human on that one step.

What this is not

Not affiliated with Webflow. Not a product, not supported, and not something I will be taking feature requests on. They are MIT licensed, so fork them and make them yours. That is the intended outcome.

One skill from my own set is deliberately held back, the AI search and structured data work, because it is specific to sites I run rather than generally useful.

Download the pack Have this built for you

123 KB. No email, no signup, no tracking on the file.