PranavNagrecha

@pranavnagrecha source repo

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

▌
Salesforce 2 · pranavnagrecha
Entry point for the SfSkills Salesforce library: 1,039 skill packages across 11 domains (admin, agentforce, apex, architect, data, devops, flow, integration, lwc, omnistudio, security), 50 run-time agents and 69 slash commands. Use for any Salesforce, Force.com or Lightning Platform question — Apex, SOQL, SOSL, triggers, Flow, LWC, sObject, custom field, permission set, profile, sharing rule, validation rule, deployment, sandbox, Agentforce, OmniStudio, org setup. This skill does not answer Salesforce questions itself; it routes to the specific skill package that does, then hands off to a domain router.

15 repo stars
▌
Salesforce Lwc 2 · pranavnagrecha bundle
Router for the 83 SfSkills `lwc` skill packages. Lightning Web Components: reactivity, wire adapters, component communication, accessibility, performance, security and Jest testing. Use when the request mentions LWC, Lightning Web Component, wire, @api, @track, lightning-record-form, shadow DOM, Jest, Lightning Message Service, Aura migration, Lightning page. Finds and opens the exact skill package to read; it does not contain the guidance itself.

15 repo stars
▌
Salesforce Apex 2 · pranavnagrecha bundle
Router for the 159 SfSkills `apex` skill packages. Apex and SOQL: triggers, Apex governor limits, async processing, OUTBOUND HTTP callouts, security enforcement, and test patterns. Owns calling an external API FROM Salesforce; salesforce-integration owns inbound. Generic nightly scheduling without naming code belongs to salesforce-flow. Codebase security review belongs to salesforce-security. NOT for SOSL — use salesforce-data. Use when the request mentions Apex, trigger, SOQL, Apex governor limit, batch, queueable, @future, schedulable, test class, CPU time, heap, with sharing, StripInaccessible, callout, HTTP callout, HttpRequest, call an external API, consume a REST API from Apex, Named Credential in Apex, HttpCalloutMock, Apex REST service. Finds and opens the exact skill package to read; it does not contain the guidance itself.

15 repo stars
▌
Salesforce Admin 2 · pranavnagrecha bundle
Router for the 260 SfSkills `admin` skill packages. Declarative Salesforce configuration: objects, fields, record types, page layouts, permission sets, reports, the record-access model (OWD, role hierarchy, sharing rules), and the requirements work that precedes them. Use when the request mentions custom object, custom field, picklist, record type, page layout, permission set, profile, validation rule, report, dashboard, queue, approval process, user setup, sharing rule, org-wide default, OWD, role hierarchy, record access, record visibility, who can see this record, duplicate rule, matching rule, duplicate prevention, clean up duplicates, merge governance, Spring release, seasonal release, Release Updates, Sandbox Preview. Finds and opens the exact skill package to read; it does not contain the guidance itself.

15 repo stars
▌
Bad Skill · pranavnagrecha bundle
missing required keys to exercise the Gate C static check

15 repo stars
▌
Sample Apex Pattern · pranavnagrecha bundle
When to use this skill. Trigger keywords. What it does NOT cover.

15 repo stars
▌
Sample Data Pattern · pranavnagrecha bundle
When to use this skill. Trigger keywords. What it does NOT cover.

15 repo stars
▌
Sample Admin Pattern · pranavnagrecha bundle
When to use this skill. Trigger keywords. What it does NOT cover.

15 repo stars
▌
Sample Devops Pattern · pranavnagrecha bundle
When to use this skill. Trigger keywords. What it does NOT cover.

15 repo stars
▌
Sample Security Pattern · pranavnagrecha bundle
When to use this skill. Trigger keywords. What it does NOT cover.

15 repo stars
▌
Sample Architect Pattern · pranavnagrecha bundle
When to use this skill. Trigger keywords. What it does NOT cover.

15 repo stars
▌
Admin Playbooks · pranavnagrecha
Saved, repeatable admin routines for the sf-intelligence org that batch the right `sfi.*` tools in one request, then synthesize ONE report. Fire when the user asks for a named routine rather than a single fact — "run my pre-deploy checklist", "I inherited this org, give me the tour", "run a security audit", "what's junk in this org / what can I clean up", "is my org healthy / on fire", "audit sweep", "cleanup sweep", "go-live check". Each playbook is an ordered tool batch; run it end to end, then summarize. Single-fact questions go to `answering-org-questions` instead.

15 repo stars
▌
Pre Flight Checks · pranavnagrecha
Diagnostic skill for the SfIntelligence vault. Use when the user invokes `/sfi-status`, says "is something wrong?", "the vault feels off", "something looks stale", "are we connected?", "is the index current?", or when a previous `sfi.*` MCP call returned a `degraded` or `unhealthy` status, an unexpected error envelope, or two consecutive errors. Runs three probes — `sfi.health_check`, `sfi.get_manifest`, and `sf org list --json` — and reports findings as a numbered checklist. Reports only; suggests but does not run `/sfi-refresh` or `/sfi-init`.

15 repo stars
▌
Freshness Tracking · pranavnagrecha
Answers Salesforce admin/architect freshness questions like "when was X modified?", "who built this?", "what changed since last week?", "has this been touched since go-live?", "what changed in the last sprint?". Call `sfi.run_analysis` with `{ "name": "sfi.last_modified", "args": { … } }` and `sfi.changed_since`. Discloses v1.7 honesty axis: when Tooling API enrichment hasn't run, returns `enriched: false` with explicit guidance to run `sfi refresh --with-tooling-api`; never fabricates dates.

15 repo stars
▌
Using Sf Intelligence · pranavnagrecha
Entry point for the SfIntelligence plugin. Use whenever the conversation touches a Salesforce org in this repo — schema, dependencies, permissions, naming conventions, automation, Apex, Flow, integrations, sharing, or any question about a component the org contains. Loads first; teaches Claude the `sfi.*` MCP tool cascade, the resolve-first / ask-a-clarifying-question pattern, the canonical component-ID format, and how to route to the other sf-intelligence skills.

15 repo stars
▌
Conversation Followups · pranavnagrecha
Conversation memory and follow-up handling for the sf-intelligence org. Fire on follow-up turns that depend on what was just discussed — pronouns and ellipsis ("what about the other one?", "and on Contact?", "is that one safe to delete?", "show me its dependencies", "the second one"), refinements of a prior answer, or "what should I look at next?". Keeps the resolved component, the last tool/plane, and the disambiguation options from the previous turns so the user does not have to repeat themselves. Pairs with answering-org-questions (which does the actual lookups) and using-sf-intelligence (the cascade).

15 repo stars
▌
Developer Code Quality · pranavnagrecha
Answers Salesforce developer code-quality questions: "audit my Apex for quality issues", "find governor-limit risks", "where do we have hardcoded IDs / emails / usernames", "check CRUD / FLS enforcement", "what tests are missing / fake-covered", "find dead code", "review this Apex class", "what methods does this class have". Drives the v2.1 quality-recognizer cascade (`code_quality_audit`, `governor_limit_risks`, `find_hardcoded_values`, `crud_fls_audit`, `test_coverage_gaps`), the v2.4 hygiene tool `find_dead_code`, and `apex_structure` for a question about ONE named class or trigger (parsed on demand; adds AST-only checks at `confidence: 'parsed'`). Every recognizer finding is `confidence: 'heuristic'` — pattern recognition is recognition, not declaration; only `apex_structure`'s eight AST-only checks rise above that. Discloses the v2.1 boundary verbatim: the recognizer pattern-matches on tokenized Apex source (not a compiler AST), so cross-class blindness, custom security utility helpers invisible, dynamic

