cms-collection-setup

You can automate Webflow CMS collection creation by defining the display name, singular name, fields, and reference relationships, then confirming to execute the setup. This Skill validates plan limits and naming conflicts, creates collections in the correct order, and captures collection IDs after setup.

Yes, you can automatically create reference and multi-reference fields between Webflow CMS collections. The Skill resolves dependencies for related collections, ensuring that referenced collections exist before creating the fields that point to them, maintaining safe and ordered creation.

To set up a Webflow CMS content model, you need to provide the collection display name, singular name, optional slug, and field definitions including names and types. You also identify any references to other collections, then preview the complete schema before confirming creation.

Yes, the Skill validates Webflow plan limits before creating CMS collections and fields. It checks for naming conflicts and resolves dependencies to ensure your content model setup does not exceed your current plan restrictions or create duplicate collection names.

Webflow CMS reference fields require the parent collection to exist first. The Skill handles this by resolving dependencies and creating collections, static fields, and reference fields in the correct ordered sequence, then performs post-creation verification to confirm successful setup.

Yes, you can preview the complete Webflow CMS collection schema before creation. The Skill generates a full preview of your collections and fields, allowing you to verify the content model and confirm accuracy before executing the actual setup commands.