PranavNagrecha/AwesomeSalesforceSkills / .claude/skills/salesforce-architect
salesforce-architect
VerifiedRouter for the 106 SfSkills `architect` skill packages. Solution and platform architecture: multi-org strategy, scalability limits, licensing, Well-Architected reviews and architecture decision records. Use when the request mentions architecture, solution design, ADR, Well-Architected, scalability, large data volume, multi-org, licensing, tenant isolation, HA/DR, technical debt. Finds and opens the exact skill package to read; it does not contain the guidance itself.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.9 KB |
| references/skill-index.md | markdown | 30.0 KB |
references/skill-index.md
View on GitHub# SfSkills — `architect` skill roster (106 packages)
The zero-setup lookup path: this file ships with the plugin and needs
no search index. Scan it, pick a package by name, then read that
package from the repository root under `${CLAUDE_PLUGIN_ROOT}`.
Generated from `registry/skills.json` by `scripts/build_plugin.py`.
Do not hand-edit.
**How to read a gloss.** The package id is on the line already, so the
gloss does not repeat it. It carries what the id cannot, in this order:
the package's own **trigger vocabulary** (the phrasings that should
land here), then its **`NOT for …` redirect** (which names the package
to use instead), then a short scope phrase if there is room. A
`…` marks a truncation, always at a word, keyword or
whole-clause boundary. Budget: 220 characters.
**A `NOT for X - use Y` clause is the most useful thing on the line.**
If your question is X, stop and open Y instead of this package.
- `skills/architect/agent-console-requirements/SKILL.md` — Triggers: service console requirements, agent workspace design, console page layout, utility bar planning, console licensing. NOT for console configuration steps or … use architect/service-cloud-architecture
- `skills/architect/ai-agent-org-integration-architecture/SKILL.md` — Triggers: AI agent Salesforce integration, agent-to-org architecture, LLM Salesforce access pattern, external AI org connectivity, agentic system org design. NOT for building … use agentforce/agentforce-agent-creation
- `skills/architect/ai-governance-architecture/SKILL.md` — System architecture for Salesforce AI governance: MLOps pipeline design, AI Audit Trail …. NOT for authoring AI ethics policy and human-oversight requirements - use admin/ai-ethics-and-governance-requirements.
- `skills/architect/ai-platform-architecture/SKILL.md` — Triggers: AI platform strategy, model selection strategy, Supervisor agent topology, multi-agent orchestration, Einstein LLM gateway, BYOLLM architecture, …. NOT for Model … use agentforce/model-builder-and-byollm
- `skills/architect/ai-ready-data-architecture/SKILL.md` — Triggers: design data model for AI, make Salesforce data AI-ready, data quality for Einstein, grounding data for Agentforce, Data Cloud for AI, …. NOT for building the RAG … use agentforce/rag-patterns-in-salesforce
- `skills/architect/aml-kyc-process-architecture/SKILL.md` — Triggers: AML architecture, KYC verification workflow design, sanctions screening integration, customer risk rating design, onboarding compliance workflow, …. NOT for implementing KYC data … use admin/fsc-action-plans
- `skills/architect/analytics-data-architecture/SKILL.md` — Triggers: CRM Analytics dataset design, dataflow performance, Recipe incremental, remote connection data lake, analytics ELT strategy, dataset row limits. NOT for the External Data … use data/analytics-external-data
- `skills/architect/analytics-embedded-components/SKILL.md` — Triggers: wave-wave-dashboard-lwc, wave-community-dashboard, analytics__Dashboard target, embed dashboard, record-id context filtering, dashboard state JSON, …. NOT for charts - use admin/analytics-dashboard-design.
- `skills/architect/analytics-security-architecture/SKILL.md` — Triggers: CRM Analytics security, row-level security predicate, Analytics dataset access, sharing inheritance, security predicate design, …. NOT for a predicate's SAQL syntax - use data/crm-analytics-security-predicates.
- `skills/architect/api-led-connectivity-architecture/SKILL.md` — Triggers: API-led connectivity, MuleSoft three-tier, System API, Process API, Experience API, integration layer governance, API versioning policy, Agent Fabric. NOT for … use integration/api-led-connectivity
- `skills/architect/architecture-decision-records/SKILL.md` — Triggers: 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.
- `skills/architect/b2b-vs-b2c-architecture/SKILL.md` — Triggers: B2B vs B2C architecture, SFCC vs B2B Commerce, Commerce Cloud platform decision, B2B data model architecture, B2C storefront architecture, …. NOT for implementation … use admin/b2b-commerce-store-setup
- `skills/architect/banking-lending-architecture/SKILL.md` — Architecture guidance for Salesforce FSC banking and Digital Lending: loan origination platform design …. NOT for FSC Insurance policy, claims or underwriting architecture — use architect/insurance-cloud-architecture.
- `skills/architect/case-deflection-strategy/SKILL.md` — Triggers: case deflection, self-service, Einstein Conversation Mining, chatbot containment, knowledge-led deflection, contact reason analysis. NOT for the self-service portal UX, search … use admin/self-service-design
- `skills/architect/ci-cd-pipeline-architecture/SKILL.md` — Triggers: pipeline stages, promotion strategy, quality gate, deployment gate, CI validation sandbox, staging environment, pipeline design, release strategy, …. NOT for … use devops/github-actions-for-salesforce
- `skills/architect/cloud-specific-deployment-architecture/SKILL.md` — Deployment architecture quirks per Salesforce cloud: Industries (OmniStudio), Marketing Cloud (MC packages) …. NOT for building the OmniStudio DataPack pipeline itself — use omnistudio/omnistudio-ci-cd-patterns.
- `skills/architect/commerce-integration-patterns/SKILL.md` — designing or diagnosing end-to-end integration between Salesforce B2B or D2C Commerce and external systems — including ERP …. NOT for CommercePayments adapter implementation — use apex/commerce-payment-integration.
- `skills/architect/composable-commerce-architecture/SKILL.md` — Composable commerce on Salesforce: headless API layer, micro-frontends, BFF pattern, CDN …. NOT for the supported PWA Kit on Managed Runtime composable storefront — use architect/headless-commerce-architecture.
- `skills/architect/conversational-ai-architecture/SKILL.md` — Triggers: Agentforce topic design, Einstein Bot handoff to Agentforce, multi-agent orchestration, conversational channel routing, …. NOT for Einstein Bot dialog and NLU design — use architect/einstein-bot-architecture.
- `skills/architect/cpq-architecture-patterns/SKILL.md` — Triggers: CPQ architecture, quote scalability, bundle design, QCP performance, CPQ integration, large quote, pricing waterfall, ServiceRouter. NOT for a quote that already … use data/cpq-performance-optimization
- `skills/architect/cpq-integration-with-erp/SKILL.md` — designing or troubleshooting an integration between Salesforce CPQ and an ERP …. NOT for syncing standard Accounts, Products or Orders with an ERP in an org without CPQ — use architect/sales-cloud-integration-patterns.
- `skills/architect/cpq-vs-standard-products-decision/SKILL.md` — Triggers: 'should we buy CPQ or use standard pricebooks', 'is CPQ worth the cost for our quoting process', 'product bundling without CPQ', …. NOT for designing bundles, the … use architect/cpq-architecture-patterns
- `skills/architect/crm-analytics-vs-tableau-decision/SKILL.md` — Triggers: 'CRM Analytics vs Tableau', 'which BI tool for Salesforce', 'Tableau for Salesforce data', 'Einstein Analytics vs Tableau', …. NOT for implementation guidance on … use admin/einstein-analytics-basics
- `skills/architect/cross-cloud-data-deployment/SKILL.md` — Cross-cloud data deployment: designing the data handoff when an implementation spans Sales Cloud …. NOT for configuring the Data Cloud identity-resolution ruleset itself — use admin/data-cloud-identity-resolution.
- `skills/architect/customer-effort-scoring/SKILL.md` — Designing a customer experience measurement strategy using CSAT, NPS, and CES metrics …. NOT for building or configuring the technical survey objects, flows, or email templates (use admin/salesforce-surveys for that).
- `skills/architect/data-cloud-architecture/SKILL.md` — Triggers: Data Cloud architecture design, identity resolution strategy, activation target setup, data lakehouse layers, unified profile design, …. NOT for configuring a data stream … use data/data-cloud-data-streams
- `skills/architect/data-cloud-vs-analytics-decision/SKILL.md` — Triggers: 'Data Cloud vs CRM Analytics', 'when to use Data Cloud versus Einstein Analytics', 'should we buy Data Cloud or CRM Analytics', …. NOT for step-by-step implementation … use architect/data-cloud-architecture
- `skills/architect/deployment-automation-architecture/SKILL.md` — Deployment automation architecture on Salesforce: pipeline orchestration …. NOT for cloud-specific deploy mechanics (Industries, Marketing Cloud, Data Cloud) — use architect/cloud-specific-deployment-architecture.
- `skills/architect/einstein-bot-architecture/SKILL.md` — Triggers: 'einstein bot architecture', 'agentforce dialog design', 'bot handoff to agent', 'intent model training'. NOT for multi-agent orchestration or Atlas Reasoning … use architect/conversational-ai-architecture
- `skills/architect/embedded-analytics-architecture/SKILL.md` — Triggers: embed CRM Analytics dashboard, embedded analytics Lightning page, analytics dashboard filter, wave dashboard LWC, analytics state attribute. NOT for a custom LWC … use architect/analytics-embedded-components
- `skills/architect/event-driven-architecture/SKILL.md` — Triggers: 'should we use event-driven architecture or request-reply for this integration', 'designing an event mesh for Salesforce enterprise integration', …. use integration/event-driven-architecture-patterns
- `skills/architect/experience-cloud-integration-patterns/SKILL.md` — Triggers: 'integrate SSO with Experience Cloud site', 'embed third-party chat widget in LWR site', 'connect Data Cloud to Experience Cloud', …. NOT for internal … use lwc/experience-cloud-multi-idp-sso
- `skills/architect/experience-cloud-licensing-model/SKILL.md` — Triggers: Customer Community vs Partner Community, login-based vs member-based license, External Apps license, external user license selection, …. NOT for adding members … use admin/experience-cloud-member-management
- `skills/architect/experience-cloud-performance/SKILL.md` — Triggers: 'Experience Cloud site loads slowly', 'CDN cache not updating after publish', 'LWR site stale after deployment', …. NOT for LWC component-level JavaScript performance (use lwc/lwc-performance).
- `skills/architect/fhir-integration-architecture/SKILL.md` — architecting how Health Cloud connects to external EHR/EMR systems via FHIR R4 — integration pattern selection …. NOT for writing the FHIR calls or HL7 v2 conversion in Apex — use apex/fhir-integration-patterns.
- `skills/architect/fsc-architecture-patterns/SKILL.md` — Triggers: 'should I use the managed-package FSC data model or the platform-native model', …. NOT for individual FSC feature configuration (use admin/household-model-configuration … use data/external-user-data-sharing
- `skills/architect/fsl-integration-patterns/SKILL.md` — Triggers: FSL ERP integration, ProductConsumed ERP sync, GPS fleet integration FSL, IoT work order trigger, customer notification FSL integration. NOT for Financial Services … use architect/fsc-architecture-patterns
- `skills/architect/fsl-multi-region-architecture/SKILL.md` — Triggers: multi-region FSL, FSL timezone territories, cross-territory resource scheduling, concurrent optimization territories, international FSL deployment. NOT for … use architect/fsl-optimization-architecture
- `skills/architect/fsl-offline-architecture/SKILL.md` — Triggers: FSL offline priming, briefcase sync FSL, offline data limits, conflict resolution MERGE_ACCEPT_YOURS, ghost records FSL. NOT for offline in the standard mobile app — use lwc/lwc-mobile-offline-and-briefcase.
- `skills/architect/fsl-optimization-architecture/SKILL.md` — Triggers: FSL optimization engine, ESO enhanced scheduling, global optimization timeout, in-day optimization, OAAS architecture, territory optimization design. NOT for … use admin/fsl-scheduling-optimization-design
- `skills/architect/fundraising-integration-patterns/SKILL.md` — Triggers: payment gateway nonprofit, Elevate payment services, GiftTransaction API, wealth screening integration, iWave Salesforce, DonorSearch scores, …. NOT for writing NPSP BDI … use apex/npsp-api-and-integration
- `skills/architect/government-cloud-compliance/SKILL.md` — Triggers: FedRAMP, Government Cloud, GovCloud Plus, Hyperforce government, ATO, FISMA, NIST 800-53, CMS ARC-AMPE, IL4 IL5 DoD, data residency US government, …. NOT for … use architect/security-architecture-review
- `skills/architect/ha-dr-architecture/SKILL.md` — Designing high availability and disaster recovery strategies for Salesforce: Trust site monitoring, backup strategies …. NOT for picking a backup product or restore mechanics — use data/salesforce-backup-and-restore.
- `skills/architect/headless-commerce-architecture/SKILL.md` — designing or evaluating a headless B2C Commerce storefront architecture …. NOT for standard SFRA storefronts, Experience Cloud headless CMS delivery, B2B Commerce architecture, or … use apex/headless-commerce-api
- `skills/architect/headless-vs-standard-experience/SKILL.md` — Triggers: headless vs LWR, LWR vs Aura, Experience Cloud architecture decision, site performance architecture, community site technology choice. NOT for building the chosen site … use admin/experience-cloud-site-setup
- `skills/architect/health-cloud-data-residency/SKILL.md` — architecting Health Cloud orgs that must satisfy geographic data residency, HIPAA …. NOT for choosing a Hyperforce region or planning a Hyperforce migration outside healthcare — use architect/hyperforce-architecture.
- `skills/architect/health-cloud-multi-cloud-strategy/SKILL.md` — Triggers: Health Cloud multi-cloud, patient portal licensing, Health Cloud Experience Cloud add-on, OmniStudio Health Cloud PSL, …. NOT for deciding whether the org … use architect/payer-vs-provider-architecture
- `skills/architect/high-volume-sales-data-architecture/SKILL.md` — Triggers: 'opportunity table is slow', 'account ownership skew', 'sales report timing out', 'archive old opportunities'. NOT for org-wide LDV design on non-sales objects - use architect/large-data-volume-architecture.
- `skills/architect/hipaa-compliance-architecture/SKILL.md` — Triggers: 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.
- `skills/architect/hybrid-integration-architecture/SKILL.md` — Triggers: on-premises to Salesforce integration network topology, DMZ relay Salesforce, hybrid integration VPN, Private Connect architecture, …. NOT for choosing the … use architect/integration-security-architecture
- `skills/architect/hyperforce-architecture/SKILL.md` — Triggers: 'hyperforce migration', 'hyperforce region selection', 'first-generation infrastructure to hyperforce', 'hyperforce ip allowlisting', …. NOT for general HA/DR … use architect/health-cloud-data-residency
- `skills/architect/industries-cloud-selection/SKILL.md` — Triggers: which industry cloud should I use, Communications Cloud vs Health Cloud, Industries licensing, vertical cloud selection, …. NOT for Industries CPQ vs … use omnistudio/industries-cpq-vs-salesforce-cpq
- `skills/architect/industries-data-model/SKILL.md` — Reference guide for Salesforce Industries cloud data models: Insurance Cloud (InsurancePolicy hierarchy) …. NOT for Health Cloud clinical objects in depth, HC24 vs FHIR R4 — use data/health-cloud-data-model.
- `skills/architect/industries-integration-architecture/SKILL.md` — designing or reviewing the integration layer between Salesforce Industries clouds (Insurance …. NOT for calling a named Industries API (TMF679, InsurancePolicy Connect) — use omnistudio/industries-api-extensions.
- `skills/architect/insurance-cloud-architecture/SKILL.md` — Architecture guidance for Salesforce Insurance Cloud on FSC: module licensing strategy, policy …. NOT for enabling insurance objects, coverage types or claim config in Setup — use admin/industries-insurance-setup.
- `skills/architect/integration-framework-design/SKILL.md` — Triggers: 'how to design a reusable integration layer in Salesforce', 'architect an Apex callout framework for multiple APIs', …. NOT for individual API implementation (use … use apex/continuation-callouts
- `skills/architect/integration-security-architecture/SKILL.md` — Triggers: mTLS, mutual TLS, Hyperforce IP allowlisting, Salesforce Private Connect, certificate limit, integration authentication architecture. NOT for wiring mTLS onto one Named … use integration/mutual-tls-callouts
- `skills/architect/knowledge-taxonomy-design/SKILL.md` — Triggers: knowledge taxonomy design, data category hierarchy, knowledge article lifecycle, knowledge governance model, KCS content gap analysis, …. NOT for enabling Lightning … use admin/knowledge-base-administration
- `skills/architect/knowledge-vs-external-cms/SKILL.md` — Triggers: 'should we use Salesforce Knowledge or a CMS', 'content federation across Salesforce and headless CMS', 'CMS Connect for Experience Cloud', …. NOT for setting up CMS … use admin/experience-cloud-cms-content
- `skills/architect/large-data-volume-architecture/SKILL.md` — Triggers: LDV architecture review, skinny table request, ownership skew hurting sharing, millions of records on custom object, bulk load performance, …. NOT for … use architect/high-volume-sales-data-architecture
- `skills/architect/license-optimization-strategy/SKILL.md` — Triggers: license audit, license cost reduction, unused licenses, permission set license, login-based license, inactive users, license reclamation, …. NOT for whether … use architect/org-edition-and-feature-licensing
- `skills/architect/limits-and-scalability-planning/SKILL.md` — Triggers: 'org is hitting governor limits', 'how many custom objects can we have', 'will our data volume cause performance issues', …. NOT for one transaction's limits - use apex/governor-limits.
- `skills/architect/loyalty-program-architecture/SKILL.md` — Triggers: 'designing a loyalty program', 'how many tiers should we have', 'point economy design', 'preventing loyalty fraud', 'partner loyalty architecture', …. NOT for … use integration/loyalty-management-setup
- `skills/architect/marketing-cloud-vs-mcae-selection/SKILL.md` — Triggers: MCE vs MCAE, Marketing Cloud vs Pardot, B2B vs B2C marketing platform, which marketing cloud product, marketing platform selection. NOT for configuring an MCAE business unit and … use admin/mcae-pardot-setup
- `skills/architect/marketing-consent-architecture/SKILL.md` — Triggers: consent data model, ContactPointConsent, ContactPointTypeConsent, Individual object, CRM system of record, MC consent sync, …. NOT for Subscription or Preference … use admin/consent-management-marketing
- `skills/architect/marketing-data-architecture/SKILL.md` — Triggers: MC data model, relational data extensions, CRM to Marketing Cloud data flow, Contact Key linkage, data architecture, sendable DE design, …. NOT for one Data Extension's keys … use data/data-extension-design
- `skills/architect/marketing-integration-patterns/SKILL.md` — Triggers: 'send transactional email from external app', 'inject contacts into a journey from e-commerce', 'batch sync customer records into Marketing Cloud', …. use architect/sales-cloud-integration-patterns
- `skills/architect/metadata-coverage-and-dependencies/SKILL.md` — Triggers: metadata coverage report, dependency graph, MetadataComponentDependency, impact analysis, unsupported metadata types, packaging eligibility. NOT for a deployment that … use devops/metadata-api-coverage-gaps
- `skills/architect/migration-architecture-patterns/SKILL.md` — Architectural patterns for org migration — org merge (consolidate two orgs into …. NOT for the go-live cutover sequencing itself (use devops/go-live-cutover-planning), NOT for the … use architect/multi-org-strategy
- `skills/architect/mulesoft-anypoint-architecture/SKILL.md` — Triggers: CloudHub, Runtime Fabric, Anypoint Platform, API Manager, Anypoint Exchange, MuleSoft runtime model, private space, Anypoint Security. NOT for … use integration/mulesoft-salesforce-connector
- `skills/architect/multi-bu-marketing-architecture/SKILL.md` — designing or evaluating a Marketing Cloud Engagement multi-Business-Unit …. NOT for configuring business units, user roles, sender and delivery profiles in one account — use admin/marketing-cloud-engagement-setup.
- `skills/architect/multi-channel-service-architecture/SKILL.md` — Triggers: channel prioritization, unified routing across channels, service channel migration, multi-channel capacity planning. NOT for end-to-end contact centre design - use architect/service-cloud-architecture.
- `skills/architect/multi-currency-sales-architecture/SKILL.md` — Triggers: 'multi-currency reporting wrong amounts', 'dated exchange rates architecture', 'ACM converted amount fields'. NOT for enabling multi-currency itself - use data/multi-currency-and-advanced-currency-management.
- `skills/architect/multi-org-strategy/SKILL.md` — Triggers: 'should we have separate Salesforce orgs', 'how do we share data between two orgs', 'we acquired a company that uses Salesforce', …. NOT for sandbox topology, refresh cadence and … use admin/sandbox-strategy
- `skills/architect/multi-site-architecture/SKILL.md` — Triggers: 'multiple Experience Cloud sites architecture', 'multi-portal strategy Salesforce', 'cross-site navigation Experience Cloud', …. NOT for single Experience Cloud site … use admin/experience-cloud-site-setup
- `skills/architect/multi-store-architecture/SKILL.md` — Triggers: multi-store, regional storefronts, shared catalog, multi-currency commerce, localization, multiple WebStores. NOT for creating one WebStore with buyer groups and … use admin/b2b-commerce-store-setup
- `skills/architect/nfr-definition-for-salesforce/SKILL.md` — Defining measurable non-functional requirements for Salesforce implementations …. NOT for technical implementation of those requirements. NOT for HA/DR and failover planning — use architect/ha-dr-architecture.
- `skills/architect/nonprofit-cloud-vs-npsp-migration/SKILL.md` — Nonprofit Cloud vs NPSP decision and migration: choose NPSP (managed package) or Nonprofit Cloud …. NOT for the go/stay decision alone, with no migration to plan - use architect/npsp-vs-nonprofit-cloud-decision.
- `skills/architect/nonprofit-platform-architecture/SKILL.md` — Triggers: Nonprofit Cloud architecture, NPC platform design, nonprofit Salesforce architecture, program and fundraising architecture, …. NOT for deciding whether to … use architect/npsp-vs-nonprofit-cloud-decision
- `skills/architect/npsp-vs-nonprofit-cloud-decision/SKILL.md` — Triggers: NPSP vs Nonprofit Cloud, upgrade NPSP, migrate to NPC, nonprofit platform decision, NPSP end of life, Nonprofit Cloud vs NPSP comparison. NOT for migration … use architect/nonprofit-cloud-vs-npsp-migration
- `skills/architect/omni-channel-capacity-model/SKILL.md` — Designing Omni-Channel capacity models for service orgs: agent capacity allocation, channel weighting …. NOT for enabling Omni-Channel, creating Service Channels or routing rules - use admin/omni-channel-routing-setup.
- `skills/architect/omnistudio-scalability-patterns/SKILL.md` — Triggers: OmniScript concurrency, Integration Procedure SOQL limits portal, Queueable Chainable, Direct Platform Access, LWR CDN Experience Cloud high volume. NOT for generic … use omnistudio/omnistudio-performance
- `skills/architect/omnistudio-vs-standard-architecture/SKILL.md` — Pick and then document the OmniStudio runtime path an architect has to live with: Standard …. NOT for the OmniStudio-vs-standard-tooling capability matrix itself (use … use architect/omnistudio-vs-standard-decision
- `skills/architect/omnistudio-vs-standard-decision/SKILL.md` — Decision framework for choosing OmniStudio (OmniScript, FlexCards, Integration …. NOT for the runtime-path ADR, Standard Runtime vs the vlocity_ins__ package - use architect/omnistudio-vs-standard-architecture.
- `skills/architect/order-management-architecture/SKILL.md` — Triggers: OMS architecture, split orders, fulfillment routing, OCI, order routing strategy, returns architecture, fulfillment location design. NOT for individual order setup or … use admin/commerce-order-management
- `skills/architect/org-edition-and-feature-licensing/SKILL.md` — Triggers: 'feature not available in our edition', 'does Enterprise include Einstein', 'Unlimited vs Performance edition differences', …. NOT for auditing and reclaiming … use architect/license-optimization-strategy
- `skills/architect/org-limits-monitoring/SKILL.md` — Triggers: 'how do I monitor org limits programmatically', 'set up alerts before we hit API limits', 'REST Limits resource usage', 'OrgLimits.getAll() in Apex', …. NOT for Limits-class … use apex/apex-limits-monitoring
- `skills/architect/payer-vs-provider-architecture/SKILL.md` — Triggers: 'should we use MemberPlan or ClinicalEncounter', 'payer vs provider Health Cloud', 'which Health Cloud objects does an insurer use', …. NOT for an insurance … use architect/insurance-cloud-architecture
- `skills/architect/platform-selection-guidance/SKILL.md` — 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 … use admin/process-automation-selection
- `skills/architect/revenue-cloud-architecture/SKILL.md` — Architecting on Salesforce Revenue Cloud (Revenue Lifecycle Management — RLM, the successor …. NOT for implementing DRO fulfilment plans or Connect API billing schedules - use integration/revenue-lifecycle-management.
- `skills/architect/sales-cloud-architecture/SKILL.md` — Triggers: 'design a Sales Cloud architecture for enterprise org', 'Sales Cloud data model and automation strategy', …. NOT for individual feature configuration (use … use architect/sales-cloud-integration-patterns
- `skills/architect/sales-cloud-integration-patterns/SKILL.md` — Triggers: 'sync Accounts and Products with ERP', 'integrate marketing leads with Salesforce', 'quote-to-order flow between Salesforce and ERP', …. NOT for generic integration … use apex/callouts-and-http-integrations
- `skills/architect/salesforce-decision-analysis/SKILL.md` — Triggers: 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.
- `skills/architect/salesforce-erd-and-diagramming/SKILL.md` — Salesforce ERD and architecture diagram generation: Mermaid/PlantUML data-model diagrams for Sales, Service, FSL, Commerce …. NOT for writing the field inventory or data dictionary — use admin/data-model-documentation.
- `skills/architect/salesforce-learning-research/SKILL.md` — Triggers: research Salesforce topic, find official Salesforce docs, prepare learning sources, verify Salesforce concept, …. NOT for the final learner-facing explanation — use admin/salesforce-learning-brief.
- `skills/architect/salesforce-shield-architecture/SKILL.md` — Salesforce Shield as an architectural choice — Platform Encryption + Event Monitoring …. NOT for setting up one Shield feature — use security/platform-encryption, security/event-monitoring or security/field-audit-trail.
- `skills/architect/security-architecture-review/SKILL.md` — Triggers: security architecture review, org security posture, sharing model audit, FLS coverage review, Connected App security, Shield assessment, …. NOT for auditing Apex … use security/secure-coding-review-checklist
- `skills/architect/service-cloud-architecture/SKILL.md` — Triggers: service cloud architecture, case routing design, omni-channel strategy, contact center design, channel strategy, knowledge deflection, …. NOT for case setup click-paths - use admin/case-management-setup.
- `skills/architect/sla-design-and-escalation-matrix/SKILL.md` — Triggers: SLA design, escalation matrix, milestone thresholds, tier definition, business hours alignment, SLA enforcement design. NOT for entitlement process configuration steps (use … use admin/escalation-rules
- `skills/architect/solution-design-patterns/SKILL.md` — Triggers: 'should I use Flow or Apex', 'declarative vs programmatic', 'which layer should handle this', 'automation design review', …. NOT for picking before-save Flow vs … use admin/process-automation-selection
- `skills/architect/subscription-management-architecture/SKILL.md` — Triggers: amendment architecture, renewal automation, co-termination design, subscription ledger, large-scale amendment, billing schedule, swap pattern, …. NOT for … use admin/contract-and-renewal-management
- `skills/architect/technical-debt-assessment/SKILL.md` — Triggers: technical debt review, org health check, dead code analysis, automation overlap, deprecated features, complexity audit, …. NOT for actually deleting the unused … use admin/org-cleanup-and-technical-debt
- `skills/architect/tenant-isolation-patterns/SKILL.md` — Multi-tenant isolation patterns on Salesforce: custom metadata per-tenant, permission-based feature gating, data …. NOT for deciding whether each tenant should get its own org — use architect/multi-org-strategy.
- `skills/architect/wealth-management-architecture/SKILL.md` — designing or reviewing a Salesforce Financial Services Cloud (FSC) wealth management platform …. NOT for the org-wide FSC data-model choice (managed-package vs platform-native) — use architect/fsc-architecture-patterns.
- `skills/architect/well-architected-review/SKILL.md` — Triggers: well-architected review, WAF assessment, org architecture review, architecture health check, trusted easy adaptable. NOT for a security-only deep-dive — use architect/security-architecture-review.
- `skills/architect/zero-trust-salesforce-patterns/SKILL.md` — Architecture pattern for assembling a zero-trust posture in Salesforce — there is no …. NOT for the LLM-side Einstein Trust Layer, an unrelated concept despite the shared word — use agentforce/einstein-trust-layer.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |