PranavNagrecha

@pranavnagrecha source repo

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

▌
Lightning Experience Transition · pranavnagrecha bundle
Use when planning, sequencing, or troubleshooting an org-wide migration from Salesforce Classic to Lightning Experience. Covers the LEX Transition Assistant Readiness Check, asset triage matrix (Visualforce, JavaScript buttons, page layouts, Knowledge, email templates, list views, AppExchange), pilot/wave rollout sequencing, end-user adoption telemetry, and cutover criteria. Triggers: 'lightning experience transition', 'classic to lightning migration plan', 'LEX readiness check', 'why are some users still on Classic', 'turning on Lightning for everyone'. NOT for individual asset migrations like a single VF page (use lwc/visualforce-to-lwc-migration), a single JavaScript button (use admin/custom-button-to-action-migration), or Knowledge article migration (use admin/knowledge-classic-to-lightning) — this skill orchestrates the program. NOT for Lightning App Builder page design (use admin/lightning-app-builder-advanced).

15 repo stars
▌
Patient Engagement Requirements · pranavnagrecha bundle
Use this skill when defining patient engagement portal requirements for Health Cloud: appointment scheduling, secure in-portal messaging, health assessments, patient education, and self-service features. NOT for care team workflows, SDOH barriers and care gaps — use admin/care-coordination-requirements. NOT for patient portal licensing and cloud topology — use architect/health-cloud-multi-cloud-strategy.

15 repo stars
▌
Picklist Field Integrity Issues · pranavnagrecha bundle
Use when picklist data quality has degraded: unrestricted picklists accepting garbage API values, dependent picklist relationships bypassed by integrations, record type picklist value mappings drifting out of sync, or orphaned values appearing in reports. NOT for the value-deactivation runbook or the API-name-vs-label trap — use admin/picklist-data-integrity. NOT for initial picklist creation or Global Value Set design — use admin/picklist-and-value-sets. NOT for record type configuration itself — use admin/record-types-and-page-layouts.

15 repo stars
▌
Program Outcome Tracking Design · pranavnagrecha bundle
Design guidance for program outcome measurement in Salesforce nonprofit orgs: logic model structure, indicator taxonomy, impact reporting design, and grant compliance reporting using NPSP Program Management Module (PMM) or Nonprofit Cloud (NPC) Outcome Management. NOT for configuring PMM programs, cohorts and service deliveries - use admin/npsp-program-management. NOT for setting up grant tracking, funding awards and disbursements - use admin/grant-management-setup.

15 repo stars
▌
Sandbox Post Refresh Automation · pranavnagrecha bundle
Automating post-sandbox-refresh cleanup via the `SandboxPostCopy` interface — the Apex class that runs ONCE after a sandbox refresh or clone completes, before users can log in. Used to mask emails, deactivate users, scrub integration endpoints, disable scheduled jobs, and reapply per-environment configuration the metadata copy doesn't carry. Covers the interface contract (`runApexClass` setting, `SandboxContext` parameter, single-execution semantics), the email-masking pattern that stops sandbox tests emailing production addresses, and the refresh runbook checklist. NOT for choosing sandbox type or refresh cadence — use admin/sandbox-strategy. NOT for re-seeding reference data after a refresh — use data/sandbox-refresh-data-strategies.

15 repo stars
▌
System Field Behavior And Audit · pranavnagrecha bundle
Use when practitioners need to understand system-managed fields (CreatedDate, LastModifiedDate, SystemModstamp, CreatedById, LastModifiedById, IsDeleted) — their update behavior, indexing, and queryability. Triggers: 'difference between SystemModstamp and LastModifiedDate', 'how to query deleted records', 'set CreatedDate during data migration', 'why does LastModifiedDate not match SystemModstamp', 'Create Audit Fields permission'. NOT for a field's value-change history — use data/field-history-tracking. NOT for Shield Field Audit Trail — use security/field-audit-trail.

15 repo stars
▌
Agent Deployment Checklist · pranavnagrecha bundle
Canonical go-live checklist for Agentforce deployments with rehearsed rollback and stakeholder sign-off records. NOT for the technical pre-prod verification behind those sign-off rows — cost telemetry, rate limits, canary rollout, latency benchmarks — use agentforce/agentforce-production-readiness-checklist. NOT for general Salesforce release management — use devops/release-management.

15 repo stars
▌
Einstein Copilot For Sales · pranavnagrecha bundle
Sales-specific AI features in Sales Cloud: Einstein Opportunity Scoring setup and optimization, Einstein Activity Capture configuration, AI email generation, Pipeline Inspection AI insights, and Einstein Relationship Insights. NOT for the license check and enablement sequence before any of these are turned on — use agentforce/agentforce-sales-ai-setup. NOT for the Service Cloud equivalents such as Case Classification and Work Summaries — use agentforce/einstein-copilot-for-service.

15 repo stars
▌
Prompt Template Versioning · pranavnagrecha bundle
Lifecycle management for Prompt Builder templates: version, test, promote, roll back via CMDT-backed bindings. NOT for source-control layout, model-version pinning, or versioning agent topic prompts — use agentforce/agentforce-prompt-versioning. NOT for authoring a template in Prompt Builder — use agentforce/prompt-builder-templates.

15 repo stars
▌
RAG Patterns In Salesforce · pranavnagrecha bundle
Grounding Agentforce agents with retrieved knowledge using Data Cloud vector search: RAG pipeline design, vector search index configuration, chunking and embedding strategy, and how retrieved context flows through the Einstein Trust Layer into prompts. NOT for the Query API, Data Cloud access tokens, or Easy vs Advanced index mechanics — use agentforce/data-cloud-vector-search-dev. NOT for structured DMO retrievers, sharing enforcement at retrieval time and citations — use agentforce/data-cloud-grounding-for-agentforce.

15 repo stars
▌
Apex Class Decomposition Pattern · pranavnagrecha bundle
When and how to split an Apex class into Domain / Service / Selector layers using this repo's lightweight base classes (BaseDomain, BaseService, BaseSelector). Covers splitting signals, ordering of extraction, and naming conventions. NOT for a full fflib migration — use apex/fflib-enterprise-patterns. NOT for choosing a trigger handler framework — use apex/trigger-framework.

15 repo stars
▌
Apex Dynamic Soql Binding Safety · pranavnagrecha bundle
Safe construction of dynamic SOQL — Database.query bind variables (:varName, API 60+ semantics), Database.queryWithBinds(query, Map<String,Object>, AccessLevel) (API 55+), field-name allowlisting, ORDER BY direction whitelist, LIMIT/OFFSET typing, and WITH USER_MODE interaction (WITH SECURITY_ENFORCED was removed in API 67.0). NOT for reviewing a query for injection or CRUD/FLS generally — use apex/soql-security. NOT for Schema.describe and runtime type inspection — use apex/dynamic-apex.

