PranavNagrecha

@pranavnagrecha source repo

1.1k skills
0 followers
15 repo stars
2 weeks ago last updated

▌
Tableau Salesforce Connector · pranavnagrecha bundle
Tableau ↔ Salesforce integration patterns: Tableau Salesforce connector, Tableau for Salesforce, CRM Analytics alternative, Data Cloud + Tableau, embedded Tableau dashboards. Choose between connector modes (live, extract, Data Cloud). NOT for CRM Analytics Studio app build-out (use admin/crm-analytics-app-creation) — use architect/crm-analytics-vs-tableau-decision.

15 repo stars
▌
Connected App Security Policies · pranavnagrecha bundle
Managing OAuth policies, IP relaxation, session security, PKCE, and credential rotation for Salesforce Connected Apps. Use when hardening Connected App security, rotating client secrets, configuring IP restrictions, or requiring high-assurance sessions. NOT for basic Connected App setup or creation — use admin/connected-app-troubleshooting.

15 repo stars
▌
Session High Assurance Policies · pranavnagrecha bundle
Enforce step-up authentication for sensitive pages/objects using High Assurance session level and login flow policies. NOT for initial MFA enrollment UX — use admin/org-setup-and-configuration.

15 repo stars
▌
Acceptance Criteria Given When Then · pranavnagrecha bundle
Use this skill when writing test-first, behavior-driven acceptance criteria in Given/When/Then format for a Salesforce user story. Covers happy path, edge cases, negative paths, permission boundaries, and data-state preconditions so the AC block can drive UAT scripts and Apex test design downstream. Trigger keywords: given when then, gherkin, behavior driven AC, test first acceptance criteria, scenario outline, BDD acceptance criteria. NOT for the user-story format itself (use admin/user-story-writing-for-salesforce). NOT for UAT script writing (use admin/uat-test-case-design). NOT for Apex test method generation (use agents/test-class-generator). NOT for high-level UAT planning (use admin/uat-and-acceptance-criteria).

15 repo stars
▌
Batch Job Scheduling And Monitoring · pranavnagrecha bundle
Use when monitoring, diagnosing, or managing Batch Apex, Scheduled Apex, Queueable, and Flow scheduled jobs: Setup > Apex Jobs, AsyncApexJob queries, concurrent limits, failure detection, and notification patterns. NOT for writing the Batch or Schedulable class itself — use apex/batch-apex-patterns or apex/apex-scheduled-jobs. NOT for BatchApexErrorEvent alerting in code — use apex/scheduled-apex-failure-detection-and-monitoring.

15 repo stars
▌
Lightning Record Page Configuration · pranavnagrecha bundle
Use when building a Lightning record page in App Builder or when the page users see is not the one you assigned. Trigger keywords: configure lightning record page, lightning app builder, flexipage, record page assignment, org default vs app default, activate lightning page. NOT for page speed - use admin/lightning-page-performance-tuning. NOT for page layout to Dynamic Forms migration - use admin/dynamic-forms-migration. NOT for related list columns - use admin/related-list-configuration.

15 repo stars
▌
Lookup Filter Cross Object Patterns · pranavnagrecha bundle
Design or repair lookup filters that constrain a child lookup using fields from the parent record (or a sibling record on the same object). Triggers: 'limit lookup based on another field', 'cross-object lookup filter', 'lookup filter $Source vs $User'. NOT for choosing lookup vs master-detail - use admin/lookup-and-relationship-design. NOT for duplicate matching rule criteria - use admin/duplicate-management.

15 repo stars
▌
Omniscript Flow Design Requirements · pranavnagrecha bundle
Use this skill to gather, document, and validate OmniScript flow design requirements before development begins — covering screen layout requirements, branching logic, data source requirements, and user journey mapping. Trigger keywords: OmniScript requirements, OmniScript BA, OmniScript screen design, OmniScript user journey, OmniScript branching requirements. NOT for building the OmniScript or moving logic into an Integration Procedure — use omnistudio/omniscript-design-patterns. NOT for FlexCard requirements — use admin/flexcard-requirements.

15 repo stars
▌
Reports And Dashboards Fundamentals · pranavnagrecha bundle
Use when learning, designing, or explaining Salesforce Reports and Dashboards from first principles — report types, custom report types, groupings, bucket fields, summary formulas, charts, dashboard components, dynamic dashboards, report subscriptions, and folder permissions. Triggers: 'how do I build a report', 'what report type should I use', 'set up a dashboard', 'joined report limits', 'bucket field vs formula', 'dynamic dashboard running user'. NOT for CRM Analytics (use crm-analytics-* skills). NOT for Einstein Discovery predictive analytics. NOT for troubleshooting missing report data caused by sharing model issues (use admin/reports-and-dashboards for that).

15 repo stars
▌
Subscription Lifecycle Requirements · pranavnagrecha bundle
Use when documenting, reviewing, or gathering requirements for Salesforce CPQ subscription lifecycle behavior: how amendments, renewals, upgrades, downgrades, and cancellations must work for a specific business. Trigger keywords: subscription requirements, amendment requirements, renewal requirements, proration requirements, co-termination, subscription ledger, upgrade downgrade policy. NOT for configuring CPQ amendments and renewals — use admin/contract-and-renewal-management. NOT for amendment architecture — use architect/subscription-management-architecture.

15 repo stars
▌
Agentforce Multi Turn Patterns · pranavnagrecha bundle
Design Agentforce conversations that span multiple turns without losing context: session variable scoping, conversation memory, clarifying-question patterns, topic-to-topic (now subagent) handoff, and the right abstractions for accumulating state across turns. NOT for deciding the topic boundaries themselves or out-of-scope behavior — use agentforce/agent-topic-design. NOT for single-turn agent actions and their input/output contracts — use agentforce/agent-actions.

15 repo stars
▌
Einstein Discovery Development · pranavnagrecha bundle
Integrating Einstein Discovery predictions into Salesforce apps, automating bulk scoring jobs, deploying stories as prediction definitions, managing models via API, or querying prediction history. Trigger keywords: Einstein Discovery, smartdatadiscovery, predict endpoint, bulk scoring job, model refresh job, prediction definition, story deployment, regression prediction, multiclass prediction, CRM Analytics ML. NOT for authoring the story in CRM Analytics Studio — use admin/einstein-discovery-setup. NOT for the click-path rollout of a trained model through Model Manager and page layouts — use admin/einstein-discovery-deployment.

15 repo stars
▌
Formula Field Performance And Limits · pranavnagrecha bundle
Use when diagnosing SOQL performance problems caused by formula fields, hitting formula compile-size limits, or deciding whether to replace a formula field with a stored field for indexing. Triggers: 'formula field slowing SOQL', 'compile size limit', 'cross-object formula spanning limit', 'formula field not indexable', 'LDV query full table scan', 'SOQL WHERE on formula'. NOT for formula syntax help, building formula expressions, or authoring new formulas from scratch — use admin/formula-fields for that.

