Back to Details

sf-industry-cme-epc-model

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

sf-industry-cme-epc-model: CME EPC Product and Offer Modeling

sf-industry-cme-epc-model: CME EPC产品与优惠套餐建模

Expert Salesforce Industries CME EPC modeler for creating Product2-based catalog entries, assigning configurable attributes, and building offer bundles through Product Child Item relationships.
This skill is optimized for DataPack-style metadata authoring. Use the canonical template set in 
assets/
:
  • assets/product2-offer-template.json
  • assets/attribute-assignment-template.json
  • assets/product-child-item-template.json
  • assets/pricebook-entries-template.json
  • assets/price-list-entries-template.json
  • assets/object-field-attributes-template.json
  • assets/orchestration-scenarios-template.json
  • assets/decomposition-relationships-template.json
  • assets/compiled-attribute-overrides-template.json
  • assets/override-definitions-template.json
  • assets/parent-keys-template.json
Additional packaged examples are available under 
assets/examples/
with one folder per bundle/simple-offer sample. The root 
assets/
folder contains the canonical baseline template set for bundle authoring.
专业的Salesforce Industries CME EPC建模工具，用于创建基于Product2的目录条目、分配可配置属性，以及通过Product Child Item关联关系构建优惠套餐。
本技能针对DataPack风格的元数据编写做了优化，请使用
assets/
目录下的标准模板集：
  • assets/product2-offer-template.json
  • assets/attribute-assignment-template.json
  • assets/product-child-item-template.json
  • assets/pricebook-entries-template.json
  • assets/price-list-entries-template.json
  • assets/object-field-attributes-template.json
  • assets/orchestration-scenarios-template.json
  • assets/decomposition-relationships-template.json
  • assets/compiled-attribute-overrides-template.json
  • assets/override-definitions-template.json
  • assets/parent-keys-template.json
assets/examples/
目录下提供了打包好的额外示例，每个套餐/简单优惠示例对应一个文件夹。 根目录的
assets/
文件夹包含了套餐编写的标准基准模板集。

Quick Reference

快速参考

  • Primary object: 
    Product2
    (EPC product and offer records)
  • Attribute data: 
    %vlocity_namespace%__AttributeMetadata__c
    , 
    %vlocity_namespace%__AttributeDefaultValues__c
    , and 
    %vlocity_namespace%__AttributeAssignment__c
  • Offer bundle composition: 
    %vlocity_namespace%__ProductChildItem__c
  • Offer marker: 
    %vlocity_namespace%__SpecificationType__c = "Offer"
    and 
    %vlocity_namespace%__SpecificationSubType__c = "Bundle"
  • Companion bundle artifacts: pricebook entries, price list entries, object field attributes, orchestration scenarios, decomposition relationships, compiled attribute overrides, override definitions, and parent keys
Scoring: 120 points across 6 categories.
Thresholds: 
>= 95
Deploy-ready | 
70-94
Needs review | 
< 70
Block and fix.
  • 核心对象：
    Product2
    （EPC产品与优惠记录）
  • 属性数据：
    %vlocity_namespace%__AttributeMetadata__c
    、
    %vlocity_namespace%__AttributeDefaultValues__c
    和
    %vlocity_namespace%__AttributeAssignment__c
  • 优惠套餐结构：
    %vlocity_namespace%__ProductChildItem__c
  • 优惠标识：
    %vlocity_namespace%__SpecificationType__c = "Offer"
    且
    %vlocity_namespace%__SpecificationSubType__c = "Bundle"
  • 配套套餐产物：价格簿条目、价目表条目、对象字段属性、编排场景、分解关系、编译属性覆盖、覆盖定义以及父键
评分：6个维度总计120分。 阈值：
>= 95
可直接部署 | 
70-94
需要审核 | 
< 70
阻塞并修复

Asset Template Set

资产模板集

Use the root 
assets/
templates when creating a bundle payload:
  • product2-offer-template.json
  • attribute-assignment-template.json
  • product-child-item-template.json
  • pricebook-entries-template.json
  • price-list-entries-template.json
  • object-field-attributes-template.json
  • orchestration-scenarios-template.json
  • decomposition-relationships-template.json
  • compiled-attribute-overrides-template.json
  • override-definitions-template.json
  • parent-keys-template.json
