uniform-content-modeling
Best practices for content modeling in Uniform — designing content types with well-chosen fields, validations, and naming, deciding what belongs in structured content vs the experience layer, modeling content classification (categories, tags, taxonomies), modeling relationships between entries with references, designing content for discoverability across search and answer engines and multi-channel delivery, and organizing entries for reuse and localization. Use when creating or updating Uniform content types or entries, migrating structured content from another CMS into Uniform, or reviewing an existing content model for best-practice violations.
Install
With your agent
Install OMGSkills skill "uniformdev/agent-skills:skills/uniform-content-modeling" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/uniformdev/agent-skills /tmp/agent-skills && ln -s /tmp/agent-skills/skills/uniform-content-modeling ~/.claude/skills/uniform-content-modelingFrom README
Uniform content modeling Content modeling defines display-agnostic content types and the entries created from them. Experience modeling defines how content is displayed and composed via component definitions and patterns. Keep the two separate: this skill is about building content models that are reusable across presentations and channels. Key principles Model content, not presentation Display concerns (layout, styling, variants) belong in component definitions and patterns, not content types. Model classification once, deliberately Classify with select fields or references to a classification content type — never free text. Pick one mechanism per classification and reuse it across types. Model for findability Fields you filter or sort on must use filterable field types. Blocks, asset, image URL, JSON, and link fields cannot be filtered by the Edge Delivery API — decide query requirements before choosing field types.
More from this repo
uniform-enrichment-recommendations
Used to add personalized, relevance-ranked content recommendations to a Uniform + React/Next.js project by boosting...
uniform-experience-modeling
Best practices for experience modeling in Uniform — designing component definitions with well-chosen parameters, slots,...
uniform-forms
Used when adding a form (like contact, signup, newsletter, lead-capture or survey) to a Uniform project, when creating...