15 repo stars
▌
Salesforce Field Audit · pranavnagrecha bundle
Decide whether Salesforce fields can be deleted, and validate someone else's field-cleanup analysis. Traces every dependency (flows, formulas, roll-ups, validation rules, layouts, related lists, reports, dashboards, Apex, LWC, integrations) before any field is dispositioned Keep / Review / Deprecate-then-Remove / Remove. Use when asked about field cleanup, field deprecation, "can we delete this field", unused or dead fields, org cleanup, technical debt cleanup, field usage audit, safe-to-delete analysis, reviewing a field inventory or field population spreadsheet, or trimming an object before building new automation on it.

15 repo stars
▌
Salesforce Org Context · pranavnagrecha
Silent pre-loader for the SfIntelligence vault. Fires automatically when the user's message mentions any Salesforce concept — words like "object", "field", "trigger", "flow", "validation rule", "permission set", "profile", "layout", "Apex", "picklist", "lookup", "record type", "metadata", "org", "sandbox"; common object names like Account, Contact, Opportunity, Lead, Case, User; or the custom-suffix patterns `__c`, `__mdt`, `__e`, `__b`, `__r`, `__x`. Calls `sfi.org_card` (the refresh-time orientation card; falls back to `sfi.get_manifest` + `sfi.list_components(type: 'CustomObject')` on a vault without a card) to warm the cache so the next question answers faster. Does not print to the user; produces no visible output. Skips when the user invokes `/sfi-init`, `/sfi-refresh`, or `/sfi-status`, when the message is off-topic, or when context is already loaded this session.

15 repo stars
▌
Vault Coverage Honesty · pranavnagrecha
Routes coverage and destructive-verdict questions. Call sfi.coverage_report when the user asks whether the vault is complete, why something was not found, or before narrating safe-to-delete / what-if answers. Render coverageCaveat BEFORE the verdict — never footnote it. Refuse absence-based answers for not-modeled families; distinguish "not in vault" from "not in org".

15 repo stars
▌
Admin Legacy Automation · pranavnagrecha
Answers admin questions about Salesforce's legacy automation layer: "what workflow rules touch Account", "which approval processes are still active", "what assignment rule routes Cases", "is this workflow being replaced by a flow", "which fields does this duplicate rule check", "what emails go out for this approval", "show me the auto-response rules for Lead". Calls `sfi.get_impact` and `sfi.get_edges` to find workflow rules, approval processes, assignment/auto-response/escalation rules, duplicate/matching rules, email templates, and letterheads — plus the `sendsEmail`, `triggersOn`, and `references` edges that connect them. Discloses the v1.3 boundary honestly: workflow rules and processes are extracted in v1.3, but their actual execution semantics (criteria evaluation, time-dependent actions, approval routing) need record-level data v1.x doesn't have. Recommends Flow migration honestly where applicable.

15 repo stars
▌
Answering Org Questions · pranavnagrecha
Conversational interface for questions about the Salesforce org backed by this repo's `org-kb/` vault. Use for any question about schema, dependencies, permissions, naming conventions, Apex source, Flow metadata, or vault freshness — except refresh requests (those fire `refreshing-the-org-vault` instead) and initialization (which fires `/sfi-init`). Triggers on questions starting with "what", "which", "show me", "find", "list", "who can", "where is", "how many", "does", "is there", or "when was" when the topic is a Salesforce entity (object, field, validation rule, flow, Apex class, trigger, layout, permission set, profile) or the vault itself.

15 repo stars
▌
Developer Apex Refactor · pranavnagrecha
Answers code-source-focused developer questions across the full org code surface: Apex classes, Apex triggers, and the v1.4 frontend tier (LWC, Aura, Visualforce). Triggers: "where is field X used in Apex", "find LWC components reading this field", "what calls this Apex from VF", "Aura references to this object", "who reads/writes this field from code", "what classes call MyClass.someMethod", "is it safe to rename this method", "find all Apex references to this", "what Apex/LWC/VF touches this object". Call `sfi.run_analysis` with `{ "name": "sfi.find_code_usages", "args": { … } }` (incoming readsFrom/writesTo/callsApex/references edges from ApexClass, ApexTrigger, LightningComponentBundle, AuraDefinitionBundle, VisualforcePage, or VisualforceComponent nodes) — the single code-usage tool. For strictly Apex-only questions, narrow it with `nodeTypes: ['ApexClass','ApexTrigger']` (the former `find_apex_usages` Apex-only view, now folded in). Optionally follows up with `sfi.search_apex_source` to surface the actu

15 repo stars
▌
Developer Find Anywhere · pranavnagrecha
Answers Salesforce developer "where is X used everywhere" and "what does this field mean in our org" discovery questions: "find every reference to `Industry__c`", "do we already have a field for customer health", "what does this field actually mean", "is `Status` the same as `Stage` here", "is this field manually entered or automated", "what does this acronym mean", "find this literal anywhere in the org". Cascades over the v2.2 universal- search tools (`find_field_anywhere`, `find_semantic_field`, `find_hardcoded_values_anywhere`) and the v2.9 vocabulary + semantic-disambiguation tools (`field_meaning`, `disambiguate_concepts`, `field_provenance`). Discloses the v2.2 Q95 honesty anchor verbatim (lexical-only, no synonyms) and the v2.9 classifier-not-run boundary (`sourceOfTruth` / `semanticCategory` absent on pre-v2.9 vaults).

15 repo stars
▌
Refreshing The Org Vault · pranavnagrecha
Refreshes the SfIntelligence vault from a live Salesforce org. Use when the user invokes `/sfi-refresh`, or says "refresh", "refresh the vault", "pull latest", "pull the latest from my org", "rebuild the vault", "rebuild the index", "my data is stale", "the vault is stale", "I just deployed changes", or any phrase signaling the vault is out of date relative to the org. Drives `sfi refresh`, which shells out to `sf project retrieve`, runs the full extractor graph, imports into DuckDB, renders Markdown, and writes a new manifest (including optional **coverage** metadata).

15 repo stars
▌
Admin Page Layout Routing · pranavnagrecha
Answers Salesforce admin questions about which page layout a user sees and why: "what layout does user X see for Account", "which page layout for Sales rep on Opportunity", "why is this user seeing this layout", "which record type does this profile default to", "what's the layout for record type Y", "user reports wrong layout", "page layout assignments for profile X". Call `sfi.run_analysis` with `{ "name": "sfi.layout_for_user", "args": { … } }` (cascade over profile lookup, layoutAssignment matching, recordType resolution) and explains the routing decision honestly: stages return `unknown` rather than fabricating when v1.2's metadata model can't tell (e.g., org-default layouts, permission-set layout assignments). Discloses v1.2's boundary: only profile-based layout assignments are resolved; permission-set layouts, app-default routing, and Lightning page assignments are noted for manual verification.

15 repo stars
▌
Architect Impact Analysis · pranavnagrecha
Answers "what breaks if I change X?" CHANGE-IMPACT questions for Salesforce architects. Triggers on phrases like "what breaks if I change/delete/rename", "what depends on", "what's the impact of", "is it safe to deprecate", "blast radius of". USAGE phrasings — "where is X used", "what touches X", "which components reference X", "show me everything that uses X" — are NOT this skill: route them to `sfi.find_component_usages` (the §C3 universal usage dispatcher), and "find formulas using X" to `sfi.find_formula_references`. Calls `sfi.get_impact` (BFS over incoming edges, default 2 hops), then reports the dependency subgraph organized by component type with canonical IDs and per-edge confidence. Discloses the current edge-coverage boundary explicitly: dynamic Apex/SOQL blind spots, heuristic-confidence edges, and any metadata families missing from the vault coverage report.