For additional real-world variants, use the per-example folders under 
assets/examples/
.
创建套餐payload时请使用根目录
assets/
下的模板：
  • product2-offer-template.json
  • attribute-assignment-template.json
  • product-child-item-template.json
  • pricebook-entries-template.json
  • price-list-entries-template.json
  • object-field-attributes-template.json
  • orchestration-scenarios-template.json
  • decomposition-relationships-template.json
  • compiled-attribute-overrides-template.json
  • override-definitions-template.json
  • parent-keys-template.json
如需更多实际业务变体，请使用
assets/examples/
下的各示例文件夹。

Core Responsibilities

核心职责

  1. Product Creation: Create EPC Product2 records with consistent naming, lifecycle dates, status, and classification fields.
  2. Attribute Modeling: Define category-based attributes, defaults, valid value sets, display sequences, and required flags.
  3. Offer Bundle Modeling: Compose offers with child products using 
    %vlocity_namespace%__ProductChildItem__c
    records and clear quantity rules.
  4. Companion Metadata Generation: Generate and align all related bundle files (pricing, object field attributes, orchestration/decomposition, overrides, parent keys) from the same offer baseline.
  5. DataPack Consistency: Keep record source keys, global keys, lookup objects, and namespace fields internally consistent for deployment.
  1. 产品创建：创建EPC Product2记录，保持命名、生命周期日期、状态和分类字段的一致性。
  2. 属性建模：定义基于类别的属性、默认值、有效值集、显示顺序和必填标记。
  3. 优惠套餐建模：使用
    %vlocity_namespace%__ProductChildItem__c
    记录和清晰的数量规则，搭配子产品组合成优惠。
  4. 配套元数据生成：基于同一个优惠基准，生成并对齐所有相关的套餐文件（定价、对象字段属性、编排/分解、覆盖、父键）。
  5. DataPack一致性：保持记录源键、全局键、查找对象和命名空间字段的内部一致性，以便部署。

Invocation Rules (Mandatory)

调用规则（强制）

Route to this skill whenever the prompt intent matches either of these:
  1. Create a product bundle:
    • User asks to create/build/generate/model an EPC offer bundle.
    • User asks for Product2 offer setup with Product Child Items.
    • User asks to generate bundle DataPack JSON artifacts from templates/examples.
  2. Score or review an existing product bundle:
    • User asks to score/assess/validate/audit an existing EPC bundle.
    • User asks to apply the 120-point rubric to existing Product2/PCI/attribute payloads.
    • User asks for risk findings, quality gaps, or fix recommendations on bundle metadata.
Instruction priority: treat these two intents as direct triggers for 
sf-industry-cme-epc-model
, even if the prompt is brief and does not mention EPC by name.
当提示意图符合以下任意一种情况时，请路由到本技能：
  1. 创建产品套餐：
    • 用户要求创建/构建/生成/建模EPC优惠套餐。
    • 用户要求通过Product Child Item设置Product2优惠。
    • 用户要求从模板/示例生成套餐DataPack JSON产物。
  2. 评分或审核现有产品套餐：
    • 用户要求评分/评估/验证/审计现有EPC套餐。
    • 用户要求对现有Product2/PCI/属性payload应用120分评分规则。
    • 用户要求获取套餐元数据的风险发现、质量差距或修复建议。
指令优先级：将这两类意图视为
sf-industry-cme-epc-model
的直接触发条件，即使提示内容简短且未明确提及EPC也适用。

Workflow (Create/Review)

工作流程（创建/审核）

Phase 1: Identify Catalog Intent

阶段1：识别目录意图

Ask for:
  • Product type: spec product or offer bundle
  • Domain taxonomy: Family, Type/SubType, category path, and channel
  • Attribute requirements: required/optional, picklist values, default values
  • Bundle composition: child products, quantity constraints, optional vs required
  • Target org namespace model: 
    %vlocity_namespace%
    , 
    vlocity_cmt
    , or Core
询问以下信息：
  • 产品类型：规格产品或优惠套餐
  • 领域分类：系列、类型/子类型、类别路径和渠道
  • 属性要求：必填/选填、下拉选项值、默认值
  • 套餐构成：子产品、数量约束、可选vs必填
  • 目标组织命名空间模式：
    %vlocity_namespace%
    、
    vlocity_cmt
    或核心版

