Open
Conversation
Interactive workflow to design Payload collections from source CMS data. Config-first approach: establish data structure through conversation before any data import. Includes: - SKILL.md with workflow phases and guidance - PAYLOAD-FIELD-REFERENCE.md with complete field type schemas - Select vs relationship disambiguation guidance - Migration patterns for WordPress, Contentful, Strapi
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This skill helps users migrate content to Payload from other CMSs like WordPress, Contentful, Strapi, Sanity, or Webflow.
The approach is config-first: instead of jumping straight to data import, Claude works with the user to design their Payload collections through conversation. The user provides sample data, Claude proposes a collection config and explains the reasoning, and they iterate until the structure is right. Only after all collections are confirmed does it move on to discussing the actual migration.
The skill includes a complete field reference so Claude can match source data patterns to appropriate Payload field types. It also addresses a common migration mistake where things like categories appear to be fixed values but actually need to be relationship fields so users can manage them later.