15 repo stars
▌
Business User Orientation · pranavnagrecha
Answers business-user-flavored Salesforce questions like "what does this field mean in English", "what happens when I close this opportunity", "why can't I do X", "how do I find report Y", "what's the SLA on this case", "how are cases routed to agents", "is this field required", "what's this object for", "how is this calculated". Classifies the intent and routes to the right `sfi.*` tool, OR honestly refuses when v1.x doesn't yet model the answer (record-level data, reports, dashboards, live entitlement-milestone status/timers, flow-to-narrative). R6-18 extracts EntitlementProcess/MilestoneType (which milestones apply, business hours, active state) and ServiceChannel/QueueRoutingConfig (Omni-Channel routing model, capacity, overflow queue) — SLA/ entitlement and case-routing questions get a real partial answer now, not a blanket refusal. Bridges the vocabulary gap between business-user phrasing and the architect/admin tools the product already ships. v1.6 broadens to record-value lookups for Custom Metadata T

15 repo stars
▌
Developer Field Deep Dive · pranavnagrecha
Answers Salesforce developer "show me EVERYTHING about this field" and "trace this field's lineage" deep-forensics questions: "what does Account.Industry__c touch", "give me the full field profile for X", "where does this field's data come from", "what fires when this field changes", "show me the upstream + downstream walk for this field", and the same question one tier up: "show me everything about the Contact object". Cascades the v3.0 synthesis tools (`field_360`, `field_lineage`) plus the object-tier counterpart `object_360`, over the v2.0a conditional-context tier (`firesWhen` edges, `ConditionalContext` nodes). Discloses the Q165 honesty anchor verbatim (`dataNotAvailable[]` array of list-view filters, reports, dashboards) and the v2.0a synthetic ConditionalContext id-prefix classification brittleness.

15 repo stars
▌
Architect Async And Events · pranavnagrecha
Answers Salesforce architect async + event-driven topology questions that v2.8 surfaces beyond the v1.5 integration tier. Triggers: "who subscribes to CDC events on Account", "what change-data-capture subscribers do we have", "what's the async chain depth from this Queueable", "show me every scheduled job", "what outbound messages does this org send", "give me every endpoint URL in one place". Drives the cascade: `event_topology` (the event plane — Platform Events, Change Data Capture enablement, event channels, and the retrieval coverage behind each; it supersedes the retired `cdc_subscribers` alias), `async_chain_depth` (transitive `dispatchesAsync` walk; chainAsync NOT persisted), `scheduled_job_catalog` (cron-driven jobs from `System.schedule` detection), `outbound_message_catalog` (the new v2.8 OutboundMessage ComponentType promoted from WorkflowRule dangling refs), `endpoint_catalog` (unified URL view across REST exposes / OutboundMessage / ExternalDataSource / NamedCredential). Discloses v2.8 boundarie

15 repo stars
▌
Architect Cross Org Compare · pranavnagrecha
Answers cross-org metadata comparison questions for Salesforce architects — sandbox-vs-prod drift, prod-vs-prod (multi-customer) audits, "what changed since I last refreshed?" diffs, and Lead-vs- Contact (intra-org) field-mapping for the conversion. Triggers on phrases like "compare sandbox vs prod", "compare two orgs", "what's drifted between {vaultA} and {vaultB}?", "is this object different in sandbox?", "does System Administrator have the same permissions in sandbox?", "Lead conversion mapping", "map Lead fields to Contact". Routes to four MCP tools — `sfi.compare_vaults`, `sfi.compare_object_across_vaults`, `sfi.compare_profile_across_vaults`, `sfi.field_mapping_between_objects` — surfacing the verbatim honesty disclosures on every response: volatile-property filter, api-name-match correspondence, profile-edition rollup, and the Q174 heuristic-mapping disclosure.

15 repo stars
▌
Admin Sharing Troubleshooting · pranavnagrecha
Answers Salesforce admin sharing/visibility questions like "why can't user X see Y", "who can see this record", "what would let this user see Y", "the user says they can't see Z", "visibility check for X on Y", "sharing rules touching Z", "role hierarchy from Foo up", "what grants Edit access to Bar". Calls `sfi.why_cant_user_see_record` (cascade over OWD → permission grants → role hierarchy → owner sharing rules → criteria sharing rules → manual/sets/teams) and explains the verdict honestly: stages return `unknown` rather than fabricating decisions when v1.1's metadata model can't tell. Discloses v1.1's boundary explicitly — manual sharing, sharing sets, account teams, and record-level criteria evaluation all return `unknown` for an admin to verify manually.

15 repo stars
▌
Salesforce Industries Routing · pranavnagrecha
Answers Salesforce Industries / OmniStudio questions: "walk this OmniScript step by step", "what endpoints does this Integration Procedure hit", "what does this DataRaptor map", "what's inside this FlexCard", "what inputs does this DecisionTable take", "what OmniStudio version is this org on". Drives the v3.2 cascade: `omniscript_flow` (OmniScript step sequence + downstream IP / DataRaptor dispatches), `integration_procedure_chain` (IP action chain + REST endpoints + downstream IP / DataRaptor), `datatransform_field_map` (DataRaptor source→target field map with per-row confidence), `omniuicard_widget_breakdown` (FlexCard widget tree + states + dispatched actions), `decision_table_browse` (DecisionTable parameter shape; rows null — Q179 refusal). Triggers on: "OmniScript", "FlexCard", "DataRaptor", "Integration Procedure", "DecisionTable", "OmniStudio", "OmniUiCard", "Industries", "vlocity", "omnistudio__". Discloses the v3.2 honesty axes verbatim: Native-vs-Vlocity-Legacy detection is heuristic (Q180); the Om

15 repo stars
▌
Admin Documentation Generators · pranavnagrecha
Answers Salesforce admin documentation-generation requests: "generate a data dictionary for Account", "create an admin handbook for this org", "write an onboarding doc for a new developer", "generate an architecture overview", "produce a sharing-model summary", "draft a compliance report on PII". Drives the v2.5 documentation-generator tier (`generate_data_dictionary`, `generate_admin_handbook`, `generate_onboarding_doc`, `generate_architecture_overview`, `generate_sharing_summary`, `generate_compliance_report`). Every generator emits a `GeneratedDocument` with frontmatter (`generatedAt`, `sourceTreeHash`, `componentIds`), structured markdown body, per-section confidence labels, and verbatim `boundaries[]` disclosures. Discloses the v2.5 Q125 freshness disclosure on every generated doc, the inherited-confidence rule, the heuristic-tagged sections (Domain Clustering, PII Inventory, Field Label Glossary), and the v1.7-enrichment- missing fallback for Recent Changes / Key Contacts.