Phase 1A: Clarifying Questions for Complete Bundle (Mandatory)

阶段1A：完整套餐的澄清问题（强制）

Before generating a new offer bundle payload, ask clarifying questions until all required inputs are known.
Required clarification checklist:
  1. Offer identity
    • What is the offer name and 
      ProductCode
      ?
    • Is this net-new or an update to an existing Product2 offer?
  2. Catalog classification
    • What are Family, Type/SubType, and channel/sales context values?
    • Should 
      SpecificationType=Offer
      and 
      SpecificationSubType=Bundle
      be set now?
  3. Lifecycle and availability
    • What are 
      EffectiveDate
      and 
      SellingStartDate
      ?
    • Should 
      IsActive
      and 
      %vlocity_namespace%__IsOrderable__c
      be true at creation time?
  4. Child product composition
    • Which child products are included (name/code for each)?
    • For each child, what are required/optional semantics and sequence order?
  5. Quantity behavior per child
    • What are 
      MinQuantity
      , 
      MaxQuantity
      , and default 
      Quantity
      ?
    • Should 
      %vlocity_namespace%__MinMaxDefaultQty__c
      be enforced for each line?
  6. Attribute model
    • Which attributes are required vs optional?
    • What are valid values, defaults, display types, and display sequences?
  7. Pricing and companion artifacts
    • Should pricebook and price list entries be generated now?
    • Should orchestration/decomposition/override/parent-key files be included in the same request?
  8. Namespace and keying
    • Which namespace convention should be used (
      %vlocity_namespace%
      , 
      vlocity_cmt
      , or Core)?
    • Are there existing global keys/source keys to preserve?
If any required checklist item is unanswered, do not generate final bundle files yet; ask focused follow-up questions first.
生成新的优惠套餐payload之前，请先询问澄清问题，直到所有必填输入信息都明确为止。
必填澄清检查清单：
  1. 优惠标识
    • 优惠名称和
      ProductCode
      是什么？
    • 是全新创建还是更新现有Product2优惠？
  2. 目录分类
    • 系列、类型/子类型、渠道/销售场景值是什么？
    • 是否需要现在设置
      SpecificationType=Offer
      和
      SpecificationSubType=Bundle
      ？
  3. 生命周期与可用性 
    • EffectiveDate
      和
      SellingStartDate
      是什么？
    • 创建时是否需要将
      IsActive
      和
      %vlocity_namespace%__IsOrderable__c
      设为true？
  4. 子产品构成
    • 包含哪些子产品（每个的名称/编码）？
    • 每个子产品的必填/选填规则和排序顺序是什么？
  5. 每个子产品的数量规则 
    • MinQuantity
      、
      MaxQuantity
      和默认
      Quantity
      是多少？
    • 是否需要为每个行项强制执行
      %vlocity_namespace%__MinMaxDefaultQty__c
      ？
  6. 属性模型
    • 哪些属性是必填，哪些是选填？
    • 有效值、默认值、显示类型和显示顺序是什么？
  7. 定价与配套产物
    • 是否需要现在生成价格簿和价目表条目？
    • 是否需要在同一次请求中包含编排/分解/覆盖/父键文件？
  8. **命名空间与键值
    • 应该使用哪种命名空间约定（
      %vlocity_namespace%
      、
      vlocity_cmt
      或核心版）？
    • 是否有需要保留的现有全局键/源键？
如果有任何必填检查项未得到答复，请不要生成最终套餐文件，先提出针对性的跟进问题。

Phase 2: Build Product2 Backbone

阶段2：构建Product2基础

For every new EPC record, define:
  • Name
  • ProductCode
    (unique, stable, environment-agnostic)
  • %vlocity_namespace%__GlobalKey__c
    (stable UUID-style key)
  • %vlocity_namespace%__SpecificationType__c
    and 
    %vlocity_namespace%__SpecificationSubType__c
  • %vlocity_namespace%__Status__c
    and date fields (
    EffectiveDate
    , 
    SellingStartDate
    )
  • IsActive
    and 
    %vlocity_namespace%__IsOrderable__c
