PranavNagrecha
- 1.1k skills
- 0 followers
- 15 repo stars
- 2 weeks ago last updated
- ▌ Data Loader Picklist Validation Pre Load · pranavnagrecha bundleWhen and how to pre-validate a CSV against Salesforce picklist rules and record-type assignments BEFORE running a Data Loader / Bulk API insert or upsert — restricted picklists, record-type-scoped values, inactive values, Global Value Sets, dependent picklists, multi-select delimiters, API name vs label, and the 255-char per-value limit. NOT for mapping CSV headers to field API names — use data/data-loader-csv-column-mapping. NOT for cleaning up bad picklist values already in the org — use admin/picklist-field-integrity-issues.
- ▌ Duplicate Rule Person Account Edge Cases · pranavnagrecha bundleDuplicate Rules and Matching Rules for Person Accounts — PA shape, lead convert, PII. Triggers: person account duplicate rule, PA matching, IsPersonAccount filter. NOT for general B2B duplicate management — use admin/duplicate-management. NOT for Person Account enablement — use data/person-accounts.
- ▌ Callout Limits And Async Patterns · pranavnagrecha bundleUse when designing or troubleshooting Apex callouts that approach governor limits: choosing between synchronous callouts, @future, Queueable, Continuation, or async chaining strategies. NOT for the @future rules themselves — primitive-only parameters, no chaining, the 50-per-transaction cap — use apex/apex-future-method-patterns. NOT for building the HttpRequest, handling the response, or mocking the callout in tests — use apex/callouts-and-http-integrations. NOT for configuring the Named Credential or External Credential itself — use integration/named-credentials-setup.
- ▌ Data Cloud Activation Development · pranavnagrecha bundleUse this skill when building developer-driven Data Cloud activation surfaces: webhook Data Action Targets with HMAC-SHA256 signing, Salesforce Platform Event data actions, Data Cloud-Triggered Flows on DMO insert. NOT for standard admin-level Activation Targets (SFTP, ad platform segment publishing) — use admin/data-cloud-segmentation. NOT for receiving webhooks into Salesforce — use integration/webhook-inbound-patterns.
- ▌ Omnistudio Error Handling Patterns · pranavnagrecha bundleUse when designing fault behavior across Integration Procedures, DataRaptors, OmniScripts, and FlexCards — error routing, user-facing messaging, retry semantics, and idempotency. Triggers: 'omnistudio error', 'integration procedure fault'. NOT for general Apex exception design or Flow fault paths — use data/omnistudio-metadata-management.
- ▌ Managed Package Installation And Upgrade · pranavnagrecha bundleUse when a subscriber admin is installing, upgrading, or rolling back a managed package (1GP or 2GP) sourced from AppExchange or a private install URL — covers pre-install evaluation, sandbox dry runs, license and dependency checks, the install/upgrade audit trail, post-install configuration the package's InstallHandler cannot perform, and uninstall fallback. NOT for building managed packages as an ISV (use devops/managed-package-development), unlocked-package development (use devops/unlocked-package-development), or AppExchange listing setup.
- ▌ Data Cloud Grounding For Agentforce · pranavnagrecha bundleGrounding an Agentforce agent with Data Cloud retrievers, DMO selection, chunking, and freshness windows. Triggers: agent grounding, retriever, DMO, data graph, RAG, vector index, citations. NOT for building or tuning the vector index itself — chunk size, embedding model, Query API — use agentforce/data-cloud-vector-search-dev. NOT for the end-to-end Knowledge-article RAG build — use agentforce/rag-patterns-in-salesforce. NOT for Data Cloud ingestion pipelines — use data/data-cloud-data-streams. NOT for identity resolution ruleset tuning — use admin/data-cloud-identity-resolution.
- ▌ Subscription Management Architecture · pranavnagrecha bundleUse when designing or evaluating Salesforce CPQ subscription lifecycle architecture: amendment flow, renewal automation, co-termination design, or billing integration at the contract level. Trigger keywords: amendment architecture, renewal automation, co-termination design, subscription ledger, large-scale amendment, billing schedule, swap pattern, SBQQ__Subscription__c. NOT for configuring amendment and renewal quotes - use admin/contract-and-renewal-management. NOT for bundle design or pricing-engine performance - use architect/cpq-architecture-patterns.
- ▌ Source Tracking And Conflict Resolution · pranavnagrecha bundleUse when diagnosing and resolving SFDX source-tracking conflicts between a local project and a Salesforce org. Trigger keywords: source tracking, conflict, --force-overwrite, --ignore-conflicts, maxRevision.json, sf project retrieve, source:status. NOT for Git merge conflicts, DevOps Center pipeline conflicts, or change-set deployments — use devops/metadata-api-retrieve-deploy.
- ▌ Event Driven Architecture Patterns · pranavnagrecha bundleUse when choosing between Salesforce event-driven mechanisms — Platform Events, Change Data Capture (CDC), Streaming API (PushTopic), and Outbound Messages — to determine which pattern fits a given integration requirement. Triggers: platform events vs CDC, choose event pattern, streaming API vs platform events. NOT for implementing a single pattern — use integration/platform-events-integration, integration/change-data-capture-integration, or integration/streaming-api-and-pushtopic.
- ▌ Slack Salesforce Integration Setup · pranavnagrecha bundleUse this skill when setting up or troubleshooting the Salesforce for Slack managed app — including connecting a Salesforce org to a Slack workspace, configuring the three-party admin handshake, linking Slack channels. NOT for building custom Slack apps or Slack bots (separate development platform), not fo — use integration/slack-workflow-builder.
- ▌ Omnistudio Field Mapping Governance · pranavnagrecha bundleGovern DataRaptor field mappings to prevent runtime errors when source metadata changes: naming, versioning, and dependency tracking. NOT for DataRaptor authoring fundamentals — use data/omnistudio-metadata-management.
- ▌ Omnistudio Lwc Omniscript Migration · pranavnagrecha bundleMigrate classic Visualforce-based OmniScripts to LWC-based runtime with feature parity and regression testing. NOT for new OmniScript design — use omnistudio/omnistudio-lwc-integration.
- ▌ Apex Stripinaccessible And Fls Enforcement · pranavnagrecha bundleUse Security.stripInaccessible to enforce CRUD/FLS on user-supplied records before DML, and to scrub query results before returning them to clients. Covers AccessType.READABLE/CREATABLE/UPDATABLE/UPSERTABLE, the SObjectAccessDecision API, and when to prefer WITH USER_MODE on the SOQL itself. NOT for the with sharing / without sharing keyword choice — use apex/apex-with-without-sharing-decision. NOT for SOQL injection review — use apex/soql-security.
- ▌ AI Agent Org Integration Architecture · pranavnagrecha bundleUse this skill to design and review the architecture for integrating external AI agents (Claude, ChatGPT, LangChain, custom LLM pipelines) with a Salesforce org — covering integration pattern selection (MCP vs. REST vs. Platform Events), auth model design, data exposure scope, org governor limit planning, and Well-Architected tradeoffs. Trigger keywords: AI agent Salesforce integration, agent-to-org architecture, LLM Salesforce access pattern, external AI org connectivity, agentic system org design. NOT for building an Agentforce agent in-org — use agentforce/agentforce-agent-creation. NOT for implementation-level Apex tool code — use agentforce/mcp-tool-definition-apex. NOT for ETL or data pipeline design — use agentforce/sf-to-llm-data-pipelines.
- ▌ Experience Cloud Integration Patterns · pranavnagrecha bundleUse when designing or reviewing integrations between an Experience Cloud site and external systems — SSO identity providers, third-party widgets, external content sources, and behavioral data platforms. Triggers: 'integrate SSO with Experience Cloud site', 'embed third-party chat widget in LWR site', 'connect Data Cloud to Experience Cloud', 'inject Google Tag Manager into Experience Cloud', 'configure SAML for community login', 'allow external IdP login on portal'. NOT for internal Salesforce-to-Salesforce integration, NOT for Apex callout mechanics within Experience Cloud pages, NOT for multi-IdP SSO login-page routing (use lwc/experience-cloud-multi-idp-sso).
- ▌ Salesforce Connect External Objects · pranavnagrecha bundleUse when deciding whether Salesforce Connect and External Objects are the right fit for external data access, or when reviewing OData, cross-org, and custom adapter patterns, query limitations, and latency tradeoffs. Triggers: 'Salesforce Connect', 'External Objects', '__x', 'OData adapter', 'custom adapter'. NOT for the External Object configuration walkthrough and the full inventory of what they cannot do — triggers, validation rules, record-triggered flows, roll-ups, indirect lookup keys — use data/data-virtualization-patterns. NOT for keeping high-volume history inside Salesforce instead — use data/external-data-and-big-objects.
- ▌ Visualforce Security And Modernization · pranavnagrecha bundleUse when hardening or modernizing legacy Visualforce pages — covers the platform CSRF token model and when disabling it is a security regression, view state encryption guarantees and the 170 KB ceiling, FLS/CRUD enforcement gaps on `<apex:outputField>` and on getters that return sObjects, `<apex:includeScript>` interaction with the org Content Security Policy, hosting LWC inside a VF page via `lightning:container` / `lightning-out`, and the retire-vs-harden-vs-leave-alone decision for an inventory of legacy pages. Triggers: 'should I rewrite this Visualforce page in LWC', 'CSRF protection disabled on Visualforce page is that safe', 'community user sees a field they should not on a Visualforce page', 'view state encryption is that enough for sensitive data', 'how do I host an LWC inside a Visualforce page', 'apex:dynamicComponent and apex:actionFunction safe to keep'. NOT for greenfield Visualforce architecture (use apex/visualforce-fundamentals — controller types, view state pattern selection, PDF rendering);
- ▌ Apex Trigger Bypass And Killswitch Patterns · pranavnagrecha bundleRuntime mechanisms to disable Apex triggers without commenting out code: Custom Metadata kill switches via Trigger_Setting__mdt, Custom Permission gates via FeatureManagement.checkPermission, Hierarchy Custom Settings, and TriggerControl static-state bypass for nested operations. NOT for a handler re-entering itself — use apex/recursive-trigger-prevention. NOT for gating a business feature — use apex/feature-flags-and-kill-switches.
- ▌ Cross Object Formula And Rollup Performance · pranavnagrecha bundleUse when diagnosing or preventing performance problems caused by cross-object formula spanning relationships and roll-up summary field recalculations — especially in LDV orgs. Triggers: 'roll-up summary timing stale in trigger', 'Maximum 15 object references error', 'rollup recalculation timeout on large child set'. NOT for formula syntax authoring (use admin/formula-fields), formula compile-size limits (use apex/formula-field-performance-and-limits), or general governor-limit troubleshooting.
- ▌ Cloud Specific Deployment Architecture · pranavnagrecha bundleDeployment architecture quirks per Salesforce cloud: Industries (OmniStudio), Marketing Cloud (MC packages), Commerce Cloud, Data Cloud, Agentforce. What ships via metadata API, what ships via cloud-specific tools, ordering, dependencies. NOT for building the OmniStudio DataPack pipeline itself — use omnistudio/omnistudio-ci-cd-patterns. NOT for the generic CI/CD pipeline, branch strategy or Copado-vs-Gearset choice — use architect/deployment-automation-architecture.
- ▌ Salesforce To Salesforce Integration · pranavnagrecha bundleUse this skill to implement Salesforce-to-Salesforce integration patterns — covering the native S2S feature, API-based cross-org sync, Platform Event bridging, and Salesforce Connect Cross-Org adapter. Trigger keywords: Salesforce to Salesforce integration, cross-org data sharing, S2S feature, cross-org Platform Events, Salesforce Connect cross-org. NOT for multi-org strategy or architecture decisions (use architect/multi-org-strategy), single-org data sharing, or external (non-Salesforce) system integration.
- ▌ Soql String Escaping And Reserved Characters · pranavnagrecha bundleUse when a SOQL single-quoted string literal contains a character that must be escaped: an apostrophe in a name (O'Brien, Bob's BBQ), a backslash, a tab/newline/other control character, a Unicode character via \uXXXX, or a literal LIKE wildcard (\_ or \%). Covers the backslash escape character, the full quoted-string escape-sequence table, the two reserved characters (single quote and backslash) that must always be escaped, the LIKE-only \_ / \% wildcard escapes, the hard-error rule for any other backslash use, and String.escapeSingleQuotes on the Apex side. NOT for binding untrusted input into dynamic SOQL — use apex/apex-dynamic-soql-binding-safety. NOT for SOQL-injection review or CRUD/FLS enforcement — use apex/soql-security. NOT for Apex String/regex methods — use apex/apex-string-and-regex.
- ▌ Vlocity To Native Omnistudio Migration · pranavnagrecha bundleUse when migrating an org from the Vlocity managed package (vlocity_ins, vlocity_cmt, vlocity_ps) to native OmniStudio. Trigger keywords: Vlocity to OmniStudio migration, namespace migration, vlocity_ins to omnistudio. NOT for greenfield OmniStudio setup or migrating between OmniStudio-native orgs — use omnistudio/omnistudio-deployment-datapacks.
- ▌ Omnistudio Asynchronous Data Operations · pranavnagrecha bundleUse Integration Procedures queues, DataRaptor Chain, and Remote Actions with async patterns for long-running OmniStudio flows. NOT for simple DataRaptor reads — use omnistudio/dataraptor-patterns.
- ▌ Integration Procedure Cacheable Patterns · pranavnagrecha bundleUse when designing Integration Procedures (IPs) with platform cache to cut latency and callout load. Covers Cache Block boundary, cache key design, per-user vs org-wide partitions, invalidation on data changes, and safe fallback on cache miss. NOT for general IP authoring or LWC client-side caching — use omnistudio/integration-procedures.
- ▌ Agentforce Production Readiness Checklist · pranavnagrecha bundleAn Agentforce agent is moving from build or sandbox to live end-user traffic and the team needs a comprehensive readiness gate: coverage testing, Trust Layer config, guardrails, cost telemetry, observability, rate limits, permissions, rollout strategy, rollback plan, performance benchmarks. Triggers: 'we want to ship our Agentforce agent next week', 'pre-prod readiness review for our Service Agent', 'what do we need before turning the agent on for real customers', 'agent went live and is hallucinating, what should we have caught', 'cost monitoring for our internal sales agent', 'rollout strategy from internal pilot to GA'. NOT for the lighter five-block activation sign-off artifact — use agentforce/agent-deployment-checklist. NOT for authoring the guardrails themselves — use agentforce/agentforce-guardrails. NOT for building the test harness — use agentforce/agentforce-eval-harness. NOT for Trust Layer feature setup in isolation — use agentforce/einstein-trust-layer.
- ▌ Scheduled Apex Failure Detection And Monitoring · pranavnagrecha bundleUse when nightly batch / scheduled Apex jobs are failing without anyone noticing — covers why uncaught exceptions in `execute()` go to the debug log instead of email, how to query `AsyncApexJob` for `Status`, `NumberOfErrors`, and `ExtendedStatus`, when to implement `Database.RaisesPlatformEvents` so the platform publishes `BatchApexErrorEvent` on uncaught failures, how to subscribe to that event with an Apex trigger and notify operators, and how to layer a custom watcher schedule on top so silent-failure modes (job that never started, scheduled class deleted, queue stuck on `Queued`) still surface. Triggers: 'nightly batch failed at 2am with no notification', 'how do we know if a scheduled apex job is failing', 'BatchApexErrorEvent vs custom retry logic', 'Setup Apex Jobs only shows last 7 days, where else can I look', 'job is stuck in queued status nobody noticed for a week'. NOT for general Apex exception handling patterns (use apex/exception-handling), NOT for Batch Apex authoring or chunking strategy (us
- ▌ Multi Currency And Advanced Currency Management · pranavnagrecha bundleUse when designing or reviewing Salesforce multi-currency behavior, especially irreversible activation, `CurrencyIsoCode`, `convertCurrency()`, dated exchange rates, and Advanced Currency Management tradeoffs. Triggers: 'multi currency', 'advanced currency management', 'CurrencyIsoCode', 'dated exchange rate', 'convertCurrency'. NOT for what convertCurrency() allows in WHERE/ORDER BY or querying CurrencyType and DatedConversionRate — use data/currency-management-patterns. NOT for wrong converted amounts in Sales Cloud reports and roll-ups — use architect/multi-currency-sales-architecture.
- ▌ Analytics Dataflow Development · pranavnagrecha bundleUse this skill when building, debugging, or optimizing CRM Analytics dataflows — defining node types (sfdcDigest, Append, Augment, computeExpression, computeRelative, Flatten, dim2mea, sfdcRegister), scheduling runs, handling run failures, and tuning performance. NOT for doing the same transformation in a Data Prep recipe — use admin/analytics-recipe-design. NOT for dataset field types, refresh schedules, or row limits — use admin/analytics-dataset-management.
- ▌ Approval Process Apex Patterns · pranavnagrecha bundleProgrammatically driving Salesforce Approval Processes from Apex — `Approval.process(ProcessSubmitRequest)` to submit, `ProcessWorkitemRequest` to approve / reject / reassign, recall semantics, querying `ProcessInstance` and `ProcessInstanceWorkitem` to find pending approvals, and the bulk-submit / bulk-action error-row handling. Covers when to use Apex-driven approval (system-initiated submission, batch approvals, custom UIs) vs leaving the platform's standard buttons in place. NOT for the Approval Process metadata definition itself (that's admin / declarative — see admin/approval-processes), NOT for Flow-based approvals (use flow/flow-orchestration-patterns).
- ▌ Care Coordination Requirements · pranavnagrecha bundleUse this skill when mapping care coordination process requirements for Health Cloud: designing care team workflows, transition of care handoffs, social determinants of health (SDOH) barrier tracking, and care gap identification. NOT for building care plan templates, problems, and goals — use admin/care-plan-configuration. NOT for referral routing and provider networks — use admin/referral-management-health.
- ▌ Change Management And Training · pranavnagrecha bundleUse this skill when planning user adoption, structuring Salesforce training materials, drafting release communications, or running a change impact assessment for a Salesforce rollout or update. Triggers: user adoption plan, training materials, release announcement, change impact, go-live communication. NOT for org deployment mechanics or sandbox promotion — use admin/change-management-and-deployment. NOT for adoption of an Agentforce or Einstein AI feature — use admin/ai-adoption-change-management.
- ▌ Data Cloud Calculated Insights · pranavnagrecha bundleCreate, design, and maintain Calculated Insights in Data Cloud: SQL authoring, dimension and measure definition, scheduling, streaming insights. Trigger keywords: calculated insight, CI SQL, insight measure, insight dimension, streaming insight, insight schedule, Data Cloud metric, insight refresh. NOT for segment filters, audiences and activation - use admin/data-cloud-segmentation. NOT for ingestion, DLO to DMO mapping and identity resolution - use data/data-cloud-data-streams.
- ▌ Data Cloud Identity Resolution · pranavnagrecha bundleUse this skill when configuring or troubleshooting Data Cloud identity resolution rulesets — matching rules, reconciliation rules, unified profiles, and cross-device identity linking. Trigger keywords: identity resolution ruleset, unified individual, match rule, reconciliation rule, unified profile, cross-device identity, Data Cloud deduplication, cluster creation. NOT for CRM duplicate and matching rules — use admin/duplicate-management. NOT for overall Data Cloud layer and activation design — use architect/data-cloud-architecture.
- ▌ Industries Public Sector Setup · pranavnagrecha bundlePublic Sector Solutions (PSS) setup: licensing, permits, inspections, benefits, case management for government, citizen portals, and grant management. NOT for standard Service Cloud cases — use admin/case-management-setup. NOT for a plain portal site — use admin/experience-cloud-site-setup.
- ▌ Journey Builder Administration · pranavnagrecha bundleUse when setting up, configuring, or troubleshooting Marketing Cloud Journey Builder — including entry sources, activities, decision splits, wait activities, goals, exit criteria, journey versions, test mode, or journey analytics. Triggers: 'journey builder setup', 'entry source configuration', 'decision split not routing', 'exit criteria not removing contacts', 'goal not tracking conversion', 'journey version publishing', 'journey re-entry settings', 'wait activity date field'. NOT for coding a custom activity or entry source — use apex/marketing-cloud-custom-activities. NOT for business units and sender profiles — use admin/marketing-cloud-engagement-setup.
- ▌ Knowledge Classic To Lightning · pranavnagrecha bundleMigrating Classic Knowledge (KnowledgeArticleVersion / Article Types) to Lightning Knowledge (Knowledge__kav with record types): article-type-to-record-type mapping, multi-language translation preservation, data category re-architecture, file attachment porting, version and publication-state retention, channel visibility translation, and downstream Case Feed / Community / Bot rewiring. NOT for new Lightning Knowledge setup or editorial publishing workflow design (use admin/knowledge-base-administration).
- ▌ Lead Management And Conversion · pranavnagrecha bundleConfiguring Salesforce lead management and conversion in Setup: lead settings, web-to-lead, conversion field mapping, lead queues, auto-response rules, lead processes. Trigger keywords: web-to-lead, lead conversion, lead field mapping, lead settings, lead process, lead queue, lead auto-response. NOT for Apex that controls what conversion creates - use apex/lead-conversion-customization. NOT for lead assignment rule logic - use admin/assignment-rules. NOT for duplicate rule configuration - use admin/duplicate-management.
- ▌ Lightning App Builder Advanced · pranavnagrecha bundleAdvanced Lightning App Builder usage: component visibility filters, custom page templates, Dynamic Forms, Dynamic Actions, page performance optimization, LWC targetConfig constraints on record pages. Use when building complex record pages or custom app templates. NOT for Dynamic Forms basics — use admin/dynamic-forms-and-actions. NOT for exposing an LWC via js-meta.xml targets — use lwc/lwc-app-builder-config.
- ▌ List Views And Compact Layouts · pranavnagrecha bundleUse when designing or reviewing list views, compact layouts, highlights panels, and search-result presentation so users can scan, find, and act on records quickly across desktop and mobile. Triggers: 'too many list views', 'compact layout not showing the right fields', 'search layouts vs list views', 'mobile highlights panel'. NOT for page layouts or record types — use admin/record-types-and-page-layouts. NOT for Dynamic Forms — use admin/dynamic-forms-and-actions.
- ▌ Lookup And Relationship Design · pranavnagrecha bundleDesigning Lookup vs Master-Detail vs Hierarchical vs External relationships: cascade delete, roll-up summaries, ownership, sharing implications, polymorphic lookups, junction objects, relationship depth limits. NOT for restricting which records a lookup can pick — use admin/lookup-filter-cross-object-patterns. NOT for a roll-up across a plain lookup — use data/roll-up-summary-alternatives.
- ▌ Multi Language And Translation · pranavnagrecha bundleConfigure Salesforce Translation Workbench and translate custom labels, picklist values, field labels, page layout sections, or the Experience Cloud language switcher. Triggers: 'how to add a language to Salesforce', 'translate custom labels', 'Translation Workbench setup', 'picklist value translation', 'RTL language support'. NOT for creating the Custom Label records or referencing them from Apex/LWC — use admin/custom-label-management. NOT for locale formatting and RTL layout inside a component — use lwc/lwc-internationalization.
- ▌ Omnistudio Admin Configuration · pranavnagrecha bundleUse when configuring OmniStudio at the org level: enabling Standard Runtime, selecting the Runtime Namespace, assigning Permission Set Licenses, toggling feature settings, and granting Experience Cloud community access. Trigger keywords: OmniStudio Settings, Standard OmniStudio Runtime, managed package runtime, runtime namespace, OmniStudio Permission Set, OmniStudio PSL. NOT for moving an org off the vlocity namespace — use omnistudio/vlocity-to-native-omnistudio-migration. NOT for deciding whether to adopt OmniStudio — use architect/omnistudio-vs-standard-decision.
- ▌ Org Cleanup And Technical Debt · pranavnagrecha bundleUse when executing admin-level cleanup in a Salesforce org: deleting unused fields, removing inactive Flow versions, deactivating legacy automation, running Salesforce Optimizer or Org Check, and performing destructive metadata deploys. Triggers: 'clean up unused fields', 'delete inactive flows', 'run Optimizer', 'org has too many custom fields', 'remove old workflow rules', 'Flow version limit'. NOT for assessing or reporting on technical debt (use architect/technical-debt-assessment). NOT for code-level refactoring or Apex cleanup (use apex/ skills).
- ▌ Partner Community Requirements · pranavnagrecha bundleUse this skill to define and validate the requirements for a Salesforce Partner Relationship Management (PRM) implementation: deal registration flows, lead distribution models, partner tier hierarchies, MDF budget tracking, and co-marketing content entitlement. Trigger keywords: partner community requirements, PRM deal registration setup, channel partner portal requirements, lead distribution partner, partner tier management, MDF tracking, co-marketing entitlement. NOT for implementing the partner sharing model — use data/partner-data-access-patterns. NOT for building the portal in Experience Builder — use admin/experience-cloud-site-setup.
- ▌ Persona And Journey Mapping Sf · pranavnagrecha bundleBuild Salesforce-anchored personas and journey maps where every persona ties to a Permission Set Group, primary record types, list views, dashboards, automation, and a measured mobile/desktop posture, and journeys walk each task end-to-end with friction tags that drive UX decisions. NOT for stakeholder authority / RACI (use admin/stakeholder-raci-for-sf-projects), NOT for system-side process flows (use admin/process-flow-as-is-to-be), NOT for Lightning page design itself (use admin/lightning-app-builder-advanced or the lightning-record-page-auditor agent), NOT for pure design / UX research disconnected from org artifacts.
- ▌ Salesforce Object Queryability · pranavnagrecha bundleDistinguish the six real reasons a Salesforce query can 'fail', and the protocol for diagnosing before declaring: object doesn't exist, not queryable in edition, permission-denied, field-level errors, namespace prefix missing, API version mismatch. NOT for one object's own query restrictions, required filters or row caps - use apex/soql-object-limits-and-restrictions. NOT for a query that works but is slow - use data/soql-query-optimization.
- ▌ Salesforce Release Preparation · pranavnagrecha bundleUse when preparing for a Salesforce seasonal release — triaging release notes, reviewing Release Updates, opting into Sandbox Preview, and communicating change impact to stakeholders. Triggers: 'upcoming Salesforce release', 'release notes triage', 'Release Updates', 'sandbox preview opt-in', 'release readiness checklist', 'production upgrade date', 'feature impact', 'critical update', 'roll out the Spring release safely', 'is our org ready for the Spring release'. NOT for planning your own release train — use devops/release-management. NOT for user training and go-live comms — use admin/change-management-and-training.
- ▌ Wealth Management Requirements · pranavnagrecha bundleUse this skill when gathering, structuring, and documenting requirements for a Financial Services Cloud (FSC) wealth management implementation — including financial planning workflow discovery, portfolio review process mapping, client lifecycle requirements, advisor tooling needs, and FSC architecture determination (managed package vs. FSC Core). Trigger keywords: wealth management requirements, FSC requirements gathering, financial planning workflow, portfolio review process, advisor tools setup, FSC data model scoping, wealth management process mapping. NOT for implementation, configuration, or code — use financial-account-setup, fsc-action-plans, or apex/fsc-financial-calculations for those. NOT for FSC architecture decisions — use architect/wealth-management-architecture. NOT for Health Cloud or NPSP requirements.
- ▌ Workflow Field Update Patterns · pranavnagrecha bundleCross-tool decision matrix for field-update automation in Salesforce — Before-Save Flow vs After-Save Flow vs Apex Trigger vs the deprecated Workflow Rule + Field Update. Covers the recursion / re-entrancy rules, governor cost per pattern (Before-Save flow is governor-free for the same record), the order-of-execution slot each tool occupies, and the Workflow-Rule-to-Flow migration playbook for field-update actions. NOT for the full record-save order of execution — use apex/order-of-execution-deep-dive. NOT for building the record-triggered Flow once the tool is chosen — use flow/record-triggered-flow-patterns.
- ▌ Agent Rate Limit Strategy · pranavnagrecha bundleControl LLM spend and Apex governor exposure for high-traffic Agentforce agents via per-user token budgets and graceful fallback when the budget is exhausted. NOT for reducing tokens per conversation in the first place — use agentforce/agentforce-cost-optimization. NOT for API rate-limiting of Salesforce REST endpoints — use integration/api-governance-and-rate-limits.
- ▌ Agentforce Agent Creation · pranavnagrecha bundleUse when creating, configuring, auditing, or troubleshooting an Agentforce agent end-to-end: agent definition, agent user setup, channel assignment, system instructions, activation, and lifecycle management. Triggers: 'create agentforce agent', 'agent not appearing to users', 'how to activate agent', 'agent channel setup', 'agent lifecycle', 'deploy agent to production'. NOT for designing what the agent can DO — an agent that looks up an order, checks a case, or creates a record is action design, use agentforce/agent-actions. NOT for topic boundary design — use agentforce/agent-topic-design.
- ▌ Agentforce Persona Design · pranavnagrecha bundleUse when defining or refining the tone, voice, and behavioral personality of an Agentforce agent: system instruction encoding, brand voice alignment, adaptive response formats, multi-persona strategies. NOT for writing the actual conversational copy — utterances, fallback messages, escalation phrasing — use admin/agent-conversation-design. NOT for topic scope design — use agentforce/agent-topic-design.
- ▌ Agentforce Sales AI Setup · pranavnagrecha bundleSetup and configuration of Einstein for Sales AI features: Opportunity Scoring, Pipeline Inspection AI insights, Einstein email insights and composition, and Forecasting AI — prerequisites, license checks, feature sequencing, data readiness validation. NOT for configuring or troubleshooting Einstein Activity Capture and Relationship Insights in a live org — use agentforce/einstein-copilot-for-sales. NOT for building an Agentforce agent — use agentforce/agentforce-agent-creation. NOT for its topic boundary design — use agentforce/agent-topic-design.
- ▌ Custom Agent Actions Apex · pranavnagrecha bundleBuilding custom Apex-based actions for Agentforce agents: designing @InvocableMethod classes for Atlas Reasoning Engine invocation, defining input/output schema, handling errors, and managing security context. NOT for choosing between Apex, Flow, External Service and prompt-template tool shapes — use agentforce/agentforce-tool-use-patterns. NOT for the Apex test class that covers each action branch — use agentforce/agent-action-unit-tests.
- ▌ Einstein Next Best Action · pranavnagrecha bundleGuide practitioners through building Einstein Next Best Action strategies using Flow Builder, configuring Recommendation records, and surfacing recommendations via the Actions & Recommendations Lightning component. Trigger keywords: next best action, NBA strategy, surface recommendations. NOT for training a custom prediction model on your own records — use agentforce/einstein-prediction-builder. NOT for Einstein Bot or Agentforce agent conversation design — use architect/einstein-bot-architecture.
- ▌ Sales Coach Agent Rollout · pranavnagrecha bundleUse when an admin or RevOps team is rolling out the out-of-the-box Sales Coach agent (the Agentforce template that role-plays opportunity-stage conversations with reps for Discovery, Needs Analysis, Qualification, Proposal/Pricing, and Negotiation/Review). Covers prerequisites (Agentforce SKU, Einstein Generative AI activation, Opportunity stage hygiene, knowledge grounding), stage-by-stage prompt configuration, customizing role-play scenarios with org-specific objections and value props, privacy posture for what gets captured in LLM context vs persisted, console-vs-portal embedding choices, and a measurement plan tying coached opportunities to win-rate signal. Triggers: 'roll out sales coach agent', 'set up Agentforce sales coach for our reps', 'sales coach not engaging reps on early-stage opps', 'customize sales coach role-play scenarios for our industry', 'how do we measure sales coach effectiveness', 'sales coach feedback contradicts our methodology'. NOT for rolling out an HR or employee self-service age
- ▌ Apex Named Credentials Patterns · pranavnagrecha bundleUse when writing Apex that calls out to external endpoints via Named Credentials, working with custom header formula tokens ({!$Credential.OAuthToken}), querying per-user auth state through the UserExternalCredential SObject, or diagnosing why Named Credential callouts fail. Trigger keywords: 'callout: prefix', 'named credential header formula', 'UserExternalCredential', 'External Credential per-user principal', 'Named Credential oauth token apex'. NOT for Named Credential setup in the Salesforce Setup UI — use integration/named-credentials-setup. NOT for general HTTP callout mechanics (HttpRequest, HttpResponse, mock patterns) — use apex/callouts-and-http-integrations.
- ▌ Apex Regex And Pattern Matching · pranavnagrecha bundleUse when writing Apex that validates, extracts, or transforms strings with Pattern/Matcher or String regex methods. Covers catastrophic backtracking, the 1M char input cap, anchored vs unanchored matching, and replaceAll reserved `$`/`\` chars. NOT for String.split or String.format — use apex/apex-string-and-regex. NOT for Flow REGEX() — use flow/flow-formula-and-expression-patterns.
- ▌ Apex Secrets And Protected Cmdt · pranavnagrecha bundleStoring API keys, signing secrets, and third-party tokens that Apex must consume — Protected Custom Metadata in a managed package, Protected Custom Settings, Encrypted Custom Fields, Apex Crypto, and what to NEVER do (hardcode, unprotected CMDT, System.debug). NOT for callout authentication — use apex/apex-named-credentials-patterns. NOT for computing the HMAC or signature itself — use apex/apex-encoding-and-crypto. NOT for record-level Shield data encryption — use security/platform-encryption.
- ▌ Apex User And Permission Checks · pranavnagrecha bundleUse when Apex needs to check what the running user is, can see, or can do — via UserInfo, FeatureManagement, FeatureManagement.checkPermission, or FeatureManagement.checkPermissionType. Covers custom permissions, permission sets, user licenses, and profile checks. NOT for CRUD/FLS enforcement — use apex/apex-stripinaccessible-and-fls-enforcement. NOT for creating or assigning custom permissions in Setup — use admin/custom-permissions.
- ▌ Feature Flags And Kill Switches · pranavnagrecha bundleUse when implementing runtime feature toggles, emergency kill switches, or gradual rollout controls in Apex using Custom Metadata Types, Custom Permissions, or Hierarchical Custom Settings. NOT for disabling a trigger during a data load — use apex/apex-trigger-bypass-and-killswitch-patterns. NOT for CMDT basics — use admin/custom-metadata-types.
- ▌ Soql For View And For Reference · pranavnagrecha bundleUse when a SOQL query that serves a custom record-viewing surface (custom LWC/Aura/Visualforce page, mobile app, or API client) must make the retrieved records show up in the user's Recent Items and global-search auto-complete by writing LastViewedDate / LastReferencedDate and a RecentlyViewed row via the optional FOR VIEW / FOR REFERENCE clauses. Covers which clause to pick, correct grammar placement, the misuse warning, the RecentlyViewed 90-day / 200-per-object lifecycle, and the custom-object custom-tab prerequisite. Standard Lightning record pages already write recency for you. NOT for FOR UPDATE row locking — use apex/record-locking-and-contention. NOT for scoping a query to Mine / Team / Territory — use apex/soql-using-scope-clause.
- ▌ Agent Console Requirements · pranavnagrecha bundleUse when gathering and documenting requirements for a Lightning Service Console deployment: agent workspace layout, page template selection, utility bar composition, macro requirements, case handling workflows, split-view navigation design, and licensing requirements. Triggers: service console requirements, agent workspace design, console page layout, utility bar planning, console licensing. NOT for console configuration steps or click-by-click setup (use admin/case-management-setup), NOT for Omni-Channel routing model design (use architect/service-cloud-architecture), NOT for CTI telephony integration details.
- ▌ AI Governance Architecture · pranavnagrecha bundleSystem architecture for Salesforce AI governance: MLOps pipeline design, AI Audit Trail architecture, Einstein Trust Layer security design, Policy-as-Code engine, and regulatory compliance design for EU AI Act and similar frameworks. NOT for authoring AI ethics policy and human-oversight requirements - use admin/ai-ethics-and-governance-requirements. NOT for model tier selection or Supervisor/Specialist topology - use architect/ai-platform-architecture.
- ▌ AI Ready Data Architecture · pranavnagrecha bundleUse when designing or auditing a Salesforce data architecture to support AI features — Einstein, Agentforce, Data Cloud, or custom ML models. Covers field-level data quality requirements, structured vs unstructured data placement, embedding-ready text field design, knowledge article structure for RAG grounding, Data Cloud harmonized data model, Einstein Feature Store patterns, AI-ready field naming conventions, and data freshness requirements for model retraining. Trigger phrases: design data model for AI, make Salesforce data AI-ready, data quality for Einstein, grounding data for Agentforce, Data Cloud for AI, RAG data architecture Salesforce. NOT for building the RAG grounding pipeline — use agentforce/rag-patterns-in-salesforce. NOT for Einstein Discovery or Prediction Builder training-data prep — use data/ai-training-data-preparation.
- ▌ Industries Cloud Selection · pranavnagrecha bundleUse this skill when selecting which Salesforce Industries (vertical) cloud fits a customer's industry and requirements — evaluating data model compatibility, licensing implications, and customization vs configuration tradeoffs before committing to a vertical cloud; pre-purchase selection only, not configuration or OmniStudio development. Trigger keywords: which industry cloud should I use, Communications Cloud vs Health Cloud, Industries licensing, vertical cloud selection, Salesforce Industries portfolio, industry cloud comparison. NOT for Industries CPQ vs Salesforce CPQ selection — use omnistudio/industries-cpq-vs-salesforce-cpq. NOT for the object model of a chosen vertical — use architect/industries-data-model.
- ▌ Revenue Cloud Architecture · pranavnagrecha bundleArchitecting on Salesforce Revenue Cloud (Revenue Lifecycle Management — RLM, the successor to CPQ-Plus + Billing). Covers the five RLM domains (Product Catalog & Pricing, Transaction Management, Contract Lifecycle Management, Order-to-Cash, Billing), the canonical data model (Product2 / PricebookEntry / Quote / Order / OrderItem / Contract / Asset / BillingSchedule / Invoice / LegalEntity), multi-entity scoping via LegalEntity, the RLM ↔ ERP integration patterns (CDC + MuleSoft preferred over point-to-point trigger callouts), and the disambiguation between native RLM and the legacy `blng__` Salesforce Billing managed package and `SBQQ__` CPQ classic. NOT for implementing DRO fulfilment plans or Connect API billing schedules - use integration/revenue-lifecycle-management. NOT for CPQ classic bundle, pricing and quoting architecture - use architect/cpq-architecture-patterns.
- ▌ Service Cloud Architecture · pranavnagrecha bundleUse when designing a Service Cloud solution end-to-end: channel strategy (phone, email, chat, messaging, social), routing model (queue-based vs skills-based Omni-Channel), knowledge strategy, entitlement and SLA enforcement, Einstein Bot / Agentforce deflection, and integration points. Triggers: service cloud architecture, case routing design, omni-channel strategy, contact center design, channel strategy, knowledge deflection, service console architecture. NOT for case setup click-paths - use admin/case-management-setup. NOT for Einstein Bot dialog and intent design - use architect/einstein-bot-architecture.
- ▌ Data Loader Batch Window Sizing · pranavnagrecha bundleChoose the right batch size, parallel/serial mode, and load window for Data Loader, Bulk API V1/V2, and custom Database.executeBatch jobs against a given object volume and complexity profile. Covers tradeoffs between batch size, trigger CPU cost, sharing recalculation cost, and row-skew lock contention. NOT for CSV column mapping (use data/data-loader-csv-column-mapping). NOT for picklist validation pre-load (use data/data-loader-picklist-validation-pre-load). NOT for sharing-recalc tuning after the load lands (use data/sharing-recalculation-performance).
- ▌ Sandbox Refresh Data Strategies · pranavnagrecha bundleUse this skill when designing data strategies for sandbox refreshes: which reference data must be re-seeded after every refresh, the native Data Seeding feature, SandboxPostCopy implementations that hand off to Queueable jobs for large data loads, and clearing stale data between sprints. Trigger keywords: seed data after sandbox refresh, SandboxPostCopy data strategy, native data seeding Salesforce, reference data re-seed after refresh, post-refresh data cleanup. NOT for refresh mechanics, sandbox templates and PII masking — use devops/sandbox-refresh-and-templates. NOT for sandbox type selection — use admin/sandbox-strategy. NOT for scratch-org data seeding for CI — use devops/data-seeding-for-testing.
- ▌ Cpq Deployment Administration · pranavnagrecha bundleDeploying Salesforce CPQ (Steelbrick/SBQQ) configuration between orgs — Product Rules, Price Rules, Price Actions, Price Conditions, Option Constraints, Quote Templates, Custom Settings: data-migration strategy, parent-child ordering, external-ID mapping, tooling choice (Prodly, Copado, Salto, Data Loader). NOT for building the bundles and rules in the first place — use admin/cpq-product-catalog-setup. NOT for bulk-loading the product catalog itself — use data/product-catalog-migration-cpq.
- ▌ Github Actions For Salesforce · pranavnagrecha bundleUse this skill to set up, review, or troubleshoot GitHub Actions CI/CD pipelines for Salesforce using SFDX JWT Bearer Flow authentication, Apex test gates, and branch-conditional deployments. Trigger keywords: github actions, CI pipeline, jwt auth, sfdx ci, workflow yaml, github secrets, apex coverage threshold. NOT for GitLab CI — use devops/gitlab-ci-for-salesforce. NOT for Bitbucket Pipelines — use devops/bitbucket-pipelines-for-salesforce.
- ▌ Sandbox Refresh And Templates · pranavnagrecha bundleSandbox refresh cycles, sandbox templates, post-refresh automation via the SandboxPostCopy Apex interface, and data handling during refresh. NOT for sandbox type selection — use admin/sandbox-strategy.
- ▌ Flow Element Naming Conventions · pranavnagrecha bundleCanonical naming conventions for Flow elements (Get_/Update_/Decision_/Loop_/Assignment_), resource variables (var/coll/map/formula/choice/constant/stage/screen), Decision branch outcomes, Stage/Step labels in Orchestrations, Subflow input/output contracts, and fault-path target names. NOT for object or field API naming (use admin/object-creation-and-design) or flow portfolio retirement — use flow/flow-governance.
- ▌ Flow Large Data Volume Patterns · pranavnagrecha bundleUse when Flows must stay healthy at large data volumes: total SOQL rows returned per transaction, unbounded Get Records, collection sizing, scheduled or record-triggered scale, and when to cap or move work async. Triggers: 'Too many query rows 50001 flow', 'Get Records returns too many rows', 'LDV flow design', 'flow collection limit', 'record triggered flow production data volume'. NOT for loop and per-iteration query patterns — use flow/flow-bulkification. NOT for Batch Apex jobs — use apex/batch-apex-patterns.
- ▌ Flow Reactive Screen Components · pranavnagrecha bundleBuild reactive Flow screens where one component updates another without navigation using reactive formulas and component outputs. NOT for Aura-based screens — use flow/flow-screen-input-validation-patterns.
- ▌ Workflow Rule To Flow Migration · pranavnagrecha bundleMigrate Workflow Rules to record-triggered Flows: field update mapping, email alert migration, outbound message alternatives using Flow Core Actions, time-based workflow replacement with Scheduled Paths. NOT for Process Builder migration — use flow/process-builder-to-flow-migration. NOT for building the replacement flow from scratch — use flow/record-triggered-flow-patterns.
- ▌ Data Cloud Ingestion API · pranavnagrecha bundleUse when implementing or troubleshooting the Salesforce Data Cloud Ingestion API — covers streaming ingestion (near-real-time micro-batches), bulk ingestion (CSV-based full-replace jobs), schema management in OpenAPI. NOT for standard Salesforce Bulk API, CRM Analytics data import, or Data Cloud data stre — use integration/bulk-api-2-patterns.
- ▌ Loyalty Management Setup · pranavnagrecha bundleUse this skill when setting up or extending Salesforce Loyalty Management — including program and currency creation, tier group design, qualifying vs. non-qualifying point currency separation, DPE batch job. NOT for Marketing Cloud engagement program design or B2B loyalty via Sales Cloud — use architect/loyalty-program-architecture.
- ▌ Sis Integration Patterns · pranavnagrecha bundleUse this skill when designing or implementing an integration between a Student Information System (SIS) — such as Ellucian Banner, Ellucian Colleague, Anthology Student, Oracle PeopleSoft Campus Solutions, or Workday Student — and Salesforce Education Cloud. NOT for Salesforce Admissions Connect application processing, Financial Aid integration — use architect/sales-cloud-integration-patterns.
- ▌ Sustainability Reporting · pranavnagrecha bundleProducing regulatory and voluntary sustainability disclosures from Salesforce Net Zero Cloud (formerly Sustainability Cloud) — the native ESRS / CSRD / SASB / GRI / CDP report builders, the Carbon Accounting Manager data model (Stationary Asset, Vehicle Asset, Scope 3 procurement items, Energy Use Records), the double-materiality assessment prerequisite for CSRD, the MSESRSMainDataraptor Data Mapper for ESRS reports, and the Sustainability Scorecard. NOT for Net Zero Cloud feature setup / emissions-source configuration (use integration/net-zero-cloud-setup), NOT for general CRM Analytics dashboards (Net Zero Cloud's report builders are a separate surface).
- ▌ Webhook Inbound Patterns · pranavnagrecha bundleUse when implementing an inbound webhook receiver in Salesforce: routing via Apex REST and Salesforce Sites, authenticating webhook payloads via HMAC, ensuring idempotent processing, and handling the 5-second response window. NOT for Salesforce POSTing a webhook out to a third-party endpoint — use integration/outbound-webhook-from-salesforce. NOT for designing a general-purpose Apex REST API rather than a webhook sink — use apex/apex-rest-services.
- ▌ Lwc Mobile Offline And Briefcase · pranavnagrecha bundleUse when designing LWCs that must work offline in the standard Salesforce Mobile App, and when configuring Briefcase Builder rules to prime records onto user devices. Covers form-factor detection (`@salesforce/client/formFactor`), Lightning Data Service offline-cache behavior, Briefcase priming-rule design, conflict resolution on reconnect, and the legacy SmartStore / IndexedDB picture for context. Triggers: 'briefcase builder rule design', 'lwc not working offline', 'how do I prime records to user devices', 'sync conflict on reconnect', 'offline draft persistence in lwc'. NOT for Field Service Mobile offline priming (use admin/fsl-mobile-app-setup or architect/fsl-offline-architecture — FSL has its own priming pipeline). NOT for general LWC mobile container patterns / device APIs (use lwc/lwc-offline-and-mobile).
- ▌ Lwc Shadow Vs Light Dom Decision · pranavnagrecha bundleDecide Shadow DOM vs Light DOM for an LWC — Salesforce distribution rules, Locker/LWS, third-party library needs. Triggers: shadow vs light DOM, renderMode decision. NOT for implementing Light DOM after the decision — use lwc/lwc-light-dom.
- ▌ Flexcard State Management · pranavnagrecha bundleFlexCard actions, conditional visibility, and state across navigation, refresh, and parent/child transitions. Triggers: flexcard state, flexcard actions, flexcard refresh. NOT for FlexCard layout/design — use omnistudio/flexcard-design-patterns. NOT for admin requirements — use admin/flexcard-requirements.
- ▌ Industries API Extensions · pranavnagrecha bundleEndpoint path, payload and error handling for a named Salesforce Industries API — Insurance Policy Business Connect, Communications Cloud TM Forum Open APIs (TMF679, TMF680), Energy and Utilities Update Asset Status, Service Process Studio Connect. Trigger keywords: Insurance policy issuance API, endorsement API, TMF679, Communications Cloud REST API, Update Asset Status, Service Process API, InsurancePolicy Connect API, sfiEnergy, industry-specific REST endpoint. NOT for designing the integration to a policy admin, BSS/OSS or CIS backend — use architect/industries-integration-architecture. NOT for standard Salesforce REST API CRUD on non-industry sObjects — use integration/rest-api-patterns.
- ▌ Omnistudio CI CD Patterns · pranavnagrecha bundleCI/CD pipelines for OmniStudio — DataPack export/import, versioning, env promotion. Triggers: OmniStudio CI/CD, DataPack pipeline, OmniStudio deployment. NOT for manual DataPack operations — use omnistudio/omnistudio-deployment-datapacks.
- ▌ Omnistudio Multi Language · pranavnagrecha bundleLocalize OmniScripts, FlexCards, and DataRaptors using Label-based translation, multi-language JSON, and locale-aware number/date formatting. NOT for Salesforce Translation Workbench alone — use admin/multi-language-and-translation.
- ▌ Omnistudio Remote Actions · pranavnagrecha bundleUse when configuring, troubleshooting, or choosing between Remote Action types in OmniScript or FlexCard. Triggers: 'remote action', 'OmniScript action', 'IP action', 'Apex action element'. NOT for Integration Procedure internal design or generic Apex callout patterns — use omnistudio/integration-procedures.
- ▌ Commerce Checkout Configuration · pranavnagrecha bundleUse this skill when configuring Salesforce B2B or D2C Commerce checkout: payment methods, shipping/tax integration, guest checkout, order summary setup, and CartCheckoutSession state orchestration. Trigger keywords: checkout flow, payment adapter, shipping tax integration, guest checkout, order summary, CartCheckoutSession, Managed Checkout, Commerce checkout flow. NOT for deciding the checkout design before build (LWR vs Aura) — use admin/commerce-checkout-flow-design. NOT for writing the CommercePayments adapter class — use apex/commerce-payment-integration.
- ▌ Commerce Pricing And Promotions · pranavnagrecha bundleConfigure pricebooks, tiered pricing, promotions, coupon codes, and cart discounts for B2B or D2C Commerce stores. Trigger keywords: WebStorePricebook, BuyerGroupPricebook, PriceAdjustmentSchedule, PromotionsCartCalculator, commerce coupon, cart-level discount, tiered price, Commerce promotion. NOT for Sales Cloud pricebooks and PricebookEntry - use admin/products-and-pricebooks. NOT for CPQ quote pricing and discount schedules - use admin/cpq-pricing-rules.
- ▌ Contract And Renewal Management · pranavnagrecha bundleUse when configuring or troubleshooting Salesforce CPQ contract creation, subscription management, amendment quotes, or renewal quotes. Trigger keywords: contract, amendment, renewal, subscription, co-termination, SBQQ__Subscription__c. NOT for designing the amendment/renewal architecture or swap pattern — use architect/subscription-management-architecture. NOT for amending or renewing contracts from Apex — use apex/cpq-api-and-automation.
- ▌ Custom Notification Type Design · pranavnagrecha bundleUse when designing Custom Notification Types that fire via Flow, Apex, or Process Builder to Lightning bell, desktop, mobile (push), and Slack. Covers channel enablement, targeting, deliverability, consent, and anti-spam discipline. NOT for actually sending one from Flow or Apex, or the recipient limit — use admin/custom-notification-types. NOT for email templates and alerts — use admin/email-templates-and-alerts.
- ▌ Digital Storefront Requirements · pranavnagrecha bundleUse when gathering or evaluating requirements for a Salesforce Commerce Cloud digital storefront — branding strategy, content management approach, personalization, mobile experience, and accessibility compliance. Trigger keywords: SFRA branding, PWA Kit storefront, composable storefront, storefront accessibility, WCAG Commerce Cloud, overlay cartridge branding, mobile storefront, storefront personalization, content slots. NOT for building the site in Business Manager — use admin/b2c-commerce-store-setup. NOT for SCAPI design, Managed Runtime and caching strategy — use architect/headless-commerce-architecture.
- ▌ Einstein Activity Capture Setup · pranavnagrecha bundleConfigure Einstein Activity Capture (EAC) for an org: enable the feature, create Configuration profiles, set auth type (User-Level or Org-Level OAuth), define email and calendar sync scope, excluded domains and privacy settings, assign users, verify sync health. NOT for querying synced emails or events in SOQL, Apex or reports — use apex/einstein-activity-capture-api. NOT for Opportunity Scoring or Pipeline Inspection — use agentforce/einstein-copilot-for-sales.
- ▌ Enterprise Territory Management · pranavnagrecha bundleUse when configuring or troubleshooting Salesforce Enterprise Territory Management (ETM): territory models, territory types, territory hierarchies, account assignment rules, opportunity territory assignment, and forecast by territory. Trigger keywords: territory model, territory hierarchy, ETM, assign accounts to territories, territory forecast, territory activation. NOT for choosing the coverage model first — use admin/territory-design-requirements. NOT for role hierarchy — use admin/sharing-and-visibility.
- ▌ Health Cloud Consent Management · pranavnagrecha bundleUse this skill when configuring Health Cloud patient consent management: setting up HIPAA authorization forms, consent templates, consent tracking per patient, and withdrawal handling. NOT for querying the AuthorizationFormConsent object hierarchy or its required field values — use data/consent-data-model-health. NOT for GDPR/CCPA marketing opt-out on ContactPointTypeConsent — use security/gdpr-data-privacy.
- ▌ Industries Communications Setup · pranavnagrecha bundleConfigure Communications Cloud for the first time: org setup sequence, permission sets, Enterprise Product Catalog (EPC) service catalog, TM Forum-aligned order decomposition setup, Account record-type segmentation, contract lifecycle activation. NOT for designing the commercial-to-technical order process itself - use admin/industries-process-design. NOT for calling TM Forum Open APIs (TMF622, TMF679) - use omnistudio/industries-api-extensions.