15 repo stars
▌
Architect Integration Topology · pranavnagrecha
Answers Salesforce architect integration questions: "draw me our integration map", "what subscribes to this platform event", "who calls this REST API", "which classes are queueable / batchable", "what runs async in this org", "where does this external data source connect", "what is our external API surface", "which external services use this named credential", "audit our auth providers". Call `sfi.run_analysis` with `{ "name": "sfi.integration_map", "args": { … } }` (organized map of auth + endpoints + APIs + access lists) and `sfi.event_subscribers` (given a platform event, return all Apex/Flow subscribers). Plus `sfi.list_components` with the new v1.5 property filters (isQueueable, isSchedulable, isBatchable, hasFutureMethod, hasInvocableMethod, isRestResource, hasAuraEnabledMethod) for async/job and API surface questions. Discloses v1.5 honesty axis: some patterns are heuristic (dispatchesAsync via reflection, LWC fetch URL correlation, CDC subscription detection) and require manual verification.

15 repo stars
▌
Recognizing Naming Conventions · pranavnagrecha
Surfaces observed naming-convention patterns from the SfIntelligence vault. Use when the user asks "what's our convention", "what's the naming standard", "do we always …", "is this consistent with the rest of the org", or proposes a new component name and wants it sanity-checked ("can I name this `CustomerOrder__c`?", "should I call this `Foo__c` or `Bar__c`?"). Calls `sfi.get_naming_convention_report` and reports its observations as **heuristic** — observed patterns, not enforced rules.

15 repo stars
▌
Developer Impact And Reachability · pranavnagrecha
Answers Salesforce developer "what breaks if I change X / where is M reachable from / what does this method touch / is this dead code" questions. Cascades the v2.3 what-if composer family (`what_if_deactivate_flow`, `what_if_disable_trigger`, `what_if_change_method_signature`, `what_if_change_field_type`, `what_if_remove_picklist_value`, `what_if_make_field_required`, `what_if_merge_profiles`, `what_if_split_profile`) and the v2.7 deep code-understanding tools (`call_graph`, `downstream_effects`, `test_coverage_for_method`, `method_reachability`, `meaningful_test_audit`). Discloses the v2.3 / v2.7 boundary axes verbatim: class-granularity (not method); dynamic-dispatch and reflective-invocation invisibility; method-name echo (`method_name` surfaced verbatim, not subsetted); cross-class transitive analysis not available.

15 repo stars
▌
User Story Writing For Salesforce · pranavnagrecha bundle
Use this skill when authoring INVEST-compliant Salesforce user stories from gathered requirements: shaping the As-A/I-Want/So-That stem, writing Given-When-Then acceptance criteria, sizing complexity (S/M/L/XL), splitting stories that are too large for a sprint, and emitting handoff metadata that names the next downstream agent. Trigger keywords: user story, INVEST, story splitting, story sizing, As-A I-Want So-That, story handoff, recommended_agents, backlog item shape. NOT for requirements elicitation or stakeholder interviews (use admin/requirements-gathering-for-sf). NOT for the Given-When-Then technique itself in depth (use admin/acceptance-criteria-given-when-then). NOT for UAT test case design (use admin/uat-test-case-design). NOT for backlog prioritization (use admin/moscow-prioritization-for-sf-backlog).

15 repo stars
▌
Agent Testing And Evaluation · pranavnagrecha bundle
Use when testing, evaluating, or building regression suites for Agentforce agents: conversation testing in Agent Builder, topic (now subagent) coverage and utterance testing, Testing API and AiEvaluationDefinition metadata, Agentforce DX CLI test runs (sf agent generate test-spec, sf agent test create/run/resume/results/list), evaluation metrics (containment rate, escalation rate, CSAT, topic activation accuracy), and post-deploy analytics via Enhanced Event Logs. Triggers: 'how do I test my Agentforce agent', 'agent routes to wrong subagent', 'write utterance tests', 'regression test after topic change', 'measure agent quality', 'agent containment rate', 'run agent tests from the CLI'. NOT for agent creation, topic design, or action contract design — use agentforce/agentforce-agent-creation, agentforce/agent-topic-design, or agentforce/agent-actions respectively.

15 repo stars
▌
Agentforce Cost Optimization · pranavnagrecha bundle
Use when Agentforce run costs are climbing, you need to forecast scale, or you want to reduce tokens per conversation without hurting quality. Covers topic (now subagent) design impact on cost, prompt/template reuse, grounding size discipline, caching, and model-tier selection. Triggers: 'agentforce cost', 'tokens per conversation too high', 'reduce agentforce runs spend', 'forecast agentforce scale cost', 'einstein trust layer tokens'. NOT for capping spend per user with a budget gate and fallback — use agentforce/agent-rate-limit-strategy. NOT for org-wide model-tier and BYOLLM platform strategy — use architect/ai-platform-architecture.

15 repo stars
▌
Agentforce Prompt Versioning · pranavnagrecha bundle
Version Prompt Templates and agent topic (now subagent) prompts: source-control shape, change review, model-version pinning, A/B, and rollback. Trigger keywords: prompt template versioning, prompt changelog, prompt rollback, A/B prompt test, agentforce prompt release. NOT for the CMDT-backed binding that swaps the live template version without a redeploy — use agentforce/prompt-template-versioning. NOT for authoring the template itself — use agentforce/prompt-builder-templates. NOT for prompt engineering tips, general LLM fine-tuning, or Classify / Einstein Generate studio UI walkthroughs.

15 repo stars
▌
Agentforce Tool Use Patterns · pranavnagrecha bundle
Pick the right tool shape for each agent action: Apex invocable vs Flow action vs External Service vs Prompt Template vs Data Cloud retrieval. Covers action selection by use case, argument design for LLM clarity, return-shape contracts, error-surfacing, cost implications, and when to chain tools vs keep a single action. NOT for designing or reviewing an action whose shape is already settled — naming, confirmation, error behavior — use agentforce/agent-actions. NOT for writing the Apex class itself — use agentforce/custom-agent-actions-apex.

15 repo stars
▌
Data Cloud Vector Search Dev · pranavnagrecha bundle
Developing Data Cloud vector search: configuring search indexes, selecting chunking strategies (Easy Setup vs Advanced Setup), generating embeddings via the Salesforce-managed model, calling the Query API with a Data Cloud access token, and wiring retrieval to Agentforce grounding. NOT for admin-side index upkeep in Setup — refresh mode, PII field exclusion, rebuilds — use data/vector-database-management. NOT for end-to-end RAG pipeline design — use agentforce/rag-patterns-in-salesforce.

15 repo stars
▌
Einstein Copilot For Service · pranavnagrecha bundle
Service-specific AI features in Service Cloud: Case Classification setup and optimization, Article Recommendations configuration, Reply Recommendations, Work Summary (After-Visit Summary), Service Replies with Einstein, Auto-Routing, and Einstein Conversation Mining. NOT for the license, entitlement and data-threshold check before first enablement — use agentforce/agentforce-service-ai-setup. NOT for building an Agentforce agent — use agentforce/agentforce-agent-creation. NOT for its topic boundary design — use agentforce/agent-topic-design.

15 repo stars
▌
Apex With Without Sharing Decision · pranavnagrecha bundle
Choosing the sharing keyword on an Apex class: with sharing vs without sharing vs inherited sharing, how it flows through called methods, and when WITH USER_MODE overrides it. NOT for enforcing CRUD/FLS on the records themselves — use apex/apex-stripinaccessible-and-fls-enforcement. NOT for granting row access via __Share records — use apex/apex-managed-sharing.

15 repo stars
▌
Long Running Process Orchestration · pranavnagrecha bundle
Use when designing or reviewing multi-step Apex orchestration that spans multiple transactions, checkpoints state across async boundaries, or recovers from partial failure in a long-running workflow. Trigger keywords: 'multi-step Queueable chain', 'cross-transaction state', 'platform event state machine', 'Finalizer retry', 'orchestrate across transactions', 'workflow progress tracking'. NOT for single-job Queueable design (use apex/apex-queueable-patterns), NOT for Flow Orchestration (use flow/orchestration-flows), NOT for bulk record processing where Batch Apex is the primary tool (use batch-apex-patterns).