Use 
assets/product2-offer-template.json
as baseline structure.
为每个新的EPC记录定义：
  • Name
  • ProductCode
    （唯一、稳定、不依赖环境）
  • %vlocity_namespace%__GlobalKey__c
    （稳定的UUID风格键）
  • %vlocity_namespace%__SpecificationType__c
    和
    %vlocity_namespace%__SpecificationSubType__c
  • %vlocity_namespace%__Status__c
    和日期字段（
    EffectiveDate
    、
    SellingStartDate
    ）
  • IsActive
    和
    %vlocity_namespace%__IsOrderable__c
使用
assets/product2-offer-template.json
作为基准结构。

Phase 3: Add Attributes

阶段3：添加属性

When attributes are required:
  1. Populate 
    %vlocity_namespace%__AttributeMetadata__c
    category and 
    productAttributes
    records.
  2. Populate 
    %vlocity_namespace%__AttributeDefaultValues__c
    with attribute code to default value mapping.
  3. Create 
    %vlocity_namespace%__AttributeAssignment__c
    records with:
    • category linkage
    • attribute linkage
    • UI display type (dropdown, etc.)
    • valid values and default marker
Use 
assets/attribute-assignment-template.json
as the assignment baseline.
需要配置属性时：
  1. 填充
    %vlocity_namespace%__AttributeMetadata__c
    类别和
    productAttributes
    记录。
  2. 填充
    %vlocity_namespace%__AttributeDefaultValues__c
    ，包含属性编码到默认值的映射。
  3. 创建
    %vlocity_namespace%__AttributeAssignment__c
    记录，包含：
    • 类别关联
    • 属性关联
    • UI显示类型（下拉框等）
    • 有效值和默认标记
使用
assets/attribute-assignment-template.json
作为分配基准。

Phase 4: Build Offer Bundles

阶段4：构建优惠套餐

For offers:
  1. Keep parent 
    Product2
    record as offer (
    SpecificationType=Offer
    , 
    SpecificationSubType=Bundle
    ).
  2. Create root 
    %vlocity_namespace%__ProductChildItem__c
    row (
    IsRootProductChildItem=true
    ).
  3. Add child rows per component with:
    • parent and child references
    • sequence and line number
    • min/max/default quantity behavior (
      MinMaxDefaultQty
      , 
      MinQuantity
      , 
      MaxQuantity
      , 
      Quantity
      )
  4. Use override rows only when behavior differs from inherited/default behavior.
Use 
assets/product-child-item-template.json
for child relationship structure.
For complete bundle payloads, also align and include:
  • assets/pricebook-entries-template.json
  • assets/price-list-entries-template.json
  • assets/object-field-attributes-template.json
  • assets/orchestration-scenarios-template.json
  • assets/decomposition-relationships-template.json
  • assets/compiled-attribute-overrides-template.json
  • assets/override-definitions-template.json
  • assets/parent-keys-template.json
针对优惠场景：
  1. 保持父级
    Product2
    记录为优惠类型（
    SpecificationType=Offer
    、
    SpecificationSubType=Bundle
    ）。
  2. 创建根级
    %vlocity_namespace%__ProductChildItem__c
    行（
    IsRootProductChildItem=true
    ）。
  3. 为每个组件添加子行，包含：
    • 父级和子级引用
    • 顺序和行号
    • 最小/最大/默认数量规则（
      MinMaxDefaultQty
      、
      MinQuantity
      、
      MaxQuantity
      、
      Quantity
      ）
  4. 仅当行为与继承/默认行为不同时使用覆盖行。
使用
assets/product-child-item-template.json
作为子关联关系结构。
对于完整套餐payload，还需要对齐并包含：
  • assets/pricebook-entries-template.json
  • assets/price-list-entries-template.json
  • assets/object-field-attributes-template.json
  • assets/orchestration-scenarios-template.json
  • assets/decomposition-relationships-template.json
  • assets/compiled-attribute-overrides-template.json
  • assets/override-definitions-template.json
  • assets/parent-keys-template.json

Phase 4B: Generate Companion Metadata Files

阶段4B：生成配套元数据文件

When the user asks to generate a bundle, generate/update all companion files together as one coherent set:
  1. pricebook-entries-template.json
    and 
    price-list-entries-template.json
    • Keep Product2 GlobalKey/ProductCode references aligned with the parent offer.
  2. object-field-attributes-template.json
    • Keep object class references and field mappings aligned with the same offer model.
  3. orchestration-scenarios-template.json
    and 
    decomposition-relationships-template.json
    • Keep decomposition and orchestration artifacts consistent with bundle child items.
  4. compiled-attribute-overrides-template.json
    and 
    override-definitions-template.json
    • Keep override keys and references aligned with attribute metadata and assignments.
  5. parent-keys-template.json
    • Keep parent linkage values synchronized with generated artifact keys.
Mandatory rule: do not generate only a partial subset when a full bundle payload is requested unless the user explicitly asks for a limited file scope.
当用户要求生成套餐时，将所有配套文件作为一个连贯的集合一起生成/更新：
  1. pricebook-entries-template.json
    和
    price-list-entries-template.json
    • 保持Product2 GlobalKey/ProductCode引用与父优惠对齐。
  2. object-field-attributes-template.json
    • 保持对象类引用和字段映射与同一个优惠模型对齐。
  3. orchestration-scenarios-template.json
    和
    decomposition-relationships-template.json
    • 保持分解和编排产物与套餐子项一致。
  4. compiled-attribute-overrides-template.json
    和
    override-definitions-template.json
    • 保持覆盖键和引用与属性元数据和分配对齐。
  5. parent-keys-template.json
    • 保持父级链接值与生成的产物键同步。
强制规则：当用户请求完整套餐payload时，不要仅生成部分子集，除非用户明确要求限制文件范围。

Phase 5: Validate and Handoff

阶段5：验证与交付

Provide a completion block:
text
EPC Model Complete: <Name>
Type: <Spec Product|Offer Bundle>
ProductCode: <code>
Attributes: <count>
Bundle Children: <count>
Companion Metadata Files: <count generated>
Validation Score: <score>/120
Risks: <none|list>
提供完成块：
text
EPC Model Complete: <Name>
Type: <Spec Product|Offer Bundle>
ProductCode: <code>
Attributes: <count>
Bundle Children: <count>
Companion Metadata Files: <count generated>
Validation Score: <score>/120
Risks: <none|list>

Generation Guardrails (Mandatory)

生成护栏（强制）

If any anti-pattern appears, stop and ask for confirmation before proceeding.
Anti-patternWhy it failsRequired correction
Missing 
ProductCode
or unstable code values		Breaks quote/cart references and package diffsUse deterministic code convention
Hardcoded org-specific IDs in relationshipsFails across orgs/environmentsUse lookup objects with matching keys/global keys
Offer bundle without root PCI rowRuntime bundle traversal issuesAdd root 
%vlocity_namespace%__ProductChildItem__c
Attribute defaults not present in valid valuesInvalid cart configuration defaultsEnsure default exists in allowed value set
Duplicate display sequences in same attribute categoryUI ordering conflictEnforce unique and spaced sequence values
Offer marked active with incomplete child referencesBroken bundle at runtimeComplete and validate child link set before activation
Mixed naming styles (
snake_case
, ad hoc abbreviations)		Reduces maintainability and discoverabilityEnforce naming convention from references doc
如果出现任何反模式，请先停止并请求确认后再继续。
反模式问题原因所需修正
缺失
ProductCode
或编码值不稳定		破坏报价/购物车引用和包差异对比使用确定性的编码约定
关联关系中硬编码了特定组织的ID跨组织/环境部署失败使用带有匹配键/全局键的查找对象
优惠套餐没有根PCI行运行时套餐遍历异常添加根级
%vlocity_namespace%__ProductChildItem__c
属性默认值不在有效值范围内购物车配置默认值无效确保默认值存在于允许的值集中
同一属性类别中存在重复的显示顺序UI排序冲突强制使用唯一且留有间隔的顺序值
优惠标记为激活但子引用不完整运行时套餐损坏激活前完成并验证子链接集
混合命名风格（
snake_case
、临时缩写）		降低可维护性和可发现性执行参考文档中的命名约定

Scoring Model (120 Points)

评分模型（120分）

1) Catalog Identity and Naming (20)

1) 目录标识与命名（20分）

  • Product name clarity and uniqueness
  • ProductCode
    convention quality
  • Type/SubType/Family coherence
  • Stable keying (
    GlobalKey
    , source key integrity)
  • 产品名称清晰度和唯一性
  • ProductCode
    约定质量
  • 类型/子类型/系列一致性
  • 稳定键值（
    GlobalKey
    、源键完整性）

2) EPC Product Structure (20)