15 repo stars
▌
Analytics Security Architecture · pranavnagrecha bundle
Use this skill when designing or auditing CRM Analytics (formerly Einstein Analytics / Tableau CRM) data access controls: row-level security predicates, dataset-level visibility, app-level sharing roles, sharing inheritance configuration, and cross-dataset security embedding strategies. Trigger keywords: CRM Analytics security, row-level security predicate, Analytics dataset access, sharing inheritance, security predicate design, cross-dataset security, analytics entitlement dataset. NOT for a predicate's SAQL syntax - use data/crm-analytics-security-predicates. NOT for sharing an app or assigning an Analytics license - use admin/analytics-permission-and-sharing.

15 repo stars
▌
Embedded Analytics Architecture · pranavnagrecha bundle
Use this skill to architect CRM Analytics dashboard embedding in Lightning pages, Experience Cloud, or Visualforce — covering dashboard context strategy, filter/state management, cross-dashboard context propagation, performance optimization, and LWC vs Aura component selection. Trigger keywords: embed CRM Analytics dashboard, embedded analytics Lightning page, analytics dashboard filter, wave dashboard LWC, analytics state attribute. NOT for a custom LWC inside a dashboard canvas - use architect/analytics-embedded-components. NOT for building the dashboard's charts and datasets - use admin/analytics-dashboard-design.

15 repo stars
▌
Headless Vs Standard Experience · pranavnagrecha bundle
Use when choosing between Headless, LWR (Lightning Web Runtime), or Aura as the Experience Cloud frontend architecture: performance tradeoffs, developer cost, migration readiness, and flexibility. Trigger keywords: headless vs LWR, LWR vs Aura, Experience Cloud architecture decision, site performance architecture, community site technology choice. NOT for building the chosen site — branding, domain, Experience Builder pages — use admin/experience-cloud-site-setup. NOT for LWR themes and custom components — use lwc/lwr-site-development. NOT for headless CMS delivery via Connect REST API — use lwc/headless-experience-cloud.

15 repo stars
▌
Hybrid Integration Architecture · pranavnagrecha bundle
Use this skill when designing hybrid on-premises-to-Salesforce integration architectures: DMZ relay patterns, reverse proxy configuration, VPN connectivity, and Salesforce Private Connect (AWS PrivateLink) topology. Trigger keywords: on-premises to Salesforce integration network topology, DMZ relay Salesforce, hybrid integration VPN, Private Connect architecture, data residency Salesforce hybrid. NOT for choosing the authentication mechanism — mTLS, OAuth flow, API gateway placement — use architect/integration-security-architecture. NOT for the Setup steps that configure Private Connect peering — use integration/private-connect-setup.

15 repo stars
▌
Limits And Scalability Planning · pranavnagrecha bundle
Use when planning a new org build for scale, auditing an existing org for governor limit exposure, or investigating a limit-related incident. Trigger phrases: 'org is hitting governor limits', 'how many custom objects can we have', 'will our data volume cause performance issues', 'batch job keeps failing with limit errors', 'planning for 10 million records', 'platform event throughput limits', 'SOQL limit exceeded in production'. NOT for one transaction's limits - use apex/governor-limits. NOT for tuning an individual SOQL query - use data/soql-query-optimization. NOT for Batch Apex authoring mechanics - use apex/batch-apex-patterns.

15 repo stars
▌
Migration Architecture Patterns · pranavnagrecha bundle
Architectural patterns for org migration — org merge (consolidate two orgs into one), org split (separate one org into two), and coexistence (run both for a transition period with identity / data / metadata bridges). Covers the pre-migration metadata audit (the most-skipped step), the why-vs-how decision separation for splits, record-Id remapping for external systems that hardcoded 15/18-digit IDs, and rollback-safe deployment windows. NOT for the go-live cutover sequencing itself (use devops/go-live-cutover-planning), NOT for the upstream multi-org-strategy decision (use architect/multi-org-strategy).

15 repo stars
▌
Multi Bu Marketing Architecture · pranavnagrecha bundle
Use this skill when designing or evaluating a Marketing Cloud Engagement multi-Business-Unit hierarchy — covering Enterprise 2.0 parent/child BU structure, Shared Data Extensions, cross-BU user provisioning, and data segregation governance. NOT for configuring business units, user roles, sender and delivery profiles in one account — use admin/marketing-cloud-engagement-setup. NOT for choosing between Marketing Cloud Engagement and Account Engagement (Pardot) — use architect/marketing-cloud-vs-mcae-selection.

15 repo stars
▌
Nonprofit Platform Architecture · pranavnagrecha bundle
Use this skill when designing or evaluating the holistic platform architecture for a Nonprofit Cloud (Agentforce Nonprofit) implementation — module selection, data model foundations, integration strategy, and phased adoption across the six independently licensable modules. Trigger keywords: Nonprofit Cloud architecture, NPC platform design, nonprofit Salesforce architecture, program and fundraising architecture, nonprofit data model strategy, Agentforce Nonprofit. NOT for deciding whether to stay on NPSP or move to NPC — use architect/npsp-vs-nonprofit-cloud-decision. NOT for planning the NPSP-to-NPC data migration — use architect/nonprofit-cloud-vs-npsp-migration.

15 repo stars
▌
Omnistudio Scalability Patterns · pranavnagrecha bundle
Use when OmniStudio components are degrading under high concurrent user load, when Integration Procedures are hitting governor limits at portal scale, or when designing an OmniStudio deployment for thousands of simultaneous Experience Cloud users. Trigger keywords: OmniScript concurrency, Integration Procedure SOQL limits portal, Queueable Chainable, Direct Platform Access, LWR CDN Experience Cloud high volume. NOT for generic scalability planning (use architect/limits-and-scalability-planning), NOT for single-session performance tuning (use omnistudio/omnistudio-performance).

15 repo stars
▌
Omnistudio Vs Standard Decision · pranavnagrecha bundle
Decision framework for choosing OmniStudio (OmniScript, FlexCards, Integration Procedures) vs standard Salesforce tooling (Screen Flow, LWC, Apex) for guided UI and data transformation use cases: capability matrix, license availability gate, team skills assessment, and migration path from managed package to Standard Designers. NOT for the runtime-path ADR, Standard Runtime vs the vlocity_ins__ package - use architect/omnistudio-vs-standard-architecture. NOT for platform-wide capability choices like Custom Metadata vs Custom Settings - use architect/platform-selection-guidance. NOT for executing a Vlocity managed-package to native OmniStudio namespace migration — use omnistudio/vlocity-to-native-omnistudio-migration; this skill only decides whether to use OmniStudio at all.

