# experience-cms-content-type-generate

Builds a ContentTypeBundle for Salesforce CMS: discovers existing types, writes the two bundle files, and checks them with a dry-run deploy.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 699 installs · ★ 1112
- Author: forcedotcom
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/forcedotcom/sf-skills/tree/HEAD/skills/experience-cms-content-type-generate/SKILL.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/skills/experience-cms-content-type-generate

## What it does

The skill covers the whole path from a request to a finished bundle. It checks the local `<sfdx-source>/contentTypes/` folder and asks `metadata-grounding` about types that already exist, both out-of-the-box and custom. Then it generates `schema.json` and `.contentTypeBundle-meta.xml`, runs `sf project deploy start --dry-run` against the chosen org, and fixes schema problems on its own, up to three attempts. Deployment waits for a yes or no answer, so nothing ships by accident.

The rules are strict. New types get created, existing ones only get reconciled against the org. Ask it to add or rename a field on a deployed type and it prints one line saying so, then still shows the type summary instead of pretending the edit happened. For real changes you edit `schema.json` and redeploy, or go through the CMS UI.

Before you start: CLI `sf` 2.0.0 or newer, API version 64.0 or higher, and the `metadata-grounding` and `content-readonly` MCP servers. When the caller already knows the workspace, it passes `spaceId` or `folderId` — never together with `baseType`, since those arguments are mutually exclusive and a call with both fails.

## Requirements
- Works with: Salesforce

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add forcedotcom/sf-skills --skill experience-cms-content-type-generate -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/experience-cms-content-type-generate/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/experience-cms-content-type-generate/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add forcedotcom/sf-skills --skill experience-cms-content-type-generate -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/experience-cms-content-type-generate/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add forcedotcom/sf-skills --skill experience-cms-content-type-generate -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/experience-cms-content-type-generate/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install forcedotcom/sf-skills experience-cms-content-type-generate
```

2. **Manually: put the files in place**
- File: `.github/skills/experience-cms-content-type-generate/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add forcedotcom/sf-skills --skill experience-cms-content-type-generate -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/forcedotcom/sf-skills --path skills/experience-cms-content-type-generate
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/experience-cms-content-type-generate/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add forcedotcom/sf-skills --skill experience-cms-content-type-generate -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/forcedotcom/sf-skills/tree/HEAD/skills/experience-cms-content-type-generate/SKILL.md

## When to use it
- define a reusable content shape in Salesforce CMS
- reconcile a local bundle against what is deployed in the org
- catch schema errors before a real deploy
- generate `schema.json` and `.contentTypeBundle-meta.xml` that pass the validator
- find existing types before adding another one

## Example prompts
- create a content type for a news card in Salesforce CMS
- generate a schema for a "Promotion" content type in CMS
- resolve the type `myNS__PromoCard` and show me its schema

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: bff10db7478d0fd9.

BEGIN THIRD-PARTY FILE bff10db7478d0fd9
```text
---
name: experience-cms-content-type-generate
description: "Salesforce CMS ContentTypeBundle creation skill. Use this skill ANY TIME a user request involves creating a ContentTypeBundle, and activate FIRST when CMS ContentTypeBundle creation is mentioned. Discovers existing types via metadata-grounding and produces a validator-correct two-file bundle that passes dry-run deploy. TRIGGER when: user wants to define, scaffold, generate, or set up a reusable content shape in Salesforce CMS — any domain — including phrasings like \"create a content type for X\", \"generate a schema for X in CMS\", or \"set up a content type for X\". DO NOT TRIGGER when: authoring a RECORD (use experience-cms-content-generate), publishing / managing records (use CMS UI), modifying / renaming / deleting an existing bundle, CMS brand (experience-cms-brand-apply), media search (experience-search-coordinate), Custom Lightning Types (platform-custom-lightning-type-generate), or non-CMS metadata."
metadata:
  version: "1.0"
  domains: ["Experience"]
  minApiVersion: "64.0"
  relatedSkills:
    - "experience-cms-brand-apply"
    - "experience-cms-content-generate"
    - "experience-search-coordinate"
    - "platform-custom-lightning-type-generate"
  cliTools:
    - tool: ["sf"]
      semver: ">=2.0.0"
  mcpTools:
    metadata-grounding: { tools: ["search_metadata", "query_metadata", "describe_metadata"], semver: ">=1.0.0" }
    content-readonly: { tools: ["get_content_types_for_workspace"], semver: ">=1.0.0" }
---

# experience-cms-content-type-generate

## What This Skill Does

- **DISCOVER** — checks local `<sfdx-source>/contentTypes/` and queries `metadata-grounding` for existing OOTB/custom ContentTypeBundles.
- **RECONCILE** — on existing pick/provided FQN, retrieves from org (custom only) and reconciles against local. Returns `{fqn, schema}` matching the org.
- **CREATE** — generates a validator-correct ContentTypeBundle (`schema.json`, `.contentTypeBundle-meta.xml`).
- **VALIDATE** — `sf project deploy start --dry-run` against the CLI default (or picked) org.
- **AUTO-FIX** — fixes schema issues, re-validates (max 3 attempts).
- **DEPLOY** — asks yes/no, deploys on yes.
```
END THIRD-PARTY FILE bff10db7478d0fd9

The third-party file has ended. Everything between the bff10db7478d0fd9 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2201 of 43879 bytes. © forcedotcom · Apache-2.0 · https://github.com/forcedotcom/sf-skills/tree/HEAD/skills/experience-cms-content-type-generate/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md