forcedotcom/sf-skills

dx-org-switch

Switches the active Salesforce org (default target-org) using the Salesforce CLI.

查看源码
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Steps

  1. Identify the org: the user provides a username or alias (orgIdentifier). If not provided, run sf org list to show authenticated orgs and ask the user which one to use.
  2. Set the default org:
  • Local (default): sf config set target-org <orgIdentifier>
  • Applies only within the current project directory. Use this for normal project work.
  • Global (only if user explicitly requests): sf config set target-org <orgIdentifier> --global
  • Applies system-wide across all directories. Use when working outside a project or when the user asks for global scope.
  • If this fails, report the error and suggest running sf org login web if the org may not be authorized.
  1. Verify:
  • sf config get target-org --json
  • Note: the JSON output does not include a scope/location field — it cannot confirm whether the value is local or global. Confirm the value only, e.g.: target-org is now set to: <value>
  • If it fails, report the error and advise running sf config get target-org.

Notes

  • Unified CLI uses keys like target-org and target-dev-hub. Legacy sfdx keys (defaultusername, defaultdevhubusername) are deprecated in this context.
  • The sf CLI does not have --local or --scope flags for config set. Local scope is the default behavior.
  • If the org does not change after setting the config, check whether SF_TARGET_ORG is set — environment variables override config values.
  • Salesforce CLI config (unified) reference: https://developer.salesforce.com/docs/atlas.en-us.sfdxclireference.meta/sfdxclireference/clireferenceconfigcommandsunified.htm#clireferenceconfigsetunified
来自同一仓库

更多 Skills

全部 Skills
forcedotcom
社区

design-systems-slds-apply

Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons. Use when building any UI that needs SLDS, choosing between Lightning Base Components and SLDS Blueprints, applying styling hooks for theming, using utility classes for layout and spacing, or selecting icons. Triggers include \"build a modal\", \"create a form\", \"data table\", \"SLDS styling\", \"style with hooks\", \"add an icon\".

安装量
5
GitHub Stars
948
最近更新
8月28日
forcedotcom
社区

design-systems-slds-validate

Audit Lightning Web Components for SLDS design-system compliance and produce a scored quality report. Runs the SLDS linter and analyzes CSS for theming hook usage and pairing, scoring SLDS findings across categories into an overall grade. Use when asked to \"score my component's SLDS\", \"SLDS scorecard\", \"SLDS quality report\", \"audit SLDS compliance\", \"how good is my SLDS\", \"check SLDS quality\", \"rate my SLDS styling\", \"evaluate my component's SLDS\", \"is this component's SLDS ready to ship?\", \"look at my LWC for SLDS issues\", \"audit SLDS before I submit\", \"review my component's SLDS before code review\", or any time a user wants an SLDS quality assessment or SLDS production-readiness check on an LWC. Not for fixing violations (use design-systems-slds2-migrate), building new components (use design-systems-slds-apply), or accessibility/WCAG/ARIA audits (use experience-accessibility-validate).

安装量
5
GitHub Stars
948
最近更新
8月28日
forcedotcom
社区

design-systems-slds2-migrate

Migrate Lightning Web Components from SLDS 1 to SLDS 2 by running the SLDS linter and fixing violations. Use this skill whenever users mention SLDS 2, SLDS uplift, linter violations, LWC token migration, class overrides, hardcoded CSS values that need SLDS hook replacement, or styling hook selection. Covers all styling hook categories — color, spacing, sizing, typography, borders, radius, and shadows. Also use when users mention no-hardcoded-values, no-slds-class-overrides, lwc-to-slds-hooks, no-deprecated-tokens-slds1, or ask about SLDS component migration — even if they don't explicitly say \"uplift\" or \"migration\".

安装量
5
GitHub Stars
948
最近更新
8月28日
forcedotcom
社区

agentforce-architecture-analyze

Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins. Renders a human-readable architecture document and Mermaid invocation graph from design-time metadata (not runtime audit rows). TRIGGER when user asks to describe, diagram, inventory, audit, document, or diff (e.g. v3 vs v5) the architecture / action tree / topic structure / tool inventory of a specific agent by agent API name in a specific org. DO NOT TRIGGER for runtime session traces, conversation transcripts, generation timings, or gateway audit chains — this skill reads design-time metadata only (use agentforce-d360-analyze for session traces).

安装量
4
GitHub Stars
948
最近更新
8月28日