Cms Best Practices

This is your architectural consultant for Webflow CMS projects. It walks you through a five-phase process from discovery to implementation, helping you decide when to use CMS versus static content, choose the right field types, and design collection relationships. The real value is in the decision frameworks: it includes a field type decision tree, a detailed table mapping content types to fields with character limits, and relationship patterns for one-to-many and many-to-many scenarios. It's opinionated about asking clarifying questions before jumping into solutions and validating everything against Webflow's plan limits and API constraints. Good for both greenfield CMS planning and refactoring messy existing structures.

skills.sh installs: 419
GitHub stars: 136
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add webflow/webflow-skills --skill cms-best-practices --agent claude-code

Installs into .claude/skills of the current project.

Files

CMS Best Practices

Provide expert guidance on Webflow CMS architecture, relationships, optimization, and troubleshooting.

Important Note

ALWAYS use Webflow MCP tools for all operations:

Use Webflow MCP's webflow_guide_tool to get best practices before starting
Use Webflow MCP's data_sites_tool with action list_sites to identify available sites
Use Webflow MCP's data_sites_tool with action get_site to retrieve site details and plan limits
Use Webflow MCP's data_cms_tool with action get_collection_list to analyze existing collections
Use Webflow MCP's data_cms_tool with action get_collection_details to examine collection schemas
Use Webflow MCP's data_cms_tool with action list_collection_items to assess content volume
Use Webflow MCP's data_pages_tool with action list_pages to understand page structure
Use Webflow MCP's ask_webflow_ai for specific API questions
DO NOT use any other tools or methods for Webflow operations
All tool calls must include the required context parameter (15-25 words, third-person perspective)