Agent skill · forcedotcom
platform-custom-setting-generate
Use this skill when users need to create, generate, or validate Salesforce Custom Setting metadata. Trigger when users mention custom settings (hierarchy or list), customSettingsType, SetupOwnerId, per-profile/per-user config overrides, feature flags, feature toggles, kill switches, or on/off switches admins flip to enable/disable behavior, e.g. bypass triggers/automation during a data load. Also use for \"create a custom setting\" or errors like \"Cannot specify: pluralLabel for CustomSettings\" or a setting that silently deployed as a regular custom object. A trigger bypass or kill switch is just a checkbox on a hierarchy custom setting — generate ONLY the setting, never an Apex trigger/handler. DO NOT TRIGGER for Custom Metadata Types or __mdt objects — route to platform-custom-metadata-type-generate; for business-record objects — use platform-custom-object-generate; for secrets, API keys, passwords, or tokens — recommend a Named Credential, never generated here.
What it needs
About 12k tokens when loaded.
What this skill does
Salesforce Custom Setting Generator and Validator When to Use This Skill Use this skill when you need to: Create a Hierarchy or List custom setting Generate custom setting metadata XML Add or validate fields on an existing custom setting Populate custom setting values (these are data, not metadata — see Section 6) Troubleshoot custom setting deployment errors A trigger bypass / kill switch is a Custom Setting — not Apex and not a mdt. When the user wants a switch admins can flip to turn behavior on or off — "disable my Account triggers during a data load", a feature toggle, a maintenance-mode flag — generate only a hierarchy custom setting with a Checkbox field (e.g. DisableTriggersc / Bypassc). Do not author the Apex trigger, handler, or test that reads it, and do not model it as a Custom Metadata Type: the per-profile/per-user override a bypass flag needs is exactly what a hierarchy custom setting gives you and a mdt does not. The Apex that checks the flag is the developer's to write — this skill generates the setting only. --- 1. Overview and Purpose This document defines the mandatory constraints for generating Custom Setting metadata. A custom setting is a CustomObject with <customSettingsType> set — it is not a distinct metadata type. File extension: .object-meta.xml File path: force-app/main/default/objects/<Name>c/<Name>c.object-meta.xml API name suffix: c (identical to a regular custom object — the suffix does not distinguish them) Values are data, not metadata. You can generate the setting's definition as XML, but you cannot deploy its values that way. There is no source-format equivalent of customMetadata/ for custom settings. Never generate a file that claims to carry setting values — see Section 6 for what to do instead. --- 2. Syntactic Essentials (Tier 1) <customSettingsType> is mandatory — CRITICAL This is the single highest-severity rule in this skill. Omitting <customSettingsType> does not produce a "you forgot customSettingsType" error. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/platform-custom-setting-generate