15 repo stars
▌
Debug Logs And Developer Console · pranavnagrecha bundle
Use when setting up debug logs and trace flags, reading Apex log output and log levels, running queries in the Developer Console, executing anonymous Apex, or using the Apex Replay Debugger in VS Code. Triggers: 'set up debug log', 'Developer Console', 'anonymous Apex', 'trace flag', 'Apex Replay Debugger'. NOT for production logging strategy or custom structured logging frameworks — use apex/debug-and-logging. NOT for writing test classes — use apex/test-class-standards.

15 repo stars
▌
Governor Limit Recovery Patterns · pranavnagrecha bundle
Recovering from and preventing Apex governor limit errors: proactive Limits class checkpoints, savepoint-based partial recovery, BatchApexErrorEvent scope recovery, CPU timeout analysis, limit-safe coding patterns. Use when diagnosing LimitException failures or designing limit-safe Apex. NOT for org-level capacity planning — use architect/limits-and-scalability-planning. NOT for bulkification patterns — use apex/governor-limits.

15 repo stars
▌
Npsp Trigger Framework Extension · pranavnagrecha bundle
Use when extending the NPSP Trigger-Driven Trigger Management (TDTM) framework with custom Apex handler classes — covering class authorship, DmlWrapper return patterns, Trigger_Handler__c registration, load order, recursion guards, and test isolation. NOT for trigger-handler framework design outside NPSP — use apex/trigger-framework. NOT for NPSP vs Nonprofit Cloud (NPC) — use architect/npsp-vs-nonprofit-cloud-decision.

15 repo stars
▌
Analytics Data Architecture · pranavnagrecha bundle
Use this skill when designing CRM Analytics dataset architecture, planning dataflow or Recipe ELT strategies, implementing incremental extraction patterns, or integrating external data lakes (Snowflake, BigQuery, Redshift). Trigger keywords: CRM Analytics dataset design, dataflow performance, Recipe incremental, remote connection data lake, analytics ELT strategy, dataset row limits. NOT for the External Data API or live-dataset setup itself — use data/analytics-external-data. NOT for authoring dataflow node JSON — use admin/analytics-dataflow-development. NOT for building a recipe's join, bucket and formula nodes — use admin/analytics-recipe-design.

15 repo stars
▌
CI CD Pipeline Architecture · pranavnagrecha bundle
Use when designing or reviewing the end-to-end stage sequence, promotion strategy, and quality gates for a Salesforce CI/CD pipeline. Trigger keywords: pipeline stages, promotion strategy, quality gate, deployment gate, CI validation sandbox, staging environment, pipeline design, release strategy, rollback strategy, environment topology. NOT for configuring an individual CI tool (GitHub Actions, GitLab CI, Jenkins) — use devops/github-actions-for-salesforce or devops/gitlab-ci-for-salesforce. NOT for Apex test configuration in CI — use devops/continuous-integration-testing. NOT for DevOps Center setup or work item promotion — use devops/devops-center-pipeline.

15 repo stars
▌
Cross Cloud Data Deployment · pranavnagrecha bundle
Cross-cloud data deployment: designing the data handoff when an implementation spans Sales Cloud, Service Cloud, Marketing Cloud, Data Cloud, Commerce Cloud. Shared keys, identity resolution, sync vs event, CDC, Data Cloud as hub. NOT for configuring the Data Cloud identity-resolution ruleset itself — use admin/data-cloud-identity-resolution. NOT for designing Data Cloud DMOs and their relationships — use data/data-cloud-data-model-objects. NOT for integration pattern selection — use the integration-pattern-selection decision tree.