15 repo stars
▌
Analytics Embedded Components · pranavnagrecha bundle
Use this skill when embedding a CRM Analytics dashboard into a Lightning App Builder page, Experience Cloud page, or when embedding a custom LWC inside an Analytics dashboard. Trigger keywords: wave-wave-dashboard-lwc, wave-community-dashboard, analytics__Dashboard target, embed dashboard, record-id context filtering, dashboard state JSON, analytics component. NOT for charts - use admin/analytics-dashboard-design. NOT for Aura wave:waveDashboard on Visualforce or cross-dashboard state - use architect/embedded-analytics-architecture.

15 repo stars
▌
Architecture Decision Records · pranavnagrecha bundle
Author and maintain Architecture Decision Records (ADRs) for Salesforce implementations: capture chosen approach, rejected alternatives, constraints, and consequences. Trigger keywords: adr, architecture decision record, design decision log, technical decision. NOT for making the design decision itself, e.g. Flow vs Apex — use architect/solution-design-patterns. NOT for a formal architecture review that produces findings — use architect/well-architected-review.

15 repo stars
▌
Commerce Integration Patterns · pranavnagrecha bundle
Use this skill when designing or diagnosing end-to-end integration between Salesforce B2B or D2C Commerce and external systems — including ERP pricing/inventory, PIM product sync, payment gateways, shipping providers, tax engines, and order management systems (OMS). Covers CartExtension Apex namespace (PricingCartCalculator, ShippingCartCalculator, InventoryCartCalculator), RegisteredExternalService custom metadata, payment gateway architecture, and Product2 External ID patterns. NOT for CommercePayments adapter implementation — use apex/commerce-payment-integration. NOT for generic non-commerce Salesforce integration (Platform Events, MuleSoft, REST APIs), NOT for storefront UI or LWC development.

15 repo stars
▌
Fhir Integration Architecture · pranavnagrecha bundle
Use this skill when architecting how Health Cloud connects to external EHR/EMR systems via FHIR R4 — integration pattern selection, transformation layer design, MuleSoft Accelerator usage, and EMR bidirectional sync topology. NOT for writing the FHIR calls or HL7 v2 conversion in Apex — use apex/fhir-integration-patterns. NOT for mapping a FHIR resource to an object — use data/fhir-data-mapping.

15 repo stars
▌
Fsl Multi Region Architecture · pranavnagrecha bundle
Use this skill when designing FSL for multiple geographic regions or timezones: territory timezone configuration, cross-territory resource assignment, and concurrent optimization serialization. Trigger keywords: multi-region FSL, FSL timezone territories, cross-territory resource scheduling, concurrent optimization territories, international FSL deployment. NOT for choosing an optimization mode or fixing Global optimization timeouts — use architect/fsl-optimization-architecture. NOT for creating a territory, its operating hours or polygon in Setup — use admin/fsl-service-territory-setup.

15 repo stars
▌
Fsl Optimization Architecture · pranavnagrecha bundle
Use this skill when designing or evaluating the FSL scheduling engine architecture: optimization mode selection (Global/In-Day/Resource/Reshuffle), ESO adoption strategy, territory sizing for optimization, and fallback planning. Trigger keywords: FSL optimization engine, ESO enhanced scheduling, global optimization timeout, in-day optimization, OAAS architecture, territory optimization design. NOT for tuning an optimization run in Setup — use admin/fsl-scheduling-optimization-design. NOT for per-appointment scheduling API calls — use apex/fsl-scheduling-api.

15 repo stars
▌
Hipaa Compliance Architecture · pranavnagrecha bundle
Use this skill to design HIPAA-compliant Salesforce org architectures for healthcare organizations storing or processing Protected Health Information (PHI). Trigger keywords: HIPAA BAA, PHI storage, Shield encryption, Health Cloud compliance, HIPAA technical safeguards, covered entity Salesforce architecture. NOT for minimum-necessary access design — use admin/hipaa-workflow-design. NOT for non-healthcare org security review — use architect/security-architecture-review.

15 repo stars
▌
License Optimization Strategy · pranavnagrecha bundle
Auditing, right-sizing, and reclaiming Salesforce licenses to reduce cost and ensure compliant allocation. Trigger keywords: license audit, license cost reduction, unused licenses, permission set license, login-based license, inactive users, license reclamation, right-size licenses. NOT for whether a feature needs an edition upgrade or add-on license — use architect/org-edition-and-feature-licensing. NOT for choosing an Experience Cloud external user license type — use architect/experience-cloud-licensing-model.

15 repo stars
▌
Nfr Definition For Salesforce · pranavnagrecha bundle
Defining measurable non-functional requirements for Salesforce implementations: performance SLIs, scalability targets, availability SLAs, security and compliance requirements, usability benchmarks. Use when starting architecture design or preparing for go-live sign-off. NOT for technical implementation of those requirements. NOT for HA/DR and failover planning — use architect/ha-dr-architecture. NOT for governor limit and scale headroom analysis — use architect/limits-and-scalability-planning.

15 repo stars
▌
Order Management Architecture · pranavnagrecha bundle
Use when designing or reviewing a Salesforce Order Management (OMS) solution architecture: fulfillment workflow strategy, split-order routing design, Omnichannel Inventory (OCI) integration, returns process architecture, and multi-location inventory management decisions. Trigger keywords: OMS architecture, split orders, fulfillment routing, OCI, order routing strategy, returns architecture, fulfillment location design. NOT for individual order setup or day-to-day OMS administration (use admin/commerce-order-management), NOT for storefront or checkout flow design, NOT for CPQ quote-to-order workflows.

15 repo stars
▌
Product Catalog Migration Commerce · pranavnagrecha bundle
Use when migrating product catalog data into Salesforce B2B Commerce — covers category hierarchy, product attributes, images, pricing, and variant structure using the Commerce Import API. NOT for configuring categories, entitlement policies and variants after the load — use admin/commerce-product-catalog. NOT for migrating the CPQ (SBQQ) catalog — use data/product-catalog-migration-cpq.

15 repo stars
▌
Sosl External Object Search Limits · pranavnagrecha bundle
Use when a SOSL search (or global search) against a Salesforce Connect external object misbehaves: it returns no records, rejects an operator/function/clause, or silently drops matches. Covers the query-level rules that apply only to external objects — searchable field types (text only), the mandatory RETURNING clause, the 100-character search-string cap, unsupported operators (INCLUDES / LIKE / EXCLUDES), unsupported functions (toLabel / convertCurrency), unsupported clauses (UPDATE TRACKING / UPDATE VIEWSTAT / WITH DATA CATEGORY / WITH), and adapter-scoped limits (OData logical operators in FIND; custom-adapter convertCurrency and WITH). NOT for enabling search in Setup (use admin/global-search-configuration), NOT for SOSL against standard/custom sObjects (use data/sosl-search-patterns), NOT for general Salesforce Connect / external-object setup (use integration/salesforce-connect-external-objects), and NOT for SOQL of external objects.

15 repo stars
▌
Code Review Checklist Salesforce · pranavnagrecha bundle
Structured Salesforce code review for Apex, triggers, async, and tests before merge or deployment — governor limits, bulk-safe triggers, CRUD/FLS and sharing posture, meaningful tests, and naming consistency. NOT for AppExchange security-review-only deep dives — use security/secure-coding-review-checklist.

