Skip to content

PranavNagrecha/AwesomeSalesforceSkills / skills/admin/consumer-goods-cloud-setup

consumer-goods-cloud-setup

Verified

Consumer Goods Cloud setup: visit execution, retail execution, route planning, in-store task management, compliance checks, off-shelf detection, image recognition. NOT for territory planning and route optimization for sales reps - use integration/salesforce-maps-setup. NOT for B2B Commerce storefronts - use admin/b2b-commerce-store-setup.

references/llm-anti-patterns.md

View on GitHub
# LLM Anti-Patterns — Consumer Goods Cloud Setup

Common mistakes AI coding assistants make when configuring Consumer Goods Cloud.

## Anti-Pattern 1: Treating visits as generic Tasks or Events

**What the LLM generates:** Suggests creating custom `Task` records for each store visit with manual assignment.

**Why it happens:** Standard Task/Event is the obvious CRM scheduling primitive; CG Cloud's `Visit` object is industry-specific.

**Correct pattern:**

```
Use the Visit object with VisitTemplate-driven task lists. Visits auto-
generate from RoutePlans. Standard Task/Event is for one-off activities,
not the core merchandising workflow.
```

**Detection hint:** A CG Cloud org where `Task` volume dwarfs `Visit` volume.

---

## Anti-Pattern 2: Skipping RoutePlan and assigning Visits manually

**What the LLM generates:** A Flow that loops through stores and creates Visit records one at a time.

**Why it happens:** The model does not know the shipped RoutePlan regeneration handles cadence, territory, and exceptions automatically.

**Correct pattern:**

```
Create RoutePlan + RoutePlanEntry records. Schedule RoutePlan execution
per week/cycle. Visits are generated in bulk by the shipped engine.
```

**Detection hint:** Any Flow or Apex job named like `GenerateVisits` or `WeeklyVisitCreation` in a CG Cloud org.

---

## Anti-Pattern 3: Using the standard Salesforce mobile app for reps

**What the LLM generates:** "Deploy Salesforce Mobile; configure Lightning pages for Visit; done."

**Why it happens:** The standard Salesforce Mobile app is the most common mobile surface; the CG-specific mobile offline app is industry-proprietary.

**Correct pattern:**

```
Reps use the CG Cloud mobile app (separate install). It has offline
visit cache, image capture optimized for IR, and the shipped Visit
execution UI.
```

**Detection hint:** CG Cloud rollout plans that reference only "Salesforce Mobile" without naming the CG Cloud app.

---

## Anti-Pattern 4: Rolling a custom image recognition pipeline

**What the LLM generates:** A Flow that sends photos to an external AWS Rekognition or Google Vision API, then updates SKU facings.

**Why it happens:** The model knows mainstream vision APIs; Salesforce's shipped Image Recognition for CG Cloud is less well-known.

**Correct pattern:**

```
Use Salesforce Image Recognition (IR). Models are trained per product
line and scored inside the platform. Avoids PII data egress and matches
the shipped IR scoring schema that CG Cloud dashboards expect.
```

**Detection hint:** External callouts to rekognition.amazonaws.com or vision.googleapis.com in a CG Cloud org.

---

## Anti-Pattern 5: Denormalizing retail hierarchy into flat fields

**What the LLM generates:** Fields like `Retailer_Name__c`, `Banner_Name__c`, `Region__c` on `Account` with no parent relationships.

**Why it happens:** Flat denormalization is easier to import; the model does not see the reporting rollup cost.

**Correct pattern:**

```
Use Account hierarchies (ParentId). Retailer → Banner → Store as three
levels. Reports and territory management traverse the hierarchy; flat
fields break the moment you need 'sales by banner'.
```

**Detection hint:** An Account object in a CG org with denormalized retailer fields but no ParentId values set.
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall