scaffold-cf-model

Scaffold Content Fragment models with consistent named fields and pageType mappings.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aramark-destinations/aramark-mb --skill scaffold-cf-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scaffold-cf-model
Source: https://github.com/aramark-destinations/aramark-mb/tree/main/.agents/skills/eds/scaffold-cf-model
Command: npx skills add https://github.com/aramark-destinations/aramark-mb --skill scaffold-cf-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Content Fragment models are the structured data backbone of the platform, powering cards, detail pages, carousels, and compare tools. When field names drift across models, blocks break and rework becomes costly. This skill provides a standardized approach to design CF models with consistent, reusable field contracts.

Core Features & Use Cases

  • Enforces the mandatory Step 1 card fields with exact names (title, eyebrow, shortDescription, images, button1Link, button1Text, button1Style, button1ThemeColor, button2Link, button2Text, button2Style, button2ThemeColor) to ensure cross-model compatibility.
  • Guides addition of Step 2 detail fields and Step 3 pageType mapping, enabling robust detail pages and Compare Tool readiness.
  • Use Case: When creating a new CF model for lodging or events, or reviewing an existing CF model for naming consistency across all content types.

Quick Start

Draft the CF model by listing the required Step 1 card fields with exact names, then add the Step 2 detail fields and a pageType mapping, following the Houseboat reference model as the canonical example.

Frequently Asked Questions about scaffold-cf-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Content Fragment model fields for consistent card rendering?

To standardize Content Fragment model fields, enforce exact Step 1 card field names like title, eyebrow, and shortDescription across all content types. This ensures cross-model compatibility so cards, carousels, and detail pages render uniformly without breaking.

What are the mandatory fields for a Content Fragment model detail page?

Mandatory Content Fragment model detail page fields include Step 1 card fields like title, images, and button links, plus Step 2 detail fields and a Step 3 pageType mapping. These ensure robust detail pages and Compare Tool readiness.

Why does my card block break when rendering different content types?

Card blocks break when Content Fragment field names drift across different models. Applying a standardized schema with exact field names and data types for lodging, dining, and events prevents this drift and avoids costly rework.

How do I map pageType across different Content Fragment models?

Map pageType by defining Step 3 pageType mappings in your Content Fragment model after listing Step 1 card fields and Step 2 detail fields. Use the Houseboat reference model as the canonical example for correct pageType configuration.

Can I include optional assets and scripts in my Content Fragment schema?

Yes, the Content Fragment schema supports optional script, reference, and assets resources. You can add these alongside the mandatory Step 1 and Step 2 fields while using the provided validation checklist to verify model consistency.