15 repo stars
▌
Government Cloud Compliance · pranavnagrecha bundle
Use when architecting or assessing a Salesforce Government Cloud org — covering FedRAMP High authorization, Hyperforce GovCloud on AWS GovCloud regions, GovCloud Plus feature set, data residency and US-only data processing, FISMA continuous monitoring, CMS ARC-AMPE controls, NIST 800-53 control mapping, compliance automation patterns, DoD IL2/IL4/IL5 considerations, and multi-org architecture in government deployments. Triggers: FedRAMP, Government Cloud, GovCloud Plus, Hyperforce government, ATO, FISMA, NIST 800-53, CMS ARC-AMPE, IL4 IL5 DoD, data residency US government, compliance evidence automation. NOT for general security reviews (use architect/security-architecture-review or security/* skills). NOT for platform encryption in isolation (use security/platform-encryption). NOT for general Well-Architected reviews (use architect/well-architected-review).

15 repo stars
▌
Health Cloud Data Residency · pranavnagrecha bundle
Use this skill when architecting Health Cloud orgs that must satisfy geographic data residency, HIPAA, GDPR, or national health-data regulations on Hyperforce — scoping the HIPAA BAA, mapping transient processing exceptions, and the features that require separate compliance addenda. NOT for choosing a Hyperforce region or planning a Hyperforce migration outside healthcare — use architect/hyperforce-architecture. NOT for Shield encryption and HIPAA technical safeguards — use architect/hipaa-compliance-architecture.

15 repo stars
▌
Marketing Data Architecture · pranavnagrecha bundle
Use this skill when designing or evaluating the overall Marketing Cloud data architecture — covering Data Extension schema design (sendable vs. non-sendable), Contact Key/SubscriberKey linkage across All Subscribers and attribute DEs, Data Relationship definitions for AMPscript Lookup and Query Activity joins, and CRM-to-MC data flow patterns (MC Connect Synchronized DEs vs. SFTP file imports). Trigger keywords: MC data model, relational data extensions, CRM to Marketing Cloud data flow, Contact Key linkage, data architecture, sendable DE design, normalized DE model, SFTP import strategy, synchronized data extension architecture. NOT for one Data Extension's keys and retention — use data/data-extension-design. NOT for diagnosing MC Connect synchronized DE sync failures — use data/marketing-cloud-data-sync.

15 repo stars
▌
Omni Channel Capacity Model · pranavnagrecha bundle
Designing Omni-Channel capacity models for service orgs: agent capacity allocation, channel weighting (cases, chats, calls), skills matrix design, overflow strategy, presence configuration, and interruptible work patterns. Use when planning capacity units, defining Service Channel weights, or designing agent skills-based routing capacity. NOT for enabling Omni-Channel, creating Service Channels or routing rules - use admin/omni-channel-routing-setup. NOT for cross-channel strategy and channel-to-feature mapping - use architect/multi-channel-service-architecture.

15 repo stars
▌
Platform Selection Guidance · pranavnagrecha bundle
Use when choosing which Salesforce platform capability to use for a requirement — covering metadata storage (Custom Metadata vs Custom Settings vs Custom Objects), UI framework (LWC vs Aura), integration approach (Platform Events vs Change Data Capture vs Outbound Messaging), and data extension (OmniStudio vs standard automation). Triggers: custom metadata vs custom settings, LWC vs Aura, which salesforce feature to use, platform events vs change data capture, omnistudio vs flow. NOT for automation-specific tool selection between Flow / Apex / Workflow (use admin/process-automation-selection) or for implementing the chosen platform feature.

15 repo stars
▌
Commerce Order History Migration · pranavnagrecha bundle
Use when migrating historical order records into Salesforce Order Management — covers the required object creation sequence (Order > OrderDeliveryGroup > OrderItem > OrderSummary), LifeCycleType=Unmanaged for historical orders, and OrderSummary creation via ConnectAPI. NOT for CPQ legacy order, contract and asset upload using SBQQ objects — use data/historical-order-migration. NOT for live order processing, fulfilment, returns or cancellations — use admin/commerce-order-management.

15 repo stars
▌
Continuous Integration Testing · pranavnagrecha bundle
Use when configuring Apex test execution in CI/CD pipelines, choosing test levels for deployments, parsing test results, or troubleshooting code coverage in automated builds. Triggers: 'RunLocalTests', 'RunSpecifiedTests', 'sf project deploy', 'code coverage CI', 'JUnit test results'. NOT for standing up a GitHub Actions workflow — use devops/github-actions-for-salesforce. NOT for Apex test class design — use apex/test-class-standards. NOT for LWC Jest testing — use lwc/lwc-testing.

15 repo stars
▌
Destructive Changes Deployment · pranavnagrecha bundle
Managing destructiveChanges.xml manifests for safe metadata deletion in Salesforce deployments. Use when deleting metadata components via Metadata API or sf CLI. Covers pre vs post destructive manifests, safe deletion sequencing, dependency handling. NOT for package.xml basics (use apex/metadata-api-and-package-xml). NOT for basic deployment setup (use devops/change-set-deployment).

15 repo stars
▌
Performance Testing Salesforce · pranavnagrecha bundle
Use when planning or executing load tests, stress tests, or performance benchmarks against a Salesforce org. Covers Salesforce Scale Test, third-party tools (JMeter, BlazeMeter, k6), API throughput testing, Experience Page Time. NOT for Apex unit test performance assertions, LWC Jest tests, or query tuning — use data/soql-query-optimization.

15 repo stars
▌
Sandbox Data Isolation Gotchas · pranavnagrecha bundle
Use this skill when a sandbox has reached out to production systems, sent emails to real users, run live scheduled jobs, or leaked sensitive data after a refresh. Triggers: 'sandbox sent email to real customers', 'scheduled job fired against production API', 'integration hit live system from sandbox', 'Contact email not changed to .invalid', 'SandboxPostCopy did not run'. NOT for masking or scrubbing PII in the copied records — use security/sandbox-data-masking. NOT for refresh cadence or sandbox templates — use devops/sandbox-refresh-and-templates. NOT for picking a sandbox type — use admin/sandbox-strategy.

15 repo stars
▌
Flow Error Notification Patterns · pranavnagrecha bundle
Use when Flow fault emails are noisy, repeated, going to the wrong person, or need to go somewhere other than email. Fault-path design and error notification for Salesforce Flow — what the default unhandled-fault email contains, when to add a Fault path explicitly, how `$Flow.FaultMessage` works, and how to route errors to a real notification channel (email alert, Apex-published Platform Event, custom log object) instead of the org-default 'apex exception email recipient'. Covers the screen-flow user-visible error vs record-triggered-flow silent failure difference and suppressing noisy expected-rejection paths. Triggers: 'flow keeps sending me error emails', 'too many flow error emails', 'stop flow fault emails', 'change who receives flow error emails', 'route flow errors to Slack or a custom log object', 'apex exception email recipient'. NOT for how to build the Fault connector itself — use flow/fault-handling. NOT for triaging one failure that already happened — use flow/flow-runtime-error-diagnosis.

15 repo stars
▌
Flow Platform Events Integration · pranavnagrecha bundle
Use when Flow is a Platform Event publisher, subscriber, or both. Triggers: 'publish platform event from flow', 'platform-event-triggered flow', 'high-volume platform event', 'publish after commit vs immediate', 'PE subscriber error handling', 'integration fan-out from save'. NOT for Change Data Capture — use integration/change-data-capture-integration. NOT for async work that needs no pub/sub — use flow/scheduled-flows.

15 repo stars
▌
Flow Runtime Context And Sharing · pranavnagrecha bundle
Flow runtime sharing context — run in user vs system mode, record access in Flow. Triggers: Flow sharing, run in system mode, Flow user context. NOT for Apex sharing declarations — use apex/apex-with-without-sharing-decision.

15 repo stars
▌
Scheduled Flow Not Running Debug · pranavnagrecha bundle
Use when a Schedule-Triggered Flow is configured but is not firing at the expected time, or appears active in Setup → Flows but never produces output. Covers where scheduled flows actually surface (Setup → Scheduled Jobs, NOT Setup → Apex Jobs), the AsyncApexJob / CronTrigger evidence trail, top causes (deactivated scheduling user, daylight-savings transitions, time-zone mismatches between scheduling user and org, fault-paths that quietly stop the schedule, daily async-Apex limit pressure), and recovery steps (re-schedule via Apex, run the flow manually with the same input, switch the scheduling user). Triggers: 'how do I schedule a flow to run every monday', 'scheduled flow not firing', 'flow scheduled but no execution', 'scheduled flow stopped working last week', 'monday 6am scheduled flow did not run after dst change'. NOT for designing a new scheduled flow's record scope or idempotency (use flow/scheduled-flows), NOT for record-triggered Scheduled Paths that don't fire (use flow/flow-time-based-patterns),

15 repo stars
▌
API Error Handling Design · pranavnagrecha bundle
Designing HTTP error classification, RFC 7807-style error payload structure, and client-side error parsing for Salesforce REST/SOAP integrations and custom Apex REST endpoints. Use when deciding which HTTP status codes an endpoint returns and how callers classify them. NOT for retry mechanics or circuit breakers (use integration/retry-and-backoff-patterns) — use architect/integration-framework-design.

15 repo stars
▌
Azure Salesforce Patterns · pranavnagrecha bundle
Azure integration patterns for Salesforce — pick between the native Azure Service Bus Connector, Azure Functions / API Management as the callout target, Data 360 (Data Cloud) Azure Blob Storage ingestion, Azure AD as IdP via SAML/OIDC, and the Power Platform Salesforce connector. Decision matrix + auth model guidance (Named Credentials with External Credentials, OAuth 2.0 client-credentials, JWT Bearer, SAML). NOT for AWS — use integration/aws-salesforce-patterns. NOT for point-to-point vs hub-and-spoke — use admin/integration-pattern-selection.

15 repo stars
▌
Connect REST API Patterns · pranavnagrecha bundle
Use Connect REST API for Chatter, feeds, communities, and CMS content instead of querying underlying SObjects. NOT for custom business object CRUD — use integration/graphql-api-patterns.

15 repo stars
▌
Event Relay Configuration · pranavnagrecha bundle
Use when forwarding Salesforce Platform Events or Change Data Capture to AWS EventBridge via Event Relay. Covers Named Credential + Connection setup, channel selection, event filter design, replay handling. NOT for consuming external events in Salesforce (see pub-sub-api or salesforce-connect) — use integration/aws-salesforce-patterns.

15 repo stars
▌
Manufacturing Cloud Setup · pranavnagrecha bundle
Use this skill when configuring Salesforce Manufacturing Cloud — including Sales Agreement setup, Account-Based Forecasting (ABF) recalc jobs, run-rate management, Rebate Management programs, channel inventory tracking. NOT for general Sales Cloud opportunity-to-order flow (use standard Opportunity / Order) — use admin/rebate-management-setup.

15 repo stars
▌
Omniscript Design Patterns · pranavnagrecha bundle
Use when designing or reviewing OmniScripts for guided experiences, step structure, branching, save/resume, and the boundary between OmniScript, Integration Procedures, DataRaptors, and custom LWCs. Triggers: 'omniscript design', 'too many steps in omniscript', 'save and resume omniscript', 'branching in omniscript', 'when should this be an integration procedure'. NOT for deep Integration Procedure design — use omnistudio/integration-procedures. NOT for DataRaptor design — use omnistudio/dataraptor-patterns.

15 repo stars
▌
Omnistudio Lwc Integration · pranavnagrecha bundle
Use when embedding OmniScripts in Lightning Web Components, registering custom LWC elements inside OmniScript screens, or calling OmniScript/Integration Procedures from LWC. Triggers: embed omniscript in LWC, custom LWC element in OmniScript, call OmniScript from Lightning page, omnistudio-omni-script tag. NOT for standalone LWC development when OmniStudio is not involved - use lwc/component-communication.

15 repo stars
▌
Privileged Access Management · pranavnagrecha bundle
Design just-in-time elevation, break-glass accounts, and audit trails for Modify All Data / System Admin / Customize Application permissions. NOT for regular permission set design — use admin/permission-set-architecture.

15 repo stars
▌
Recaptcha And Bot Prevention · pranavnagrecha bundle
Use when configuring reCAPTCHA on Web-to-Case, Web-to-Lead, Experience Cloud forms, or Headless Identity flows, or when designing bot-mitigation strategies for Salesforce public-facing surfaces. Triggers: 'enable reCAPTCHA on Web-to-Case'. NOT for AppExchange security review or session-level login policies — use security/session-management-and-timeout.

15 repo stars
▌
Salesforce Shield Deployment · pranavnagrecha bundle
Roll out Shield (Platform Encryption + Event Monitoring + Field Audit Trail) end-to-end, sequencing feature enablement to avoid data lockout. NOT for Classic Encryption or general PE design — use architect/salesforce-shield-architecture.

15 repo stars
▌
Xss And Injection Prevention · pranavnagrecha bundle
Use when writing or reviewing Visualforce pages, Apex controllers, or LWC components that output user-supplied data, build dynamic queries, or construct HTTP responses. Triggers: 'XSS in Visualforce', 'SOQL injection vulnerability'. NOT for Apex CRUD/FLS enforcement, Shield encryption, or AppExchange security review — use apex/soql-security.

15 repo stars
▌
Analytics Permission And Sharing · pranavnagrecha bundle
Configure CRM Analytics (formerly Einstein Analytics) app sharing, dataset-level permissions, row-level security predicates, sharing inheritance, and license assignment. Trigger keywords: CRM Analytics security, row-level security predicate, dataset permissions, analytics sharing inheritance, Analytics Plus license. NOT for OWD and sharing rules — use admin/sharing-and-visibility. NOT for predicate design across many datasets — use architect/analytics-security-architecture.

15 repo stars
▌
Analytics Requirements Gathering · pranavnagrecha bundle
Use this skill to elicit, document, and validate CRM Analytics requirements — covering data source mapping (Salesforce object sync vs external connector vs Data Cloud), transformation needs, audience-specific lens or dashboard views, and drill-down path specifications — before any dataset or dashboard is built. Trigger keywords: CRM Analytics requirements, analytics data source mapping, CRM Analytics audience requirements, analytics visualization requirements. NOT for the formula and target behind each KPI — use admin/analytics-kpi-definition. NOT for building the dashboard once requirements are agreed — use admin/analytics-dashboard-design.

15 repo stars
▌
Change Management And Deployment · pranavnagrecha bundle
Use when planning, reviewing, or troubleshooting Salesforce metadata releases and admin deployment processes. Triggers: 'change set', 'deployment plan', 'rollback', 'DevOps Center', 'SFDX deploy', 'release checklist', 'production deployment'. NOT for change set upload mechanics — use devops/change-set-deployment. NOT for scoring release risk up front — use admin/deployment-risk-assessment.

15 repo stars
▌
Classic Email Template Migration · pranavnagrecha bundle
Migrating Classic email templates (Text, HTML with Letterhead, Custom HTML, Visualforce email) to Lightning Email Templates (LET) and the Email Template Builder. Covers merge-field translation, Letterhead-to-Enhanced-Letterhead conversion, Visualforce email retention strategy, folder reorganization, sender-context (OrgWideEmailAddress) preservation, and downstream Email Alert / Process Builder / Flow rewiring. NOT for transactional Apex email sending (use apex/apex-outbound-email-patterns) or marketing email broadcasts (use Marketing Cloud / Account Engagement).

15 repo stars
▌
Configuration Workbook Authoring · pranavnagrecha bundle
Author the Salesforce Configuration Workbook — the structured, reviewable handoff document an admin uses to execute a feature across Objects/Fields, Page Layouts, Profiles/PSGs, Sharing, Validation, Automation, List Views, Reports, Integrations, and Data. Triggers: 'salesforce configuration workbook', 'admin handoff document', 'implementation workbook'. NOT for object design itself (use admin/custom-field-creation, admin/lookup-and-relationship-design, agents/object-designer/AGENT.md), NOT for permission set design (use admin/permission-set-architecture, agents/permission-set-architect/AGENT.md), NOT for Flow construction (use skills/flow/* and agents/flow-builder/AGENT.md), and NOT for the deployment manifest (use skills/devops/metadata-api-retrieve-deploy).

15 repo stars
▌
Field Dependency And Controlling · pranavnagrecha bundle
Dependent picklists in Salesforce: controlling field (picklist or checkbox), dependent picklist, valueSettings matrix in metadata, API behavior via SOAP/REST, LWC lightning-combobox with dependency. NOT for creating picklist fields or Global Value Sets and replacing retired values - use admin/picklist-and-value-sets. NOT for filtering picklist values per record type or layout - use admin/record-types-and-page-layouts.

15 repo stars
▌
Global Actions And Quick Actions · pranavnagrecha bundle
Use this skill when configuring object-specific quick actions or global actions in Salesforce: choosing between action types, editing action layouts, pre-filling fields with predefined values, and adding actions to Lightning page layouts or mobile navigation. Trigger keywords: quick action, global action, action layout, pre-fill fields, predefined values, Salesforce mobile actions. NOT for building an LWC that runs as a quick action — use lwc/lwc-quick-actions. NOT for converting Classic JavaScript or URL buttons — use admin/custom-button-to-action-migration.

15 repo stars
▌
In App Guidance And Walkthroughs · pranavnagrecha bundle
Configuring Salesforce In-App Guidance: floating, docked, and targeted prompts, multi-step walkthroughs, audience targeting, scheduling, and adoption analytics. Use when designing user onboarding or feature adoption programs in Lightning Experience. NOT for guidance on a record's Path — use admin/path-and-guidance. NOT for adoption and training — use admin/change-management-and-training.

15 repo stars
▌
Integration Admin Connected Apps · pranavnagrecha bundle
Use when managing Connected Apps for integration purposes — configuring OAuth policies, IP restrictions, refresh token expiry, pre-authorization assignment via profile or permission set, and monitoring connected app usage via EventLogFile. NOT for choosing which OAuth grant flow to implement — use integration/oauth-flows-and-connected-apps. NOT for decoding a specific OAuth error such as invalid_grant — use admin/connected-app-troubleshooting.

15 repo stars
▌
Marketing Cloud Engagement Setup · pranavnagrecha bundle
Use this skill when configuring Marketing Cloud Engagement (formerly ExactTarget): business units, user roles, sender profiles, delivery profiles, send classifications, and account-level settings. NOT for MCAE / Account Engagement (Pardot) setup — use admin/mcae-pardot-setup. NOT for designing a multi-brand parent/child BU hierarchy — use architect/multi-bu-marketing-architecture.

15 repo stars
▌
Marketing Reporting Requirements · pranavnagrecha bundle
Gathering and documenting Salesforce marketing reporting requirements: defining KPIs, choosing an attribution model (First Touch / Last Touch / Even Distribution / Multi-Touch), selecting the right Campaign Influence configuration, and mapping business questions to report types and dashboard features. NOT for actually building the Campaign Hierarchy and CCI models - use admin/campaign-planning-and-attribution. NOT for CRM Analytics dataset and dashboard requirements - use admin/analytics-requirements-gathering.

15 repo stars
▌
Permission Set Group Composition · pranavnagrecha bundle
Tactical guidance for composing Permission Set Groups: layering permission sets, applying Mute Permission Sets to subtract narrow capabilities, sequencing the recalculation lifecycle, deletion order, and assignment-vs-activation lifecycle. Triggers: 'PSG composition', 'mute permission set', 'PSG recalculation', 'cannot delete permission set in PSG', 'PSG explosion', 'expired PSG assignment'. NOT for the strategic profile-vs-PSG choice or migrating off profiles - use admin/permission-set-architecture. NOT for record-sharing design (OWD, role hierarchy, sharing rules) - use admin/sharing-and-visibility.

15 repo stars
▌
Requirements Traceability Matrix · pranavnagrecha bundle
Use this skill when building or maintaining a Requirements Traceability Matrix (RTM) on a Salesforce project: one row per requirement, columns for source, user-story id(s), test-case id(s), defect id(s), sprint, release, and status. Covers forward traceability (req → story → code → test) and backward traceability (test → req). Trigger keywords: RTM, requirements traceability matrix, audit trail for salesforce delivery, traceability for steerco, deferred requirement tracking, regulatory traceability. NOT for eliciting the requirements in the first place — use admin/requirements-gathering-for-sf. NOT for user-story authoring — use admin/user-story-writing-for-salesforce. NOT for UAT test design — use admin/uat-test-case-design. NOT for Apex test design — use apex/test-class-standards. NOT for backlog prioritization — use admin/moscow-prioritization-for-sf-backlog.

15 repo stars
▌
Revenue Recognition Requirements · pranavnagrecha bundle
Configure and troubleshoot Salesforce Billing revenue recognition rules, schedules, and GL transaction generation under ASC 606. Triggers: 'revenue schedule not generated after order activation', 'blng__RevenueSchedule__c missing', 'blng__RevenueRecognitionRule__c on a product', 'Finance Periods not set up', 'performance obligation allocation for bundled products', 'distribution method', 'ASC 606 in Salesforce Billing'. NOT for billing schedules, invoice plans and invoice runs - use admin/billing-schedule-setup. NOT for invoice-to-payment mismatches at month-end close - use data/billing-data-reconciliation.

15 repo stars
▌
Stakeholder Raci For Sf Projects · pranavnagrecha bundle
Use this skill when building, reviewing, or refreshing a RACI (Responsible / Accountable / Consulted / Informed) matrix for a Salesforce project so that every Salesforce-specific decision — data model change, automation tier choice, security model, integration boundary, deployment, license/edition — has exactly one accountable owner and a documented escalation path that downstream agents can route to. Trigger keywords: RACI matrix salesforce project, stakeholder authority salesforce, escalation path salesforce decisions, who approves data model change, salesforce decision rights, REFUSAL_NEEDS_HUMAN_REVIEW routing. NOT for the change advisory board operating model itself (use admin/change-management-and-deployment). NOT for end-user training rollout plans (use admin/change-management-and-training). NOT for the technical mechanics of permission set assignment authority (use admin/permission-set-architecture). NOT for pure stakeholder requirements elicitation (use admin/requirements-gathering-for-sf).

15 repo stars
▌
Agent Action Error Handling · pranavnagrecha bundle
Design Invocable Apex actions that return deterministic, agent-friendly errors instead of surfacing raw exceptions to the LLM. NOT for authoring the action itself — @InvocableMethod schema, labels, security context — use agentforce/custom-agent-actions-apex. NOT for the Apex tests that force each error branch — use agentforce/agent-action-unit-tests.

15 repo stars
▌
Agentforce Service AI Setup · pranavnagrecha bundle
Verify prerequisites, license entitlements, and org readiness before enabling Einstein for Service AI features: Case Classification, Article Recommendations, Reply Recommendations, and Work Summaries. Trigger keywords: Einstein for Service setup, enable Case Classification, enable Article Recommendations, enable Reply Recommendations, enable Work Summaries, Einstein generative AI prerequisites, Data Cloud for Work Summaries. NOT for tuning or troubleshooting a feature that is already live — classification accuracy, recommendations not appearing — use agentforce/einstein-copilot-for-service. NOT for building the agent itself — use agentforce/agentforce-agent-creation. NOT for its topic boundary design — use agentforce/agent-topic-design.

15 repo stars
▌
Agentforce Testing Strategy · pranavnagrecha bundle
Design the Agentforce test pyramid: topic (now subagent) coverage, action unit tests, deterministic golden sets, adversarial prompts, and regression harness. Trigger keywords: agentforce testing, agent regression suite, prompt golden set, action unit test agentforce. NOT for hallucination evals, fixture format, or scoring rubrics — use agentforce/agentforce-eval-harness. NOT for running tests in Testing Center, AiEvaluationDefinition or sf agent test — use agentforce/agent-testing-and-evaluation.

15 repo stars
▌
Einstein Prediction Builder · pranavnagrecha bundle
Einstein Prediction Builder for creating custom binary classification predictions on Salesforce objects: field selection, training data requirements, model activation, score embedding, and monitoring. NOT for authoring an Einstein Discovery story in CRM Analytics Studio — use admin/einstein-discovery-setup. NOT for multiclass or regression predictions and programmatic Discovery scoring — use agentforce/einstein-discovery-development. NOT for judging whether the training dataset is usable, feature leakage and quality thresholds — use data/ai-training-data-preparation.

15 repo stars
▌
Salesforce MCP Server Setup · pranavnagrecha bundle
Use this skill to install and configure the salesforce-mcp-lib Apex package and npm stdio proxy so that an MCP client (Claude Desktop, Cursor, ChatGPT) can call Salesforce org data and logic via the Model Context Protocol. Trigger keywords: MCP server, salesforce-mcp-lib, Claude Desktop Salesforce, MCP proxy setup, Apex JSON-RPC, MCP Connected App. NOT for writing the Apex tool classes the server exposes — use agentforce/mcp-tool-definition-apex. NOT for choosing between MCP, REST and Platform Events for external AI access — use architect/ai-agent-org-integration-architecture.

15 repo stars
▌
Apex Callout Retry And Resilience · pranavnagrecha bundle
Strategy layer for resilient Apex HTTP callouts: bounded retry with backoff, queueable async retry chains, circuit-breaker via Platform Cache, idempotency keys, dead-letter pattern. NOT for callout authentication — use apex/apex-named-credentials-patterns. NOT for callout/DML transaction-boundary rules — use apex/callout-and-dml-transaction-boundaries.

15 repo stars
▌
Apex Decimal Arithmetic Precision · pranavnagrecha bundle
Use when Apex code performs arithmetic on currency, tax, percentage, or quantity values and the result is wrong by a cent, a penny, or a fraction — Decimal scale collapses to 0 after divide, totals don't match the sum-of-line-items, currency-field rounding differs from in-app calculation, or `divide()` throws on a non-existent rounding mode. Triggers: 'apex decimal divide rounded wrong', 'currency calculation off by a penny', 'apex setScale rounding mode', 'integer divided by integer truncated to zero', 'apex Decimal precision lost'. NOT for dated exchange rates — use data/multi-currency-and-advanced-currency-management. NOT for Flow formula rounding — use flow/flow-formula-and-expression-patterns. NOT for SOQL aggregate queries — use apex/apex-aggregate-queries.

15 repo stars
▌
Marketing Cloud Custom Activities · pranavnagrecha bundle
Use when building, debugging, or architecting a custom activity, custom split activity, or custom entry source for Marketing Cloud Journey Builder. Trigger keywords: custom activity, Postmonger, config.json, Journey Builder execute endpoint, customActivity.js, custom split outcome, installed package app extension, Journey Builder REST API. NOT for Journey Builder canvas setup — use admin/journey-builder-administration. NOT for MC REST/SOAP API calls — use apex/marketing-cloud-api.

15 repo stars
▌
Soql Aggregate Field Type Support · pranavnagrecha bundle
Use when you need to know which of the six SOQL aggregate functions (AVG, COUNT, COUNT_DISTINCT, MIN, MAX, SUM) a given Salesforce field type supports — e.g. diagnosing why SUM() or AVG() on a date, text, picklist, or boolean field throws a query error, confirming a field is aggregatable before you write the query, or reasoning about multi-currency and picklist-sort-order semantics. Trigger keywords: soql aggregate field type support, sum/avg unsupported field type, aggregate function malformed query, which fields support avg sum, min max picklist sort order, currency aggregate system currency. NOT for GROUP BY / HAVING / ROLLUP / CUBE / AggregateResult iteration mechanics (use apex/apex-aggregate-queries), NOT for report-builder summary formulas or the Reporting/Analytics API, and NOT for declarative Roll-Up Summary fields.

15 repo stars
▌
Soql Format Function Localization · pranavnagrecha bundle
Use when a SOQL SELECT clause or SOSL FIND/RETURNING clause must return number, date, time, or currency fields already localized to the running user's locale (e.g. $44,000.00 or 4/10/2025, 3:31 PM instead of a raw decimal or ISO 8601 string). Covers the FORMAT() function: its four supported field categories, the aliasing rule when the same field is queried twice, and nesting FORMAT() inside aggregate functions or convertCurrency(). NOT for grouping or filtering by date period — use apex/soql-date-functions. NOT for multi-currency setup and conversion rates — use data/currency-management-patterns.

15 repo stars
▌
Soql Multiselect Picklist Queries · pranavnagrecha bundle
Use when filtering SOQL (static or dynamic Apex) on a multi-select picklist field — the four operators =, !=, INCLUDES, EXCLUDES, the semicolon (AND) / comma (OR) grouping inside quoted operands, querying by a value's API name vs display label (API 39.0+), and why the field can't appear in ORDER BY. Trigger keywords: multi-select picklist, multiselect, INCLUDES, EXCLUDES, semicolon, 'field contains value'. NOT for single-select picklist filtering (use plain = / IN), NOT for query performance/selectivity tuning (use data/soql-query-optimization), and NOT for defining or maintaining the picklist field itself (use admin/picklist-and-value-sets).

15 repo stars
▌
Aml Kyc Process Architecture · pranavnagrecha bundle
Use when designing the architecture for AML/KYC compliance workflows on Salesforce — covering verification orchestration, third-party screening integration patterns, risk scoring design, and regulatory data flow. Triggers: AML architecture, KYC verification workflow design, sanctions screening integration, customer risk rating design, onboarding compliance workflow, watchlist screening Salesforce, FinCEN / FATF obligation data flow, BSA compliance architecture. NOT for implementing KYC data collection forms or FSC Action Plans (use admin/fsc-action-plans). NOT for configuring FSC Identity Verification for contact-center caller authentication. NOT for production screening vendor ISV configuration.

15 repo stars
▌
Banking Lending Architecture · pranavnagrecha bundle
Architecture guidance for Salesforce FSC banking and Digital Lending: loan origination platform design, ResidentialLoanApplication data model, payment processing integration patterns, and account servicing workflow architecture. NOT for FSC Insurance policy, claims or underwriting architecture — use architect/insurance-cloud-architecture. NOT for the FSC data-model choice and Compliant Data Sharing design — use architect/fsc-architecture-patterns.

15 repo stars
▌
Experience Cloud Performance · pranavnagrecha bundle
Use when diagnosing slow Experience Cloud site load times, planning CDN and caching strategy, optimizing page weight, or advising on component loading patterns for Aura and LWR-based sites. Trigger phrases: 'Experience Cloud site loads slowly', 'CDN cache not updating after publish', 'LWR site stale after deployment', 'too many Apex calls on Experience Cloud page', 'browser caching Experience Builder', 'CDN configuration Experience Cloud', 'how to reduce page load time community site', 'Experience Cloud performance audit'. NOT for LWC component-level JavaScript performance (use lwc/lwc-performance). NOT for initial site setup (use admin/experience-cloud-site-setup). NOT for multi-site topology decisions (use architect/multi-site-architecture).

15 repo stars
▌
Insurance Cloud Architecture · pranavnagrecha bundle
Architecture guidance for Salesforce Insurance Cloud on FSC: module licensing strategy, policy administration object model, claims processing workflow design, underwriting rule integration, and channel routing. NOT for enabling insurance objects, coverage types or claim config in Setup — use admin/industries-insurance-setup. NOT for FSC retail banking and lending architecture — use architect/banking-lending-architecture.

15 repo stars
▌
Integration Framework Design · pranavnagrecha bundle
Use when designing a reusable integration layer in Salesforce that serves multiple external APIs through a shared callout infrastructure. Triggers: 'how to design a reusable integration layer in Salesforce', 'architect an Apex callout framework for multiple APIs', 'create a centralized error handling pattern for integrations', 'service interface pattern for external APIs', 'factory pattern for dynamic API resolution', 'centralized callout dispatcher'. NOT for individual API implementation (use apex/callouts-and-http-integrations), NOT for Named Credential setup (use integration/named-credentials-setup), NOT for async callout patterns (use apex/continuation-callouts).

15 repo stars
▌
Loyalty Program Architecture · pranavnagrecha bundle
Use when designing or reviewing the architecture of a Salesforce Loyalty Management program before configuration begins — tier-ladder economics, qualifying-vs-non-qualifying currency split, point inflation/deflation modeling, fraud-prevention controls, partner-network topology, multi-region program federation, and tier-descalation policy. Triggers: 'designing a loyalty program', 'how many tiers should we have', 'point economy design', 'preventing loyalty fraud', 'partner loyalty architecture', 'multi-region loyalty rollout', 'tier descalation policy', 'how do we set the qualifying threshold'. NOT for hands-on Loyalty Management setup (use integration/loyalty-management-setup) — this skill produces the architecture document, not the configuration steps. NOT for Marketing Cloud engagement programs (different product). NOT for B2B partner programs that aren't loyalty (regular Sales Cloud opportunity tracking applies).

15 repo stars
▌
Salesforce Decision Analysis · pranavnagrecha bundle
Structure and evaluate a consequential Salesforce choice before the team commits: frame the decision, separate hard constraints from preferences, compare viable options with evidence, test score sensitivity, and recommend a reversible next step. Trigger keywords: compare Salesforce options, evaluate alternatives, make a platform decision, decision matrix, weighted decision. NOT for documenting an already accepted choice — use architect/architecture-decision-records. NOT for a narrow technology branch already covered by a canonical decision tree — apply that tree first.

15 repo stars
▌
Salesforce Learning Research · pranavnagrecha bundle
Research a Salesforce topic for a learner using a citation-first, release-aware evidence workflow: bound the question, prioritize official sources, build a claim ledger, resolve contradictions, and produce a research packet for teaching. Trigger keywords: research Salesforce topic, find official Salesforce docs, prepare learning sources, verify Salesforce concept, release-aware research. Repository package authoring and upstream intake remain outside this package. NOT for the final learner-facing explanation — use admin/salesforce-learning-brief.

15 repo stars
▌
Security Architecture Review · pranavnagrecha bundle
Use when conducting a dedicated security architecture review of a Salesforce org — assessing sharing model completeness, FLS/CRUD enforcement, Apex security patterns, exposed API surface, Connected App policies, and Shield readiness. Produces a structured findings report with severity ratings (Critical/High/Medium/Low) and a 20+ point review checklist. Triggers: security architecture review, org security posture, sharing model audit, FLS coverage review, Connected App security, Shield assessment, org security health deep-dive, HIPAA or PCI security controls Salesforce. NOT for auditing Apex or LWC code line-by-line for CRUD/FLS, SOQL injection and XSS — use security/secure-coding-review-checklist. NOT for a full Well-Architected review across all three pillars — use architect/well-architected-review.

15 repo stars
▌
Crm Analytics Security Predicates · pranavnagrecha bundle
Row-level security in CRM Analytics datasets via security predicates — SAQL filter expressions stored on the dataset that apply at query time per running user. Covers the syntax (`'DatasetColumn' operator value`), the `$User.*` context variables, multi-level predicates (role hierarchy + team + region), predicate performance cost, and testing discipline (admins bypass predicates). NOT for app-level sharing roles, dataset visibility, or sharing inheritance vs custom predicate design — use architect/analytics-security-architecture. NOT for the Setup steps and Analytics license assignment — use admin/analytics-permission-and-sharing.

15 repo stars
▌
Sharing Recalculation Performance · pranavnagrecha bundle
Plan, batch, and monitor Salesforce sharing recalculation jobs — including OWD changes, sharing rule add/remove, role hierarchy restructuring, and Apex managed share rebuild — to avoid multi-hour background jobs and data-access blackouts. NOT for diagnosing data-skew root causes (use admin/data-skew-and-sharing-performance), NOT for designing the sharing model itself (use admin/sharing-and-visibility), and NOT for Apex managed sharing row-cause creation (use apex/apex-managed-sharing).

15 repo stars
▌
Volunteer Management Requirements · pranavnagrecha bundle
Use when designing or implementing volunteer management in Salesforce for nonprofits using NPSP or Nonprofit Cloud — covers V4S managed package objects vs. NPC-native volunteer objects, hours tracking, scheduling, and recognition workflows. NOT for planning an NPSP-to-Nonprofit-Cloud migration — use architect/nonprofit-cloud-vs-npsp-migration. NOT for donor lifecycle and moves-management requirements — use admin/donor-lifecycle-requirements. NOT for HR systems, commercial employee volunteering programs, or Field Service Lightning crew management.

15 repo stars
▌
Cross Cloud Deployment Patterns · pranavnagrecha bundle
Use when sequencing a deployment that spans multiple Salesforce clouds — Sales Cloud, Service Cloud, and Experience Cloud — and encountering reference errors, cascading metadata failures, or DigitalExperienceBundle ordering problems. NOT for single-cloud deploys (use devops/pre-deployment-checklist) or Health Cloud specifics — use devops/health-cloud-deployment-patterns.

15 repo stars
▌
Experience Cloud Deployment Dev · pranavnagrecha bundle
Scripting or automating Experience Cloud site deployment between orgs with the Metadata API, sf CLI or CI/CD: ExperienceBundle (Aura sites), DigitalExperienceBundle (enhanced LWR sites), the ExperienceBundleSettings prerequisite, CMS content exclusion, post-deploy domain/SSO/CDN steps. NOT for the change-set path or a site left unpublished — use devops/experience-cloud-deployment-admin. NOT for writing the site's LWC components — use lwc/experience-cloud-lwc-components.

15 repo stars
▌
Metadata Diff Between Sandboxes · pranavnagrecha bundle
Use when comparing metadata between two Salesforce orgs (UAT vs Prod, dev sandbox vs full copy, fork sandbox vs source) to surface drift, identify items needing deployment, or build a destructive-changes manifest. Triggers: 'compare two. NOT for code-level diffs in version control or for deploying packages — use devops/metadata-api-coverage-gaps.

15 repo stars
▌
Salesforce Dx Project Structure · pranavnagrecha bundle
Use this skill when setting up, configuring, or troubleshooting sfdx-project.json, organizing packageDirectories for mono-repo or multi-package projects, managing sourceApiVersion alignment, and structuring the standard source-format directory tree. NOT for scratch org definition files (use devops/scratch-org-management) or CLI command usage — use apex/sf-cli-and-sfdx-essentials.

15 repo stars
▌
Process Builder To Flow Migration · pranavnagrecha bundle
Migrate Process Builder processes to record-triggered Flows using the native Migrate to Flow tool or manual rebuild. Covers conversion tool usage, pattern mapping, order-of-execution changes, testing migrated flows, and bulk behavior improvements. NOT for Workflow Rule migration — use flow/workflow-rule-to-flow-migration. NOT for designing net-new automation — use admin/process-automation-selection.

15 repo stars
▌
Recursion And Re Entry Prevention · pranavnagrecha bundle
Use when a record-triggered Flow re-fires on the same record because its own DML (or a downstream Flow's DML) re-satisfies the entry criteria — causing CPU-limit failures, duplicated side effects, or 'Maximum Trigger Depth Exceeded' errors. Triggers: 'flow infinite loop', 'flow re-firing on same record', 'flow updates field then runs again', 'flow A and flow B keep updating each other', 'maximum trigger depth exceeded record-triggered flow', 'flow recursion limit hit'. NOT for Apex trigger recursion (use apex/recursive-trigger-prevention) or for Loop element design inside a single Flow run (use flow/flow-loop-element-patterns).

15 repo stars
▌
Retry And Backoff Patterns · pranavnagrecha bundle
Implementing resilient integration retry logic in Salesforce: exponential backoff, jitter, idempotency keys, dead-letter queues, and circuit breaker patterns for Apex callouts. Use when designing callout retry behavior, preventing thundering-herd issues, or handling persistent integration failures. NOT for how many callouts fit in a transaction or CalloutException after DML — use integration/callout-limits-and-async-patterns. NOT for chaining or debugging Queueable jobs that make no callout — use apex/apex-queueable-patterns.

15 repo stars
▌
Scheduled Erp Sync Pattern · pranavnagrecha bundle
Scheduled batch ERP sync — timing, idempotency, error queues, Bulk API vs REST tradeoffs. Triggers: ERP sync schedule, nightly integration batch, ERP Salesforce sync. NOT for event-driven sync — use integration/event-driven-architecture-patterns. NOT for Bulk API job design — use data/bulk-api-patterns.

15 repo stars
▌
Dataraptor Load And Extract · pranavnagrecha bundle
Build or debug DataRaptor Extract and Load — multi-object extracts, upserts, iferror mapping. Triggers: DataRaptor Extract, DataRaptor Load, Turbo Extract debug. NOT for Extract vs Load design tradeoffs — use omnistudio/dataraptor-patterns.

15 repo stars
▌
Omnistudio Cache Strategies · pranavnagrecha bundle
Configure caching on DataRaptors and Integration Procedures for response-time gains. Triggers: OmniStudio cache, DataRaptor cache, IP cache TTL. NOT for IP-specific cacheable design — use omnistudio/integration-procedure-cacheable-patterns.

15 repo stars
▌
Omnistudio Testing Patterns · pranavnagrecha bundle
Test OmniStudio components — OmniScript preview, IP step debugging, DataRaptor validation, UTAM. Triggers: OmniStudio testing, UTAM automation, OmniScript test. NOT for live runtime debugging — use omnistudio/omnistudio-debugging. NOT for metadata/DataPack CI — use data/omnistudio-metadata-management.

15 repo stars
▌
Omnistudio Vs Flow Decision · pranavnagrecha bundle
Use when choosing between OmniStudio (OmniScript / Integration Procedure / FlexCard / DataRaptor) and Flow / Screen Flow / Apex for a given capability. Triggers: 'omnistudio or flow', 'omniscript vs screen flow'. NOT for general automation selection (use admin/process-automation-selection) — use architect/omnistudio-vs-standard-decision.

15 repo stars
▌
Apex Managed Sharing Patterns · pranavnagrecha bundle
Grant row-level access programmatically via __Share records when declarative sharing rules cannot express the policy. NOT for OWD, role hierarchy, or criteria-based sharing rule design — use admin/sharing-and-visibility.

15 repo stars
▌
Dynamic Sharing Recalculation · pranavnagrecha bundle
Force or orchestrate sharing recalculation after bulk data loads, rule changes, or user/role reorgs so row access catches up with policy. NOT for designing new sharing rules — use sharing-selection tree — use data/sharing-recalculation-performance.

15 repo stars
▌
Ip Relaxation And Restriction · pranavnagrecha bundle
Design IP-based access controls: profile login IP ranges, org-wide trusted IPs, IP relaxation per profile, and the interaction with MFA and SSO. Trigger keywords: login IP range, trusted IP, IP relaxation, restricted IP, IP allowlist, login hours. NOT for CSP Trusted Sites, CORS allowlists, TLS requirements, or troubleshooting a CSP violation — use security/network-security-and-trusted-ips.

15 repo stars
▌
Record Access Troubleshooting · pranavnagrecha bundle
Diagnose why a user can or cannot see/edit a record: UserRecordAccess SOQL, Why Can a User Access This Record debug log, OWD, role hierarchy, sharing rules, manual/team/apex shares, implicit parent share. NOT for remediating a CRUD/FLS finding — use apex/apex-stripinaccessible-and-fls-enforcement. NOT for designing the sharing model itself — use admin/sharing-and-visibility.

15 repo stars
▌
Scim Provisioning Integration · pranavnagrecha bundle
Use when designing or reviewing SCIM-based user lifecycle provisioning into Salesforce from Okta, Azure AD / Entra, or another IdP — create/update/deactivate, group-to-permission-set mapping, attribute mapping, and deprovisioning semantics. NOT for SSO/authentication setup (see single-sign-on skills) — use integration/manufacturing-cloud-setup.

15 repo stars
▌
Transaction Security Policies · pranavnagrecha bundle
Transaction Security policy creation and configuration: condition builder, enhanced policies, enforcement actions (block, MFA, notification, end session), real-time monitoring mode, and policy troubleshooting. NOT for Event Monitoring log analysis or Shield Event Monitoring setup — use security/event-monitoring.

15 repo stars
▌
Campaign Planning And Attribution · pranavnagrecha bundle
Designing Campaign Hierarchy for program-level ROI tracking, configuring Customizable Campaign Influence (CCI) attribution models, and interpreting multi-touch attribution from MCAE B2B Marketing Analytics. Trigger keywords: campaign ROI, attribution model, campaign hierarchy, first-touch, last-touch, multi-touch, CCI, campaign influence, revenue attribution, campaign member status. NOT for deciding which attribution model and KPIs to adopt before any config - use admin/marketing-reporting-requirements. NOT for MCAE connector setup or the campaign sync that writes Campaign Member records - use admin/mcae-pardot-setup.

15 repo stars

1,086 published skills · page 4 of 11