2) EPC产品结构（20分）

  • Required Product2 + EPC fields present
  • Lifecycle dates and status alignment
  • Orderable/active flags are coherent
  • Record type and classification consistency
  • 所需的Product2 + EPC字段齐全
  • 生命周期日期和状态对齐
  • 可订购/激活标志逻辑一致
  • 记录类型和分类一致性

3) Attribute Modeling (25)

3) 属性建模（25分）

  • Category and attribute grouping quality
  • Valid values + default alignment
  • Required/read-only/filterable semantics
  • Display sequence and UX consistency
  • 类别和属性分组质量
  • 有效值 + 默认值对齐
  • 必填/只读/可筛选语义正确
  • 显示顺序和UX一致性

4) Offer Bundle Composition (25)

4) 优惠套餐构成（25分）

  • Root PCI presence and correctness
  • Child references and sequencing integrity
  • Quantity constraints correctness
  • Optional/required semantics reflected in min/max/defaults
  • 根PCI存在且正确
  • 子引用和排序完整性
  • 数量约束正确
  • 可选/必填语义反映在最小/最大/默认值中

5) DataPack Integrity (15)

5) DataPack完整性（15分）

  • Namespace placeholder correctness
  • Lookup object key integrity
  • No environment-specific brittle fields
  • 命名空间占位符正确
  • 查找对象键完整性
  • 无环境相关的脆弱字段

6) Documentation and Handoff (15)

6) 文档与交付（15分）

  • Clear explanation of modeled intent
  • Testing checklist included
  • Risks and assumptions explicitly called out
  • 建模意图说明清晰
  • 包含测试检查清单
  • 明确标注风险和假设

CLI and Validation Commands

CLI和验证命令

bash
undefined
bash
undefined

Query candidate EPC products

查询候选EPC产品

sf data query -q "SELECT Id,Name,ProductCode,Family,IsActive FROM Product2 ORDER BY LastModifiedDate DESC" -o <org>
sf data query -q "SELECT Id,Name,ProductCode,Family,IsActive FROM Product2 ORDER BY LastModifiedDate DESC" -o <org>

Query Product Child Items for an offer

查询某个优惠的Product Child Items

sf data query -q "SELECT Id,Name,%vlocity_namespace%__ParentProductName__c,%vlocity_namespace%__ChildProductName__c,%vlocity_namespace%__MinMaxDefaultQty__c FROM %vlocity_namespace%__ProductChildItem__c WHERE %vlocity_namespace%__ParentProductName__c='<Offer Name>'" -o <org>
sf data query -q "SELECT Id,Name,%vlocity_namespace%__ParentProductName__c,%vlocity_namespace%__ChildProductName__c,%vlocity_namespace%__MinMaxDefaultQty__c FROM %vlocity_namespace%__ProductChildItem__c WHERE %vlocity_namespace%__ParentProductName__c='<Offer Name>'" -o <org>

Retrieve Product2 metadata package members (as applicable to project format)

检索Product2元数据包成员（适用于项目格式）

sf project retrieve start -m Product2:<DeveloperNameOrName> -o <org>
sf project retrieve start -m Product2:<DeveloperNameOrName> -o <org>

Validate deployment in dry-run mode

试运行模式验证部署

sf project deploy start -x manifest/package.xml --dry-run -o <org>

---
sf project deploy start -x manifest/package.xml --dry-run -o <org>

---

Sample Skill Invocation Commands

技能调用示例命令

Use these examples to invoke this skill from your agent/CLI workflow:
bash
undefined
使用以下示例从你的Agent/CLI工作流调用本技能：
bash
undefined

Create a new EPC offer bundle with full companion metadata

创建新的EPC优惠套餐，包含完整配套元数据

cursor-agent "Create a Product2 offer bundle named Business Internet Plus with ProductCode BIZ-INT-PLUS-01, 3 child products, and generate all companion DataPack JSON files from the assets templates."
cursor-agent "Create a Product2 offer bundle named Business Internet Plus with ProductCode BIZ-INT-PLUS-01, 3 child products, and generate all companion DataPack JSON files from the assets templates."

Add configurable attributes to an existing EPC Product2 record

为现有EPC Product2记录添加可配置属性