15 repo stars
▌
Deployment Error Troubleshooting · pranavnagrecha bundle
Use when a Salesforce metadata deployment fails and you need to diagnose the error from the DeployResult componentFailures. Trigger keywords: 'deployment failed', 'component failure', 'dependent class is invalid', 'code coverage failed', 'UNSUPPORTED_API_VERSION', 'deploy error', 'test failure blocking deploy', 'rollbackOnError', 'missing dependency deploy'. NOT for `Cannot change type`, profile FLS delta, or `entity is in use` errors — use devops/deployment-error-diagnosis. NOT for a deploy that fails because the metadata type itself is unsupported — use devops/metadata-api-coverage-gaps.

15 repo stars
▌
Health Cloud Deployment Patterns · pranavnagrecha bundle
Use when planning or executing a Health Cloud deployment to production or a full sandbox, including managed package installation sequencing, Permission Set License assignment, care plan template setup, HIPAA compliance. NOT for Health Cloud data model design or Apex extensions in Health Cloud — use data/health-cloud-data-model.

15 repo stars
▌
Org Shape And Scratch Definition · pranavnagrecha bundle
Use this skill when authoring, debugging, or optimizing a scratch org definition file (project-scratch-def.json): schema structure, features array, settings hierarchy, Org Shape sourcing, edition selection, orgPreferences-to-settings migration, and release pinning. NOT for scratch org lifecycle management (use devops/scratch-org-management), CI pipeline design, or sandbox configuration.

15 repo stars
▌
Flow Batch Processing Alternatives · pranavnagrecha bundle
Use when a Scheduled Flow or Record-Triggered Flow needs to process more records than Flow can safely handle in a single run. Covers Flow limit realities, scheduled-path chunking, Data Cloud batch transforms, and Apex. NOT for choosing async across a general workflow (see async-selection decision tree) — use flow/flow-large-data-volume-patterns.

15 repo stars
▌
Flow Record Locking And Contention · pranavnagrecha bundle
Diagnose and prevent UNABLE_TO_LOCK_ROW + parent-record contention in record-triggered, scheduled, and screen flows by mapping the implicit lock chain and applying decouple patterns (Platform Events, Queueable handoff, Scheduled Paths). NOT for general flow bulkification — see flow-bulkification — use apex/record-locking-and-contention.

15 repo stars
▌
Flow Record Save Order Interaction · pranavnagrecha bundle
Reason about how record-triggered flows interleave with the Salesforce Save Order (validation, before-save flows, before triggers, duplicate rules, after-save flows, workflow, after triggers, assignment, auto-response, escalation). Trigger keywords: save order, before-save flow, after-save flow, dml order, trigger vs flow order. NOT for choosing before-save vs after-save for one flow — use flow/record-triggered-flow-patterns. NOT for picking which tool stamps a field on save — use admin/workflow-field-update-patterns.

15 repo stars
▌
Platform Events Integration · pranavnagrecha bundle
Use when publishing Platform Events from external systems via REST API, subscribing to Platform Events from outside Salesforce via CometD or Pub/Sub API, designing replay ID strategy for durable external consumers, or handling high-volume event delivery guarantees. Trigger keywords: 'external publish platform event', 'CometD subscribe', 'Pub/Sub API', 'replay ID external', 'durable subscription', 'RetainUntilDate'. NOT for publishing or subscribing inside the org from Apex — use apex/platform-events-apex. NOT for streaming record changes rather than custom events — use integration/change-data-capture-integration.

15 repo stars
▌
Streaming API And Pushtopic · pranavnagrecha bundle
Use when setting up real-time data streaming from Salesforce to external systems using the Streaming API (PushTopic, Generic Streaming), CometD client configuration, replay, and channel management. NOT for Platform Events — use apex/platform-events-apex or integration/platform-events-integration.