15 repo stars
▌
Bitbucket Pipelines For Salesforce · pranavnagrecha bundle
Use this skill to set up, review, or troubleshoot Bitbucket Pipelines CI/CD workflows for Salesforce using SFDX JWT Bearer Flow or SFDP URL authentication, Apex test gates, branch-based deployment strategies, and Bitbucket repository variables for secret management. Trigger keywords: bitbucket pipelines, bitbucket CI, atlassian pipe, salesforce-deploy pipe, bitbucket-pipelines.yml, bitbucket repository variables. NOT for GitHub Actions (use devops/github-actions-for-salesforce), Jenkins, Copado, Azure DevOps, or any non-Bitbucket CI platform.

15 repo stars
▌
Code Coverage Orphan Class Cleanup · pranavnagrecha bundle
Use when an org's overall Apex coverage is sliding toward 75% because of orphaned (uncovered, unreferenced) classes inflating the denominator. Triggers: 'production deploy blocked at 74% coverage', 'find apex classes with 0% coverage', 'orphan apex class report', 'org coverage dropping despite green test runs'. NOT for writing tests on actively used classes (use apex/test-class-standards) or for raising coverage on partially-covered classes.

15 repo stars
▌
Migration From Change Sets To Sfdx · pranavnagrecha bundle
Use when planning or executing a migration from change-set-based deployments to Salesforce DX source-driven development. Trigger keywords: 'migrate from change sets', 'move to SFDX', 'convert metadata to source format'. NOT for greenfield SFDX project setup (use sf-cli-and-sfdx-essentials), unlocked package — use apex/sf-cli-and-sfdx-essentials.

15 repo stars
▌
Permission Set Deployment Ordering · pranavnagrecha bundle
Use when deploying permission sets, permission set groups, or profiles and encountering cross-reference errors, silent permission loss, or ordering failures. Triggers: 'permission set deployment fails', 'cross-reference id error during deploy', 'permissions disappear after deployment', 'permission set group deployment error'. NOT for permission set design or architecture decisions (use permission-set-architecture), NOT for creating permission sets from scratch (use admin/permission-set-architecture).

15 repo stars
▌
Second Generation Managed Packages · pranavnagrecha bundle
2GP managed package development: creating managed packages with Dev Hub and Salesforce CLI, semantic versioning, patch versions, namespace linking, ISV AppExchange listing, and subscriber upgrade management. NOT for unlocked packages — use devops/unlocked-package-development. NOT for 1GP packaging orgs and namespace registration — use devops/managed-package-development.

15 repo stars
▌
Flow Formula And Expression Patterns · pranavnagrecha bundle
Author NULL-safe, type-correct, performance-aware Formula resources and condition expressions in Flow: lazy re-evaluation, BLANKVALUE/ISBLANK guards, ISPICKVAL vs =. NOT for record-level formula fields on objects — use admin/formula-fields. NOT for Validation Rule formulas — use admin/validation-rules.

15 repo stars
▌
File And Document Integration · pranavnagrecha bundle
Use when uploading, downloading, managing, or integrating files and documents with Salesforce — covering ContentVersion/ContentDocument, REST multipart uploads, base64 inserts, Files Connect for external storage. NOT for Bulk API data loads, Chatter feed post content, email attachment handling via Em — use security/file-upload-virus-scanning.

15 repo stars
▌
Heroku Salesforce Integration · pranavnagrecha bundle
Heroku ↔ Salesforce integration paths — Heroku Connect (Postgres bidirectional sync), Heroku AppLink (expose Heroku APIs to Flow / Apex / Agentforce), Heroku External Objects (Salesforce Connect oData), Platform Events, REST API in either direction, and Salesforce Canvas for UI. NOT for AWS integration — use integration/aws-salesforce-patterns.

15 repo stars
▌
Mulesoft Salesforce Connector · pranavnagrecha bundle
Designing and configuring MuleSoft Anypoint Salesforce Connector flows: API selection (SOAP/REST/Bulk/Streaming), OAuth 2.0 JWT Bearer auth, watermark-based incremental sync with Object Store, batch processing with record-level error isolation. NOT for native Salesforce-to-Salesforce integration without MuleSoft — use integration/platform-events-integration or integration/change-data-capture-integration. NOT for generic REST callouts from Apex — use integration/rest-api-patterns.

15 repo stars
▌
Experience Cloud Search Customization · pranavnagrecha bundle
Use this skill when configuring or extending search on an Experience Cloud site — covering Search Manager scope configuration, LWR vs Aura search component selection, federated search setup, guest user search access, and custom search result components. NOT for SOSL/SOQL query development — use lwc/experience-cloud-lwc-components.

15 repo stars
▌
Document Generation Omnistudio · pranavnagrecha bundle
Generating documents (PDF, DOCX, PPTX) from OmniStudio using Document Templates, OmniDataTransform token mapping, and OmniScript or Integration Procedure orchestration. Use when building client-side interactive or server-side batch document generation flows. NOT for Salesforce CPQ document generation — use apex/fsc-document-generation.

15 repo stars
▌
Flexcard Container Composition · pranavnagrecha bundle
Design FlexCard composition: parent/child state flow, layout modes, actions, event wiring, and data source selection. Trigger keywords: flexcard, flex card composition, parent child flexcard, flexcard state, flexcard. NOT for the first-time FlexCard Hello-World, LWC alternatives, or Experience Cloud theming — use admin/flexcard-requirements.