cursor-agent "Update Product2 Business Internet Essential with attribute metadata/defaults/assignments for Bandwidth, ContractTerm, and StaticIPCount, including valid values and defaults."
cursor-agent "Update Product2 Business Internet Essential with attribute metadata/defaults/assignments for Bandwidth, ContractTerm, and StaticIPCount, including valid values and defaults."

Build ProductChildItem relationships for an offer

为优惠构建ProductChildItem关联关系

cursor-agent "Create root and child %vlocity_namespace%__ProductChildItem__c records for offer Business Internet Essential VPL with min/max/default quantity rules."
cursor-agent "Create root and child %vlocity_namespace%__ProductChildItem__c records for offer Business Internet Essential VPL with min/max/default quantity rules."

Review an existing DataPack for EPC modeling quality

审查现有DataPack的EPC建模质量

cursor-agent "Review the Product2 bundle JSON files under skills/sf-industry-cme-epc-model/examples/business-internet-plus-bundle/, score against the 120-point rubric, and return risks plus required fixes."
cursor-agent "Review the Product2 bundle JSON files under skills/sf-industry-cme-epc-model/examples/business-internet-plus-bundle/, score against the 120-point rubric, and return risks plus required fixes."

Convert a spec product into a bundle-ready offer payload

将规格产品转换为可套餐化的优惠payload

cursor-agent "Transform Product2 Dedicated Fiber 1G from spec product to offer bundle (SpecificationType=Offer, SpecificationSubType=Bundle) and generate aligned PCI + pricing artifacts."

If your environment uses a different command wrapper, keep the quoted instruction text and replace `cursor-agent` with your local agent command.

---
cursor-agent "Transform Product2 Dedicated Fiber 1G from spec product to offer bundle (SpecificationType=Offer, SpecificationSubType=Bundle) and generate aligned PCI + pricing artifacts."

如果你的环境使用不同的命令包装器，请保留引号内的指令文本，将`cursor-agent`替换为你本地的Agent命令即可。

---

Cross-Skill Integration

跨技能集成

From SkillTo 
sf-industry-cme-epc-model
When
sf-industry-commoncore-omnistudio-analyze-> sf-industry-cme-epc-modelNeed current dependency and namespace inventory first
sf-metadata-> sf-industry-cme-epc-modelNeed object or field readiness before EPC modeling
sf-soql-> sf-industry-cme-epc-modelNeed existing catalog query analysis
From 
sf-industry-cme-epc-model
To SkillWhen
sf-industry-cme-epc-model-> sf-industry-commoncore-omniscriptConfigure guided selling UX using the modeled catalog
sf-industry-cme-epc-model-> sf-industry-commoncore-integration-procedureBuild server-side orchestration over product and pricing payloads
sf-industry-cme-epc-model-> sf-deployDeploy validated catalog metadata
来源技能目标
sf-industry-cme-epc-model
触发场景
sf-industry-commoncore-omnistudio-analyze-> sf-industry-cme-epc-model需要先获取当前依赖和命名空间清单
sf-metadata-> sf-industry-cme-epc-modelEPC建模前需要确认对象或字段就绪状态
sf-soql-> sf-industry-cme-epc-model需要现有目录查询分析
来源
sf-industry-cme-epc-model
目标技能触发场景
sf-industry-cme-epc-model-> sf-industry-commoncore-omniscript使用建模后的目录配置引导式销售UX
sf-industry-cme-epc-model-> sf-industry-commoncore-integration-procedure基于产品和定价payload构建服务端编排
sf-industry-cme-epc-model-> sf-deploy部署验证通过的目录元数据

External References

外部参考

Additional local references:
  • references/epc-field-guide.md
  • references/naming-conventions.md
额外本地参考：
  • references/epc-field-guide.md
  • references/naming-conventions.md

Notes

说明

  • This skill is intentionally DataPack-first and optimized for 
    vlocity/Product2/...
    artifact authoring.
  • Keep 
    %vlocity_namespace%
    placeholders intact in templates to preserve portability.
  • Prefer creating reusable spec products first, then assemble offers via child relationships.
  • 本技能默认优先使用DataPack模式，针对
    vlocity/Product2/...
    产物编写做了优化。
  • 请保留模板中的
    %vlocity_namespace%
    占位符以保证可移植性。
  • 建议优先创建可复用的规格产品，然后通过子关联关系组装优惠。

License

许可证

MIT License.
MIT许可证。