15 repo stars
▌
Lwc Jest Testing With Accessibility · pranavnagrecha bundle
Use when authoring or reviewing Jest unit tests for Lightning Web Components and the test plan must include explicit accessibility assertions — covers `@salesforce/sfdx-lwc-jest` setup, `createElement` / `document.body.appendChild` render harness, wire-service mocks via `@salesforce/wire-service-jest-util`, imperative Apex mocks via `jest.fn()`, simulated user interactions (`click`, `keydown`, `focus`), ARIA attribute and accessible-name assertions, focus-management tests, keyboard-navigation tests, and optional `axe-core` integration via `jest-axe`. Triggers: 'add a11y assertions to my LWC jest tests', 'how do I test focus management in LWC', 'jest test for keyboard navigation', 'integrate axe-core into sfdx-lwc-jest', 'assert ARIA attributes after interaction', 'how do I prove the LWC is accessible in CI'. NOT for general LWC jest setup without an a11y angle (use lwc/lwc-testing — this skill is the accessibility-deep-dive sibling), NOT for accessibility-pattern authoring inside the component itself (use lwc

15 repo stars
▌
Calculation Procedure Design · pranavnagrecha bundle
Design Calculation Procedures and Matrices for pricing, rating, and rules-heavy scoring. Triggers: calculation procedure, calculation matrix, expression set, decision matrix. NOT for Salesforce CPQ price rules — use admin/cpq-pricing-rules. NOT for Flow decision logic — use flow/flow-decision-element-patterns.

15 repo stars
▌
API Security And Rate Limiting · pranavnagrecha bundle
API rate limits, Connected App scope restriction, OAuth API security auditing. Triggers: API rate limit, Connected App scopes, API security audit. NOT for Connected App policy design — use security/connected-app-security-policies. NOT for OAuth setup — use admin/connected-apps-and-auth.

15 repo stars
▌
Certificate And Key Management · pranavnagrecha bundle
Use this skill when creating, uploading, or rotating certificates in Salesforce, configuring mutual TLS (mTLS) client authentication, managing the Java KeyStore for CA-signed certificates, diagnosing certificate expiry. NOT for Shield Platform Encryption key management or Named Credential setup — use integration/named-credentials-setup.

15 repo stars
▌
Clickjack And Frame Protection · pranavnagrecha bundle
Configure clickjack protection headers and frame-ancestors for VF pages, LWR sites, and Aura apps. NOT for CSP or Trusted URL configuration — use security/csp-and-trusted-urls.

15 repo stars
▌
Customer Data Request Workflow · pranavnagrecha bundle
Implement GDPR/CCPA data subject rights (access, deletion, rectification) using Salesforce Privacy Center and/or custom workflow. NOT for the underlying erasure mechanics (Individual sObject, ShouldForget, ContactPointConsent) — use security/gdpr-data-privacy. NOT for general backup or org-level data retention policy.

15 repo stars
▌
Encrypted Field Query Patterns · pranavnagrecha bundle
Design SOQL, filters, reporting, and indexes against Shield Platform Encryption fields. Trigger keywords: Shield Platform Encryption, encrypted field query, probabilistic vs deterministic encryption, encrypted SOQL filter. NOT for Classic Encryption (deprecated), field-level security policy, or tenant secret k — use security/platform-encryption.

15 repo stars
▌
Ferpa Compliance In Salesforce · pranavnagrecha bundle
Use this skill when implementing FERPA (Family Educational Rights and Privacy Act) compliance controls in Salesforce Education Cloud or Education Data Architecture (EDA): LearnerProfile FERPA boolean fields. NOT for GDPR/CCPA data privacy, platform encryption at rest, or HIPAA health-data compliance — use architect/health-cloud-data-residency.

15 repo stars
▌
Secure Coding Review Checklist · pranavnagrecha bundle
Use this skill to audit Apex, Visualforce, LWC, and Aura code for Salesforce security review readiness — covering CRUD/FLS enforcement, SOQL injection, XSS, CSRF, and open redirects. NOT for network-level penetration testing or Shield Platform Encryption key management — use security/platform-encryption. NOT for fixing a single query's injection or FLS gap — use apex/soql-security.

15 repo stars
▌
Session Management And Timeout · pranavnagrecha bundle
Use this skill when configuring session timeout values, concurrent session limits, session IP locking, or logout behavior in Salesforce. Covers org-wide session settings, profile-level overrides, Connected App session. NOT for OAuth token refresh flows, login IP ranges, or MFA/identity-provider configuration — use security/oauth-token-management.

15 repo stars
▌
Custom Metadata Types And Settings · pranavnagrecha bundle
Use when choosing between Custom Metadata Types and Custom Settings, understanding hierarchical vs list settings, deployment behavior, governor limit implications, or accessing either from Apex and Flow. Trigger keywords: 'custom metadata vs custom settings', 'hierarchical settings per user profile', 'deployable config vs runtime settings', 'getValues getInstance in apex', 'flow get records custom settings'. NOT for modelling the CMT itself or protecting packaged defaults — use admin/custom-metadata-types. NOT for records users edit as business data — use admin/object-creation-and-design. NOT for secrets — use integration/named-credentials-setup.

15 repo stars
▌
Experience Cloud Member Management · pranavnagrecha bundle
Use this skill when adding external users to an Experience Cloud site, configuring self-registration, managing external user licenses, or customising the login and registration pages. Trigger keywords: add members to community, external user license, self-registration, customer portal login, partner user onboarding, ConfigurableSelfRegHandler. NOT for choosing which external user license to buy — use architect/experience-cloud-licensing-model. NOT for what records external users can see — use security/experience-cloud-security.

15 repo stars
▌
Fsl Scheduling Optimization Design · pranavnagrecha bundle
Use this skill to design, configure, and troubleshoot the Field Service Lightning (FSL) Optimizer — including selecting optimization type (Global, In-Day, Resource Schedule), understanding the priority-score model, configuring travel mode (Aerial vs Street-Level Routing), and tuning optimizer behavior for specific scheduling objectives. NOT for work rules and service-objective weights on a scheduling policy — use admin/fsl-scheduling-policies. NOT for ESO adoption and territory sizing — use architect/fsl-optimization-architecture.

15 repo stars
▌
Fsl Sla Configuration Requirements · pranavnagrecha bundle
Use this skill to configure SLA enforcement for Salesforce Field Service (FSL) using Work Order entitlement processes: designing entitlement processes of type Work Order, defining FSL milestones (response time, on-site arrival, resolution), wiring milestone actions, and aligning Business Hours with service territory Operating Hours. NOT for Case SLAs and Case entitlement processes — use admin/entitlements-and-milestones. NOT for defining the SLA tier table and escalation matrix — use architect/sla-design-and-escalation-matrix.

15 repo stars
▌
Agentforce Custom Channel Dev · pranavnagrecha bundle
Use this skill when building custom channel integrations with the Agentforce Agent API or BYOC (Bring Your Own Channel) for CCaaS — covering session lifecycle management, webhook handling, externalSessionKey design, sequenceId sequencing, BYOC Interaction API integration, and conversation state management. NOT for standing up a standard channel (Embedded Service, Slack, Experience Cloud, Messaging) — use agentforce/agent-channel-deployment. NOT for writing the Apex actions the agent invokes — use agentforce/custom-agent-actions-apex.

15 repo stars
▌
Apex Custom Notifications From Apex · pranavnagrecha bundle
Use when sending Custom Notifications (bell icon / mobile push) from Apex via `Messaging.CustomNotification`. Covers target resolution, Notification Type discovery, recipient limits, and async-safe sending. NOT for creating the Notification Type in Setup — use admin/custom-notification-types. NOT for sending it from Flow — use flow/flow-email-and-notifications.

15 repo stars
▌
Soql Object Limits And Restrictions · pranavnagrecha bundle
Use when a SOQL query fails or must be shaped around a specific object's own limits and restrictions — Attachment's 100,000-record ceiling, the mandatory filter fields on ContentDocumentLink / ContentHubItem / Vote, the required LIMIT clause on TopicAssignment / NewsFeed / UserProfileFeed (absent View All Data), the hard 200-row cap and ORDER BY HasAccess rule on UserRecordAccess, indexed-field-only filtering on big objects, the 4-join / 1,000-row-subquery caps on external objects, KnowledgeArticleVersion requiring dynamic SOQL, and RecentlyViewed's 90-day rolling window. NOT for generic SOQL governor limits — use apex/governor-limits. NOT for index and selectivity tuning — use data/soql-query-optimization. NOT for general SOQL syntax — use apex/soql-fundamentals.

15 repo stars
▌
Conversational AI Architecture · pranavnagrecha bundle
Use when designing or evaluating a Salesforce conversational AI deployment that involves Agentforce agents, Einstein Bots, or a combination of both. Triggers: Agentforce topic design, Einstein Bot handoff to Agentforce, multi-agent orchestration, conversational channel routing, Atlas Reasoning Engine behavior. NOT for Einstein Bot dialog and NLU design — use architect/einstein-bot-architecture. NOT for cutting an existing bot over to Agentforce — use agentforce/einstein-bots-to-agentforce-migration. NOT for Omni-Channel routing for human agents — use architect/multi-channel-service-architecture. NOT for Flow-only automation without a conversational surface — use admin/process-automation-selection.

15 repo stars
▌
Headless Commerce Architecture · pranavnagrecha bundle
Use this skill when designing or evaluating a headless B2C Commerce storefront architecture — covering the Composable Storefront (PWA Kit on Managed Runtime), SCAPI-first API design, frontend framework selection, latency budgets, and caching strategy. NOT for standard SFRA storefronts, Experience Cloud headless CMS delivery, B2B Commerce architecture, or SCAPI implementation-level coding (use apex/headless-commerce-api for that).

15 repo stars
▌
Large Data Volume Architecture · pranavnagrecha bundle
Use when designing or reviewing org-wide large data volume (LDV) concerns: query optimizer behavior and selectivity, custom indexes and skinny tables, sharing and ownership skew, bulk data loads, archival to Big Objects, and divisions. Triggers: LDV architecture review, skinny table request, ownership skew hurting sharing, millions of records on custom object, bulk load performance, 40 million rows on one object and queries crawl, tens of millions of records and everything is slow, object has grown too large and reports time out. NOT for rewriting individual SOQL statements or interpreting Query Plan output in isolation (use data/soql-query-optimization), sales-only Opportunity and Account skew playbooks (use architect/high-volume-sales-data-architecture), or Marketing Cloud data extensions.

15 repo stars
▌
Marketing Consent Architecture · pranavnagrecha bundle
Consent management architecture across Marketing Cloud and CRM: data model design, cross-system sync patterns, and compliance design for GDPR/CCPA. Trigger keywords: consent data model, ContactPointConsent, ContactPointTypeConsent, Individual object, CRM system of record, MC consent sync, opt-in opt-out architecture, data use purpose, lawful basis. NOT for Subscription or Preference Center setup, publication lists and unsubscribe handling — use admin/consent-management-marketing. NOT for right-to-be-forgotten and data subject requests in CRM — use security/gdpr-data-privacy.

15 repo stars
▌
Marketing Integration Patterns · pranavnagrecha bundle
Use when designing or selecting an integration pattern between Marketing Cloud and an external system or Salesforce CRM — including Triggered Sends, Journey injection via Event API, async batch contact entry, SFTP file-based batch sync, and MC Connect Synchronized Data Extensions. Triggers: 'send transactional email from external app', 'inject contacts into a journey from e-commerce', 'batch sync customer records into Marketing Cloud', 'connect Marketing Cloud to Salesforce CRM', 'real-time triggered messages from external platform'. NOT for generic integration framework design unrelated to Marketing Cloud, NOT for Marketing Cloud Automation Studio scripting logic, NOT for Salesforce core-to-core integration patterns (use architect/sales-cloud-integration-patterns).

15 repo stars
▌
Mulesoft Anypoint Architecture · pranavnagrecha bundle
Use when designing or evaluating MuleSoft Anypoint Platform deployment topology, runtime model selection, API governance with API Manager, or Anypoint Exchange strategy. Trigger keywords: CloudHub, Runtime Fabric, Anypoint Platform, API Manager, Anypoint Exchange, MuleSoft runtime model, private space, Anypoint Security. NOT for Salesforce-native integration patterns (use integration/api-led-connectivity), NOT for Salesforce Connector configuration in MuleSoft (use integration/mulesoft-salesforce-connector), NOT for MuleSoft flow implementation or DataWeave scripting.

15 repo stars
▌
Payer Vs Provider Architecture · pranavnagrecha bundle
Use this skill when designing or evaluating a Health Cloud implementation to determine whether the org serves a payer (health insurer), a provider (care delivery organization), or both — and to derive the correct object model, PSL matrix, and feature activation. Triggers: 'should we use MemberPlan or ClinicalEncounter', 'payer vs provider Health Cloud', 'which Health Cloud objects does an insurer use', 'setting up a Health Cloud org for a hospital vs a health plan', 'Provider Relationship Management vs clinical provider'. NOT for an insurance carrier on FSC Insurance Cloud — policy admin, claims, underwriting — use architect/insurance-cloud-architecture. NOT for the Health Cloud object and field definitions themselves — use data/health-cloud-data-model.

15 repo stars
▌
Salesforce Erd And Diagramming · pranavnagrecha bundle
Salesforce ERD and architecture diagram generation: Mermaid/PlantUML data-model diagrams for Sales, Service, FSL, Commerce, Revenue Cloud; OAuth flow diagrams; integration architecture diagrams; object-relationship visualization. NOT for writing the field inventory or data dictionary — use admin/data-model-documentation. NOT for deciding lookup vs master-detail or the model itself — use data/data-model-design-patterns.

15 repo stars
▌
Salesforce Shield Architecture · pranavnagrecha bundle
Salesforce Shield as an architectural choice — Platform Encryption + Event Monitoring + Field Audit Trail as three SEPARATELY-LICENSED components, none of which ship in any standard edition. Covers BYOK vs Cache-Only Key Service (CCKM) tradeoffs, probabilistic vs deterministic encryption schemes, the field-type encryption blocklist (Formula, Roll-Up Summary, indexed External ID), Field Audit Trail's 10-year retention model, and why every Shield design starts with a license confirmation. NOT for setting up one Shield feature — use security/platform-encryption, security/event-monitoring or security/field-audit-trail. NOT for HIPAA control mapping — use architect/hipaa-compliance-architecture. NOT for FedRAMP, FISMA or Government Cloud control mapping — use architect/government-cloud-compliance.

15 repo stars
▌
Wealth Management Architecture · pranavnagrecha bundle
Use this skill when designing or reviewing a Salesforce Financial Services Cloud (FSC) wealth management platform — covering advisor workspace configuration, client portal setup, portfolio data integration, Compliant Data Sharing, and FSC feature enablement decisions. NOT for the org-wide FSC data-model choice (managed-package vs platform-native) — use architect/fsc-architecture-patterns. NOT for gathering wealth management requirements before design — use admin/wealth-management-requirements.

15 repo stars
▌
Zero Trust Salesforce Patterns · pranavnagrecha bundle
Architecture pattern for assembling a zero-trust posture in Salesforce — there is no single zero-trust toggle. The pattern composes High-Assurance Sessions, Real-Time Event Monitoring (RTEM) Transaction Security Policies, Login Flows for conditional access, Event Monitoring for continuous verification, Mobile Security for device compliance, and a Permission Set Group strategy that defaults-deny. Covers the gotcha that not all RTEM event types support TSP enforcement (IdentityVerificationEvent and MobileEmailEvent do NOT). NOT for the LLM-side Einstein Trust Layer, an unrelated concept despite the shared word — use agentforce/einstein-trust-layer. NOT for MFA-only rollouts — use security/mfa-enforcement-strategy. NOT for Apex CRUD/FLS enforcement — use apex/apex-stripinaccessible-and-fls-enforcement.

15 repo stars
▌
Experience Cloud Deployment Admin · pranavnagrecha bundle
Deploying an Experience Cloud site (formerly Community) between Salesforce orgs or sandboxes: metadata ordering, ExperienceBundle enablement, post-deployment publishing, change-set or SFDX-based migration. NOT for automating the deploy in a CI/CD pipeline, or LWR DigitalExperienceBundle — use devops/experience-cloud-deployment-dev. NOT for building the site in Experience Builder — use admin/experience-cloud-site-setup.

15 repo stars
▌
Flow Transaction Finalizer Patterns · pranavnagrecha bundle
Use when a Flow needs to do work that must survive the triggering transaction — post-commit notifications, callouts, audit rows, or compensating actions. Covers Flow Transaction Control element, scheduled paths, Platform Event + finalizer. NOT for general Flow async decisions (see async-selection) — use apex/apex-transaction-finalizers.

15 repo stars
▌
REST API Pagination Patterns · pranavnagrecha bundle
REST API pagination for inbound and outbound integrations: Salesforce QueryMore, cursor-based, offset-based, Link header, page-size tuning, rate limit interaction. NOT for REST CRUD or Composite — use integration/rest-api-patterns. NOT for GraphQL pagination — use integration/graphql-api-patterns.

15 repo stars
▌
Revenue Lifecycle Management · pranavnagrecha bundle
Use this skill when implementing or troubleshooting Salesforce Revenue Lifecycle Management (RLM) — the native Revenue Cloud product covering order-to-cash lifecycle, Dynamic Revenue Orchestrator (DRO) fulfillment plan design, asset amendments, billing schedule creation via Connect API, and invoice management. Triggers on: Dynamic Revenue Orchestrator, RLM order decomposition, DRO fulfillment swimlanes, native Revenue Cloud billing schedule, asset lifecycle management Salesforce. NOT for the overall Revenue Cloud domain architecture or the RLM vs CPQ-classic vs legacy blng__ Billing product choice — use architect/revenue-cloud-architecture. NOT for querying the BillingSchedule / Invoice / FinanceTransaction objects and their relationships — use data/revenue-cloud-data-model.

15 repo stars
▌
Salesforce Data Pipeline Etl · pranavnagrecha bundle
Export large Salesforce datasets to a lakehouse via Bulk API 2.0, CDC streams, or Salesforce Data Pipelines. NOT for ad-hoc exports — use data/etl-vs-api-data-patterns.

15 repo stars

1,086 published skills · page 1 of 11