15 repo stars
▌
Omnistudio Custom Lwc Elements · pranavnagrecha bundle
Creating and integrating custom Lightning Web Components within OmniScripts: LWC override patterns, pubsub event handling, custom validation, OmniStudio data passing conventions. Use when a standard OmniScript element cannot meet a UX requirement. NOT for standalone LWC development (use lwc/* skills) — use lwc/lwc-web-components-interop.

15 repo stars
▌
Ip Range And Login Flow Strategy · pranavnagrecha bundle
Design and implement Salesforce Login Flows (Screen Flows assigned to profiles or Experience Cloud sites) that run post-authentication to enforce conditional MFA, IP-based branching, terms-of-service acceptance, or Experience Cloud custom login pages. NOT for IP allowlisting (use security/network-security-and-trusted-ips) or org-wide MFA rollout — use security/mfa-enforcement-strategy.

15 repo stars
▌
Network Security And Trusted Ips · pranavnagrecha bundle
Configure and audit Salesforce network security controls — trusted IP ranges (org-wide Network Access), login IP ranges on profiles, CSP Trusted Sites for Lightning components, CORS allowlists for external JavaScript, and TLS requirements — and troubleshoot login-blocked-by-IP or CSP violation errors. NOT for per-profile login IP range policy, IP relaxation decisions, or their interaction with MFA and SSO — use security/ip-relaxation-and-restriction.

15 repo stars
▌
Permission Set Groups And Muting · pranavnagrecha bundle
Use when designing or reviewing permission-set-group architecture, especially profile minimization, group composition, muting strategy, and migration away from profile-heavy security models. Triggers: 'permission set group', 'muting permission. NOT for record-sharing design or CRUD/FLS review in Apex code — use admin/permission-set-architecture.

15 repo stars
▌
Moscow Prioritization For Sf Backlog · pranavnagrecha bundle
Use this skill when prioritizing a Salesforce backlog with the MoSCoW method (Must / Should / Could / Won't) plus an effort + value lens, deciding what fits in the next sprint or release, and using WSJF as a tie-break when MoSCoW alone produces ties. Trigger keywords: MoSCoW prioritization, must should could won't, WSJF salesforce, prioritize salesforce stories, sprint commit, backlog grooming. NOT for story writing or splitting (use admin/user-story-writing-for-salesforce). NOT for release train planning (use agents/release-train-planner). NOT for sizing/estimation method debates — this skill assumes a sizing convention is already in place.

15 repo stars
▌
Einstein Search Personalization · pranavnagrecha bundle
Einstein Search personalization: configure search result ranking, promoted results, searchable objects, and Natural Language Search (NLS) for Lightning Experience. Triggers when users ask about search personalization signals, why search results feel irrelevant, how to enable NLS conversational queries, or how to manage Einstein Search settings in Setup. NOT for search on an Experience Cloud site or community portal — use lwc/experience-cloud-search-customization. NOT for B2B or D2C Commerce storefront product search and facets — use apex/commerce-search-customization.

15 repo stars
▌
Composable Commerce Architecture · pranavnagrecha bundle
Composable commerce on Salesforce: headless API layer, micro-frontends, BFF pattern, CDN strategy, third-party composability over B2C/B2B Commerce. NOT for the supported PWA Kit on Managed Runtime composable storefront — use architect/headless-commerce-architecture. NOT for standard B2C storefront setup — use admin/b2c-commerce-store-setup.

15 repo stars
▌
Data Cloud Vs Analytics Decision · pranavnagrecha bundle
Use when choosing or explaining how Salesforce Data Cloud (Data 360) and CRM Analytics (Tableau CRM / Einstein Analytics) fit together versus overlap — unified data platform vs analytics consumption, Direct Data on Data Model Objects (DMOs), identity and activation vs dashboards and recipes. Triggers: 'Data Cloud vs CRM Analytics', 'when to use Data Cloud versus Einstein Analytics', 'should we buy Data Cloud or CRM Analytics', 'CRM Analytics on Data Cloud DMOs', 'direct data connector Data Cloud', 'analytics on unified profile architecture'. NOT for step-by-step implementation of Data Cloud data streams, identity resolution rules, CRM Analytics recipes, dataflows, or dashboard build — use architect/data-cloud-architecture, admin/data-cloud-identity-resolution, or admin/einstein-analytics-basics for that.

15 repo stars
▌
Experience Cloud Licensing Model · pranavnagrecha bundle
Use this skill to select the correct Experience Cloud external user license type for a portal or community. Trigger keywords: Customer Community vs Partner Community, login-based vs member-based license, External Apps license, external user license selection, Experience Cloud license tiers. NOT for adding members, self-registration or login pages — use admin/experience-cloud-member-management. NOT for bulk-migrating existing portal users between license types — use data/community-user-data-migration.

15 repo stars
▌
Fundraising Integration Patterns · pranavnagrecha bundle
Use this skill when connecting a Salesforce Nonprofit Cloud or NPSP org to fundraising-adjacent systems: payment gateways via Salesforce.org Elevate, wealth screening tools (iWave, DonorSearch), email marketing platforms (Marketing Cloud, Pardot), and event management platforms. Trigger keywords: payment gateway nonprofit, Elevate payment services, GiftTransaction API, wealth screening integration, iWave Salesforce, DonorSearch scores, donor email marketing sync, event registration fundraising. NOT for writing NPSP BDI gift-ingestion or Enhanced Recurring Donation API code — use apex/npsp-api-and-integration. NOT for a one-off historical gift migration — use data/gift-history-import.

15 repo stars
▌
Npsp Vs Nonprofit Cloud Decision · pranavnagrecha bundle
Use this skill when an organization must decide whether to stay on NPSP (Nonprofit Success Pack) or move to Nonprofit Cloud (NPC), evaluate the timeline for that move, and understand what the migration entails at an architectural level. Trigger keywords: NPSP vs Nonprofit Cloud, upgrade NPSP, migrate to NPC, nonprofit platform decision, NPSP end of life, Nonprofit Cloud vs NPSP comparison. NOT for migration execution: object mapping and phased data conversion - use architect/nonprofit-cloud-vs-npsp-migration. NOT for designing the NPC module architecture - use architect/nonprofit-platform-architecture.

15 repo stars
▌
Sales Cloud Integration Patterns · pranavnagrecha bundle
Use when designing or reviewing integrations between Sales Cloud and external systems such as ERP, marketing automation, CPQ, or partner portals. Triggers: 'sync Accounts and Products with ERP', 'integrate marketing leads with Salesforce', 'quote-to-order flow between Salesforce and ERP', 'CPQ integration patterns', 'partner portal data access design'. NOT for generic integration framework design (use architect/integration-framework-design), NOT for Apex HTTP callout mechanics (use apex/callouts-and-http-integrations), NOT for MuleSoft or middleware configuration.

15 repo stars
▌
Sla Design And Escalation Matrix · pranavnagrecha bundle
Use when designing the SLA tier definition table, escalation matrix document, and milestone threshold configuration for a Salesforce Service Cloud implementation. Covers designing the artifact layer — tier tiers (e.g., Enterprise/Professional/Basic), response and resolution time targets, business hours mapping, milestone percentage thresholds at 50/75/90/100%, and the escalation action matrix that maps thresholds to notification targets and automated actions. Triggers: SLA design, escalation matrix, milestone thresholds, tier definition, business hours alignment, SLA enforcement design. NOT for entitlement process configuration steps (use admin/case-management-setup), NOT for escalation rule setup (use admin/escalation-rules), NOT for CPQ quoting SLAs.

15 repo stars
▌
Development Documentation Standards · pranavnagrecha bundle
Standards for Salesforce dev documentation — README, ADR, runbook, release note templates. Triggers: dev documentation standards, ADR template, runbook Salesforce. NOT for automated release notes — use devops/release-notes-automation.

15 repo stars
▌
Flow Deployment Activation Ordering · pranavnagrecha bundle
Deploying Flow metadata across environments when activation order matters: which flow version becomes active, how paused interviews survive deploys, avoiding the 'two active versions for a moment' race, SFDX / Metadata API deploy flags, 'Deploy as Active', rollback. NOT for Change Set vs SFDX vs package choice for a flow — use flow/flow-deployment-and-packaging. NOT for whether a change needs a new version or a new flow — use flow/flow-versioning-strategy.

15 repo stars
▌
Salesforce Devops Tooling Selection · pranavnagrecha bundle
Use when a team needs to choose a DevOps tooling platform for Salesforce — comparing options like Gearset, Copado, Flosum, AutoRABIT, Blue Canvas, and Salesforce DevOps Center across axes of hosting model, team composition, compliance posture, and budget. Trigger keywords: 'which DevOps tool for Salesforce', 'Gearset vs Copado', 'CI/CD tool comparison', 'DevOps platform selection', 'native vs third-party DevOps'. NOT for CI/CD pipeline configuration (use devops/continuous-integration-testing), NOT for Git branching strategy design (use devops/git-branching-for-salesforce), NOT for environment topology decisions (use devops/environment-strategy).

15 repo stars
▌
Flow Screen Input Validation Patterns · pranavnagrecha bundle
Design input validation inside Screen Flow screens using component-level <validationRule> (formula + errorMessage), isRequired, cross-field rules on the second field, reactive components, and screen-level Decision fallbacks for cross-screen checks. Trigger keywords: screen flow validation rule, EndDate after StartDate validation in flow screen, block Next button until input valid. NOT for record-level Validation Rules — use admin/validation-rules. NOT for choosing screen components or overall screen UX — use flow/screen-flows.

15 repo stars
▌
API Governance And Rate Limits · pranavnagrecha bundle
Monitor and govern Salesforce API consumption: per-user limits, org allocation, lightning-rest limits, and backoff. NOT for designing new endpoints — use security/api-security-and-rate-limiting.

15 repo stars
▌
Error Handling In Integrations · pranavnagrecha bundle
Use this skill to design orchestration-layer error handling for Salesforce integrations — covering Platform Event replay recovery, dead-letter queue routing, cross-channel error notification patterns, circuit breaker design, and trigger suspension recovery. Triggers: integration error handling, Platform Event retry, integration dead letter queue, circuit breaker. NOT for Apex exception handling — use apex/exception-handling. NOT for HTTP error response contracts — use integration/api-error-handling-design. NOT for retry backoff patterns — use integration/retry-and-backoff-patterns.

15 repo stars
▌
OAUTH Flows And Connected Apps · pranavnagrecha bundle
Use when choosing or reviewing Salesforce OAuth flows and connected-app policy for integrations, including client credentials, JWT bearer, authorization code, device flow, scopes, and token lifecycle controls. Triggers: 'OAuth flow', 'connected app', 'client credentials', 'JWT bearer', 'refresh token', 'integration user'. NOT for creating and configuring the connected app or External Client App itself in Setup — use admin/connected-apps-and-auth. NOT for wiring the Named Credential and External Credential that carry the chosen flow — use integration/named-credentials-setup. NOT for a live token failure such as invalid_grant after refresh, or token rotation and revocation — use security/oauth-token-management.

15 repo stars
▌
Real Time Vs Batch Integration · pranavnagrecha bundle
When to use this skill: choosing between real-time (synchronous callouts, Platform Events, CDC, Pub/Sub API) and batch (Bulk API 2.0, scheduled ETL) integration patterns. Trigger keywords: should I use real-time or batch, how to sync high-volume data, when to use Platform Events vs Bulk API, integration latency vs volume tradeoff. NOT for choosing an ETL tool — use data/etl-vs-api-data-patterns. NOT for Batch Apex internals — use apex/batch-apex-patterns.

15 repo stars
▌
Webhook Signature Verification · pranavnagrecha bundle
Accept inbound webhooks (Stripe, GitHub, Slack, partner) and verify HMAC signatures in Apex REST — Crypto.verifyHMac platform verification, secret in Protected Custom Metadata, replay-window rejection. NOT for designing the receiver end to end — Sites routing, guest-user access, idempotency, the 5-second response window — use integration/webhook-inbound-patterns. NOT for signing a webhook Salesforce sends out — use integration/outbound-webhook-from-salesforce.

15 repo stars
▌
Omnistudio Deployment Datapacks · pranavnagrecha bundle
Use when exporting, importing, or version-controlling OmniStudio components using DataPacks via the OmniStudio DataPacks tool or vlocity CLI. Covers DataPack export/import, Git version control integration, CI/CD for OmniStudio. NOT for SFDX-based metadata deployment of non-OmniStudio components — use data/omnistudio-datapack-migration.

15 repo stars
▌
Org Hardening And Baseline Config · pranavnagrecha bundle
Use when defining or reviewing baseline org hardening settings, especially Security Health Check gaps, clickjack and browser protections, CSP and CORS governance, password/session policies, network restrictions, and release-update hygiene. NOT for feature-level app permissions or record-sharing design — use security/security-health-check.

15 repo stars
▌
AI Ethics And Governance Requirements · pranavnagrecha bundle
Use this skill when defining AI governance policies, designing human oversight workflows, documenting bias mitigation strategies, or meeting regulatory transparency requirements for Salesforce AI features. Trigger keywords: responsible AI, AI bias, AI audit trail, AI transparency, human-in-the-loop, AI risk inventory, AI disclosure. NOT for the MLOps pipeline or Policy-as-Code engine architecture — use architect/ai-governance-architecture. NOT for Trust Layer technical configuration — use agentforce/einstein-trust-layer.

15 repo stars
▌
Compliance Documentation Requirements · pranavnagrecha bundle
Use when setting up or auditing how compliance documentation is structured, collected, and preserved for regulatory audit in Salesforce FSC — covering KYC data collection workflows, AML screening integration setup, audit trail configuration, and regulatory reporting readiness. Triggers: KYC form setup, AML integration configuration, compliance data collection, audit trail setup, regulatory documentation workflow, Field Audit Trail configuration, Setup Audit Trail, Event Monitoring, Discovery Framework, FSC KYC objects, Identity Document setup, Party Identity Verification. NOT for security implementation, NOT for designing AML/KYC architecture (use architect/aml-kyc-process-architecture), NOT for configuring who can access deal or client data (use admin/compliant-data-sharing-setup).

15 repo stars
▌
Callout And Dml Transaction Boundaries · pranavnagrecha bundle
Use when diagnosing, preventing, or refactoring the 'You have uncommitted work pending' CalloutException caused by mixing DML and callouts in the same Apex transaction. Triggers: 'uncommitted work pending', 'callout after DML', 'DML between callouts'. NOT for the callout itself — use apex/callouts-and-http-integrations. NOT for rollback semantics — use apex/apex-savepoint-and-rollback.

15 repo stars
▌
Field Level Security In Async Contexts · pranavnagrecha bundle
Use when async Apex (Queueable, Batch, Schedulable, @future) needs to honor the originating user's field-level security but the job runs in a different security context than the user who initiated it. Triggers: 'fls bypassed in batch apex', 'queueable runs as wrong user', 'stripInaccessible in async returns full record', 'WITH USER_MODE evaluating against system user', 'scheduled apex sees fields the original user could not'. NOT for synchronous FLS enforcement — use apex/apex-stripinaccessible-and-fls-enforcement. NOT for the with/without sharing keyword decision — use apex/apex-with-without-sharing-decision.

15 repo stars
▌
API Led Connectivity Architecture · pranavnagrecha bundle
Use this skill when designing API-led connectivity architecture for Salesforce integrations — covering System/Process/Experience layer separation, governance policy (catalog, versioning, deprecation, rate limits), multi-consumer strategy, and Agentforce Agent Fabric integration. Trigger keywords: API-led connectivity, MuleSoft three-tier, System API, Process API, Experience API, integration layer governance, API versioning policy, Agent Fabric. NOT for Salesforce's own place in the layered model, or whether three layers are overkill - use integration/api-led-connectivity. NOT for HTTP error contracts - use integration/api-error-handling-design. NOT for retry backoff mechanics - use integration/retry-and-backoff-patterns.

15 repo stars
▌
Cpq Vs Standard Products Decision · pranavnagrecha bundle
Use when deciding whether to implement Salesforce CPQ or stay with standard Products and Pricebooks for quoting and pricing. Triggers: 'should we buy CPQ or use standard pricebooks', 'is CPQ worth the cost for our quoting process', 'product bundling without CPQ', 'guided selling vs manual product selection', 'complex pricing rules or multi-dimensional discounting'. NOT for designing bundles, the pricing waterfall or QCP once CPQ is chosen — use architect/cpq-architecture-patterns. NOT for picking a CPQ pricing method for a product — use admin/pricing-model-design. NOT for Revenue Cloud / RLM as the alternative to CPQ — use architect/revenue-cloud-architecture.

15 repo stars
▌
Crm Analytics Vs Tableau Decision · pranavnagrecha bundle
Use when deciding between CRM Analytics (formerly Einstein Analytics / Tableau CRM) and Tableau Desktop, Tableau Server, or Tableau Cloud for a Salesforce-centric analytics requirement. Triggers: 'CRM Analytics vs Tableau', 'which BI tool for Salesforce', 'Tableau for Salesforce data', 'Einstein Analytics vs Tableau', 'analytics platform decision', 'licensing comparison CRM Analytics Tableau', 'Tableau Next', 'Tableau+ for Salesforce'. NOT for implementation guidance on configuring CRM Analytics datasets, recipes, or Tableau workbooks — use admin/einstein-analytics-basics for that.

15 repo stars
▌
Health Cloud Multi Cloud Strategy · pranavnagrecha bundle
Use this skill when designing the license model, cloud topology, and org structure for a Salesforce Health Cloud implementation that involves more than one Salesforce cloud product (Experience Cloud patient portals, OmniStudio engagement flows, Marketing Cloud care campaigns, or Service Cloud case management). Trigger keywords: Health Cloud multi-cloud, patient portal licensing, Health Cloud Experience Cloud add-on, OmniStudio Health Cloud PSL, Marketing Cloud HIPAA BAA healthcare, multi-cloud healthcare org design. NOT for deciding whether the org serves a payer or a provider and which objects follow — use architect/payer-vs-provider-architecture. NOT for Health Cloud object and field definitions — use data/health-cloud-data-model.

15 repo stars
▌
Integration Security Architecture · pranavnagrecha bundle
Architecture-layer guidance for securing Salesforce integrations: mTLS mutual authentication, OAuth 2.0 flow selection, API gateway placement, IP allowlisting strategy on Hyperforce, and certificate lifecycle management. Trigger keywords: mTLS, mutual TLS, Hyperforce IP allowlisting, Salesforce Private Connect, certificate limit, integration authentication architecture. NOT for wiring mTLS onto one Named Credential — use integration/mutual-tls-callouts. NOT for Named Credential and External Credential field setup — use integration/named-credentials-setup. NOT for connected app registration and OAuth app setup — use admin/connected-apps-and-auth. NOT for Apex callout code patterns — use apex/callouts-and-http-integrations.

15 repo stars
▌
Marketing Cloud Vs Mcae Selection · pranavnagrecha bundle
Use this skill when selecting between Marketing Cloud Engagement (MCE) and Marketing Cloud Account Engagement (MCAE/Pardot) for a Salesforce marketing implementation. Trigger keywords: MCE vs MCAE, Marketing Cloud vs Pardot, B2B vs B2C marketing platform, which marketing cloud product, marketing platform selection. NOT for configuring an MCAE business unit and its Salesforce connector — use admin/mcae-pardot-setup. NOT for setting up MCE business units, roles and sender profiles — use admin/marketing-cloud-engagement-setup.

15 repo stars
▌
Multi Currency Sales Architecture · pranavnagrecha bundle
Use when designing or reviewing multi-currency behavior in Sales Cloud: advanced currency management (ACM), dated exchange rates, converted amount field behavior, roll-up summary currency handling, and reporting currency implications. Triggers: 'multi-currency reporting wrong amounts', 'dated exchange rates architecture', 'ACM converted amount fields'. NOT for enabling multi-currency itself - use data/multi-currency-and-advanced-currency-management.

15 repo stars
▌
Nonprofit Cloud Vs Npsp Migration · pranavnagrecha bundle
Nonprofit Cloud vs NPSP decision and migration: choose NPSP (managed package) or Nonprofit Cloud (native), plan data migration, Account Model differences, Program Management, fundraising. NOT for the go/stay decision alone, with no migration to plan - use architect/npsp-vs-nonprofit-cloud-decision. NOT for designing the NPC module and platform architecture - use architect/nonprofit-platform-architecture.

15 repo stars
▌
Org Edition And Feature Licensing · pranavnagrecha bundle
Use when evaluating which Salesforce features are available in a given org edition, determining whether a planned solution requires an add-on license, or investigating why a feature is unavailable in the current org. Triggers: 'feature not available in our edition', 'does Enterprise include Einstein', 'Unlimited vs Performance edition differences', 'we need Flow Orchestration but do not have it', 'what license do we need for Agentforce'. NOT for auditing and reclaiming unused seats to cut cost — use architect/license-optimization-strategy. NOT for ISV/AppExchange package license management and Trialforce — use devops/isv-license-management-and-trialforce.

15 repo stars
▌
Screen Flow Choice Component Selection · pranavnagrecha bundle
Use when picking which Screen Flow component collects a choice from users — Picklist, Radio Buttons, Radio Button Group (Summer '26), Multi-Select Picklist, Checkbox Group, Choice Lookup, Dependent Picklists, or Data Table — and which Choice resource (Choice, Record Choice Set, Picklist Choice Set) populates it. Covers single- vs multi-select semantics, the Loop/Transform incompatibility of the multi-select components, and set-size/searchability tradeoffs. NOT for building the choice-set resource internals from records or picklist fields (use flow/flow-dynamic-choices), NOT the deep configuration of one component (see flow/screen-flow-radio-button-group, flow/flow-data-tables), and NOT general screen UX, navigation, or input validation (see flow/screen-flows, flow/flow-screen-input-validation-patterns).

15 repo stars
▌
Change Data Capture Integration · pranavnagrecha bundle
Use this skill when setting up CDC to stream Salesforce record changes to external systems via CometD or Pub/Sub API. Covers change event channels, entity selection, event structure, replay ID management, gap events, and subscriber management. NOT for Apex CDC trigger subscribers (see apex/platform-events-apex). NOT for publishing custom business events (use integration/platform-events-integration).

15 repo stars
▌
Data Cloud Integration Strategy · pranavnagrecha bundle
Use this skill when designing or troubleshooting the data pipeline strategy for connecting source systems to Data Cloud — including ingestion API pattern selection (streaming vs. batch), connector type decisions. NOT for standard Salesforce integration patterns (use integration-patterns skill), not f — use data/data-cloud-data-streams.

15 repo stars
▌
Data Cloud Zero Copy Federation · pranavnagrecha bundle
Use this skill when configuring or troubleshooting Data Cloud Zero Copy / Lakehouse Federation against Snowflake, Databricks, BigQuery, or Redshift — including external Data Lake Object setup, query semantics, refresh/cache behavior, and federation versus physical ingestion. NOT for physical Ingestion API streaming/bulk — use integration/data-cloud-integration-strategy. NOT for CRM Analytics external connectors — use data/analytics-external-data. NOT for outbound Data Cloud activation — use integration/data-cloud-activation-development.

15 repo stars
▌
Idempotent Integration Patterns · pranavnagrecha bundle
Use when designing retry-safe integrations with Salesforce — including external ID upsert strategies, idempotency key management for inbound calls, Platform Event replay safety, and Outbound Message retry handling. NOT for stopping duplicate records users create, via matching and duplicate rules — use admin/duplicate-management. NOT for the retry schedule itself — exponential backoff, jitter, circuit breaker — use integration/retry-and-backoff-patterns.

15 repo stars
▌
Middleware Integration Patterns · pranavnagrecha bundle
Use when selecting or comparing middleware / iPaaS tools (MuleSoft, Dell Boomi, Workato, Informatica) for Salesforce connectivity, or when determining whether a scenario requires middleware at all versus native Salesforce capabilities. Triggers: 'which iPaaS should I use', 'MuleSoft vs Boomi vs Workato', 'when do I need middleware for Salesforce'. NOT for MuleSoft Anypoint Salesforce Connector configuration — use integration/mulesoft-salesforce-connector. NOT for API-led connectivity layer design — use integration/api-led-connectivity.

15 repo stars
▌
Outbound Messages And Callbacks · pranavnagrecha bundle
Use when implementing or troubleshooting Salesforce Outbound Messages — the workflow-triggered SOAP notification that pushes record field values to an external HTTPS endpoint, plus the listener's SOAP acknowledgment and the session-ID callback pattern. Trigger keywords: outbound message not delivering, configure outbound message endpoint, SOAP callback from Salesforce, workflow rule sends notification to external system, outbound message retry loop, acknowledgment SOAP response, session ID in outbound message. NOT for pushing JSON to a REST endpoint or a Flow/Apex-triggered push — use integration/outbound-webhook-from-salesforce. NOT for deciding between Outbound Messages, Platform Events and CDC in the first place — use integration/event-driven-architecture-patterns.

15 repo stars
▌
Platform Event Publish Patterns · pranavnagrecha bundle
Publishing Platform Events: EventBus.publish, PublishBehavior (PublishImmediately vs PublishAfterCommit), high-volume events, event allocation, publish failures, Change Data Capture comparison. NOT for consuming events in Apex — use apex/platform-events-apex. NOT for CDC events — use integration/change-data-capture-integration.

15 repo stars
▌
Platform Event Schema Evolution · pranavnagrecha bundle
Use when modifying the schema of a Platform Event that already has live publishers and subscribers — adding fields, deprecating fields, or splitting events. Triggers: 'add field to platform event without breaking subscribers', 'platform event versioning', 'evolve event schema safely', 'rename a field on a published event'. NOT for initial event design (use integration/platform-events-integration) or for Change Data Capture event schemas.

15 repo stars
▌
Lightning Navigation Dead Link Handling · pranavnagrecha bundle
Use when an LWC navigates via NavigationMixin to records or pages that may no longer exist, lack the user's access, or be permanently moved. Triggers: 'lightning navigation 404', 'navigate to deleted record', 'NavigationMixin error toast', 'graceful fallback when target page missing', 'permission denied on navigation'. NOT for ordinary NavigationMixin calls that work — use lwc/lwc-navigation-mixin. NOT for designing URL/deep-link routing — use lwc/navigation-and-routing.

15 repo stars
▌
Industries Cpq Vs Salesforce Cpq · pranavnagrecha bundle
Use this skill when comparing Industries CPQ (formerly Vlocity CPQ) with Salesforce CPQ (Revenue Cloud managed package) — covering feature parity, decision criteria, migration paths, and coexistence patterns. Trigger keywords: Vlocity. NOT for implementing, configuring, or debugging either CPQ product — use architect/industries-cloud-selection.

15 repo stars
▌
OAUTH Redirect And Domain Strategy · pranavnagrecha bundle
Design Connected App OAuth callback URLs, My Domain naming, Enhanced Domains cutover, and cross-environment redirect handling. Trigger keywords: oauth redirect uri, connected app callback, my domain, enhanced domains, sandbox url change. NOT for end-user login flow UX, Experience Cloud branding, or SAML-only SSO configuration — use admin/connected-app-troubleshooting.

15 repo stars
▌
Agentforce Agent Handoff Patterns · pranavnagrecha bundle
Use when designing how an Agentforce agent transfers the conversation to a human agent (Omni-Channel), to another bot/agent, or to an alternate workflow — including context package, deflection, escalation triggers, and user messaging. Triggers: 'agent to human handoff', 'agentforce escalate to omni channel', 'agent to agent handoff', 'transfer conversation with context', 'agent deflection fallback'. NOT for topic scope and selector design — use agentforce/agent-topic-design. NOT for the overall Einstein Bot plus Agentforce estate topology — use architect/conversational-ai-architecture.

15 repo stars
▌
Agentforce Custom Lightning Types · pranavnagrecha bundle
Use when overriding the default UI of an Agentforce agent action's Apex input or output with your own Lightning web components via a LightningTypeBundle (schema.json + editor.json/renderer.json, lightning__AgentforceInput / lightning__AgentforceOutput targets, the @apexClassType binding). NOT for standard agent actions with primitive inputs/outputs (only Apex-class input/output can be overridden), NOT for Flow screen custom property editors (use flow/flow-custom-property-editors), and NOT for general LWC-in-Lightning-page work (use lwc/* skills).

15 repo stars
▌
Employee Hr Service Agent Rollout · pranavnagrecha bundle
Use when an org is rolling out an Agentforce-based HR / Employee Service agent for self-service workflows like leave requests, benefits questions, onboarding tasks, and time-off balance lookups. Covers Employee Agent licensing posture, knowledge-base grounding for HR policy, integration patterns with HRIS systems of record (Workday, ADP, BambooHR) — read-only vs read-write trade-offs, employee-vs-manager visibility model, PII handling under the Einstein Trust Layer, surface-placement decision (in-Salesforce vs Slack-first vs Teams-first), and rollout measurement (deflection, first-response time, employee CSAT). Triggers: 'we want an HR self-service agent for leave and benefits', 'employees keep emailing HR for time-off balance — can Agentforce answer that?', 'roll out Employee Service agent in Slack', 'wire HRIS into our Agentforce HR bot', 'how do we handle PII when the agent reads Workday', 'measure deflection on the HR agent we just launched'. NOT for general Agentforce agent build mechanics (use agentforc

15 repo stars
▌
Deployment Automation Architecture · pranavnagrecha bundle
Deployment automation architecture on Salesforce: pipeline orchestration, branch strategy, environment topology, quality gates, release trains. Selecting between Copado, Gearset, Flosum, and native SFDX + GitHub Actions. NOT for cloud-specific deploy mechanics (Industries, Marketing Cloud, Data Cloud) — use architect/cloud-specific-deployment-architecture. NOT for CI/CD tool tutorials.

15 repo stars
▌
Metadata Coverage And Dependencies · pranavnagrecha bundle
Assessing metadata type coverage across Salesforce deployment channels (Metadata API, SFDX, unlocked packages, managed packages) and mapping component dependency graphs using Tooling API MetadataComponentDependency. Use when planning packaging strategies, evaluating deployment risk, or performing impact analysis before component deletion. Trigger keywords: metadata coverage report, dependency graph, MetadataComponentDependency, impact analysis, unsupported metadata types, packaging eligibility. NOT for a deployment that already failed on an unsupported type — use devops/metadata-api-coverage-gaps. NOT for writing package.xml or running retrieve and deploy — use apex/metadata-api-and-package-xml.

15 repo stars
▌
Multi Channel Service Architecture · pranavnagrecha bundle
Use when designing a unified multi-channel service strategy spanning phone (Service Cloud Voice), email (Email-to-Case), chat (Messaging for In-App/Web), social, and SMS with Omni-Channel routing. Triggers: channel prioritization, unified routing across channels, service channel migration, multi-channel capacity planning. NOT for end-to-end contact centre design - use architect/service-cloud-architecture. NOT for enabling Omni-Channel and creating Service Channels - use admin/omni-channel-routing-setup.

15 repo stars
▌
Isv License Management And Trialforce · pranavnagrecha bundle
Use when an ISV partner is wiring license enforcement, trial provisioning, or feature-flag distribution into a managed package — covers License Management App (LMA) install and registration, Lead/License object. NOT for general managed-package version creation, ancestor pinning, or PostInstall handler design — use devops/managed-package-development.

15 repo stars
▌
Outbound Webhook From Salesforce · pranavnagrecha bundle
Use when Salesforce must POST a webhook to a third-party endpoint after a record change — with signed payloads, retries, dead-lettering, rate limits, and idempotency. Covers design choice between Outbound Message, Flow HTTP Callout, Apex Queueable callout, and Event Relay. NOT for receiving a webhook INTO Salesforce from an external system — use integration/webhook-inbound-patterns. NOT for the Workflow-triggered SOAP Outbound Message and its listener contract — use integration/outbound-messages-and-callbacks.

15 repo stars
▌
Salesforce Functions Replacement · pranavnagrecha bundle
Salesforce Functions is retired (EOL Jan 2025). This skill maps Functions workloads to replacements: Heroku (with Hyperforce), external containers, Apex (where viable), Agentforce Actions, external compute via Named Credentials. NOT for Lambda / Azure Functions tutorials — use agentforce/einstein-bots-to-agentforce-migration.

15 repo stars
▌
Dataraptor Transform Optimization · pranavnagrecha bundle
Use when DataRaptor Transform operations are slow, hit governor limits, or use Apex where formula fields would suffice. Covers formula vs Apex expressions, bulk transform sizing, and chained transform composition. Triggers: 'dataraptor transform slow'. NOT for DataRaptor Extract or Load performance — use omnistudio/dataraptor-patterns.

15 repo stars
▌
Service Account Credential Rotation · pranavnagrecha bundle
Use when designing credential rotation for integration users, connected apps, named credentials, and OAuth client secrets in Salesforce. Covers rotation cadence, zero-downtime handover, secret storage, and detection of stale credentials. Triggers: 'rotate integration user. NOT for end-user password policies — use admin/connected-apps-and-auth.

15 repo stars
▌
Shield Event Log Retention Strategy · pranavnagrecha bundle
Use when designing Salesforce Shield Event Monitoring retention, SIEM routing, and storage-tier strategy — which event types to keep, for how long, where, and how to answer audit queries across hot/warm/cold tiers. Triggers: 'shield event log retention'. NOT for enabling Shield (see salesforce-shield-deployment) — use security/event-monitoring.

15 repo stars
▌
Agent Action Input Slot Extraction · pranavnagrecha bundle
Use when designing how an Agentforce agent extracts structured input parameters (slots) from a user's natural-language utterance to invoke an action. Triggers: 'agent extract date from user', 'agent action argument extraction', 'agentforce slot filling', 'agent invocable input mapping', 'agent fails to fill required parameter'. NOT for action authoring (use agentforce/agent-actions) or for prompt-template variable binding (use agentforce/prompt-builder-templates).

15 repo stars
▌
High Volume Sales Data Architecture · pranavnagrecha bundle
Use when designing or reviewing Salesforce orgs with large Opportunity and Account volumes, including archival strategy, report performance, data skew prevention, SOQL tuning for sales queries, and index planning. Triggers: 'opportunity table is slow', 'account ownership skew', 'sales report timing out', 'archive old opportunities'. NOT for org-wide LDV design on non-sales objects - use architect/large-data-volume-architecture. NOT for tuning one query or reading a Query Plan - use data/soql-query-optimization.

15 repo stars
▌
Industries Integration Architecture · pranavnagrecha bundle
Use when designing or reviewing the integration layer between Salesforce Industries clouds (Insurance, Communications, Energy & Utilities) and vertical backend systems such as policy administration systems, BSS/OSS platforms, or Customer Information Systems (CIS). NOT for calling a named Industries API (TMF679, InsurancePolicy Connect) — use omnistudio/industries-api-extensions. NOT for FSC data model or module licensing — use architect/insurance-cloud-architecture.

15 repo stars
▌
Omnistudio Vs Standard Architecture · pranavnagrecha bundle
Pick and then document the OmniStudio runtime path an architect has to live with: Standard Runtime (natively embedded, Spring '25+, no namespace) versus the legacy vlocity_ins__ / industries__ managed package and the migration debt every new component on it accrues — gated first on whether the org actually holds a qualifying Industries license. Ends in a written ADR that records the license gate, the runtime path, team ramp cost, and the fallback to Screen Flow + LWC for a guided wizard when OmniStudio is not available. NOT for the OmniStudio-vs-standard-tooling capability matrix itself (use architect/omnistudio-vs-standard-decision), NOT for OmniScript, FlexCard, or Integration Procedure implementation.

15 repo stars

1,086 published skills · page 2 of 11