Agent skill · forcedotcom
platform-custom-lightning-type-generate
Use this skill when users need to create Custom Lightning Types (CLTs) for Einstein Agent actions or structured input/output schemas. Trigger when users mention CLT, Custom Lightning Types, JSON schemas for agents, type definitions, lightning__objectType, or editor/renderer configurations. For widget renditions that combine a CLT with a Widget bundle, use the platform-lightning-type-widget-coordinate orchestrator instead. This is complex - always use this skill for CLT work.
What it needs
About 9k tokens when loaded.
What this skill does
When to Use This Skill Use this skill when you need to: Create Custom Lightning Types (CLTs) for structured inputs/outputs Generate JSON Schema-based type definitions for Lightning Platform Configure CLTs for Einstein Agent actions Set up editor and renderer configurations for custom UI Troubleshoot deployment errors related to Custom Lightning Types Specification CustomLightningType Metadata Specification Overview & Purpose Custom Lightning Types (CLTs) are JSON Schema-based type definitions used by the Lightning Platform (including Einstein Agent actions) to describe structured inputs/outputs and drive editor/renderer experiences. Configuration Choose referenced CLT pattern for nested objects - When you need a reusable or separately deployed nested type, create a CLT for that shape and reference it with "lightning:type": "c<CLTName>". That string is the referenced type’s lightning:type value / FQN / registered identifier — not the JSON Schema title. Choose standard Lightning types when the structure is simple and can be expressed with properties and supported primitive lightning:type identifiers. Choose Apex class types (@apexClassType/...) when the structure already exists server-side and you want the Apex class to define the shape. Include editor/renderer config only when you need custom UI behavior (custom LWC input/output components). Otherwise, omit. Critical Rules (Read First) CRITICAL: NEVER include the "$schema" field in schema.json Salesforce CLT validator WILL REJECT schemas with this field, even if it's a valid JSON Schema $schema declaration. Root object schemas MUST include: "type": "object" "title" "lightning:type": "lightningobjectType" "unevaluatedProperties": false "unevaluatedProperties" is enforced as false by the CLT metaschema. Do not set it to true. Root object schemas MUST NOT include "examples" when "unevaluatedProperties": false is set. Nested objects (inside properties) MUST NOT set "lightning:type": "lightningobjectType". …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/platform-custom-lightning-type-generate--473619