Skill 詳細
experience-cms-brand-apply
Brand application only within Salesforce CMS; does not create brand strategy.
使用前に確認
自動レビューは関連性のみを確認し、安全性や推奨を保証しません。使用前に出典の説明を読んでください。
SKILL.md
これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。
---
name: experience-cms-brand-apply
description: "Extracts, retrieves, and applies CMS brand guidelines (voice, tone, style, colors, typography) to generated content. Use this skill ANY TIME a user request involves branding, brand voice, brand tone, brand guidelines, brand identity, brand styling, or applying a brand to content. Triggers for requests like \"apply my brand\", \"use our brand voice\", \"match our brand guidelines\", \"find my brand\", \"search for brand\", \"get brand instructions\", \"apply brand tone\". Handles the full workflow: searching for brands in Salesforce CMS, extracting brand instructions, and applying brand voice/tone/guidelines to generated content. Does not apply to media/image search (use experience-content-media-search skill), logo search, or creating new brand definitions."
compatibility: "Requires get_brand_instructions and/or search_media_cms_channels MCP tools"
metadata:
version: "1.0"
---
# Applying CMS Brand
Universal skill for searching, extracting, and applying CMS brand guidelines to generated content.
## Scope
**This skill is for APPLYING existing brand guidelines from Salesforce CMS to content you generate.**
**Use this skill when the user wants to:**
- Apply their brand voice/tone to generated content
- Find and use brand guidelines stored in Salesforce CMS
- Search for an existing brand in their org
- Get brand instructions for content generation
- Ensure generated content matches their brand identity
- Apply brand styling, tone, or voice to a page, component, or app
**DO NOT use this skill when the user wants to:**
- Search for images or media (use experience-content-media-search skill)
- Create a new brand from scratch
- Edit brand definitions in CMS
- Generate logos or visual brand assets
## Before You Start
**CRITICAL: You must retrieve brand instructions BEFORE applying any brand.**
When a user requests branded content:
1. **Search for available brands** (if brand is not already identified)
2. **Extract brand instructions** for the selected brand
3. **Apply brand guidelines** to all content you generate
**Never generate content first and retrofit branding later.** Brand instructions must inform content generation from the start.
## Workflow Overview
Copy this checklist and track your progress:
```text
CMS Branding Progress:
- [ ] Step 1: Determine if brand is already identified or needs search
- [ ] Step 2: Search for brands (if needed) and present options to user
- [ ] Step 3: Extract brand instructions for the selected brand
```
## Step 1: Determine Brand Context
Check if the user has already specified which brand to use:
**Brand is known** (user named it, or only one brand exists):
- Skip to Step 3 (Extract Brand Instructions)
**Brand is unknown** (user says "apply my brand" without specifying which):
- Proceed to Step 2 (Search for Brands)
## Step 2: Search for Brands
**Tool:** `search_media_cms_channels`
Brands are stored as CMS content of type `sfdc_cms__brand`. Search for them by
querying the CMS channels with the brand content type.
> **Note:** Brand content search (`contentTypeFqn=sfdc_cms__brand`) is explicitly
> excluded from the `experience-content-media-search` skill's scope. Calling
> `search_media_cms_channels` directly here is correct and intentional — do not
> route brand search through `experience-content-media-search`.
**Process:**
1. **Determine search query** — Use the user's keyword. Brand search matches on
brand title and description.
2. **Build the request** with the fixed brand-search input contract:
```json
{
"inputs": [{
"searchKeyword": "keyword",
"searchLanguage": "<detected_language>",
"channelType": "PublicUnauthenticated",
"contentTypeFqn": "sfdc_cms__brand",
"pageOffset": 0,
"searchLimit": 25
}]
}
```
Field rules:
- `searchKeyword` — the user's keyword input
- `searchLanguage` — auto-detect from the user's input; if unsure, use `en_US`
- `channelType` — always `PublicUnautheGitHub で全文を読む (外部ページ)