Agent skill · forcedotcom
platform-lightning-type-widget-coordinate
Orchestrate Apex-backed Lightning Type + HXL widget generation. TRIGGER only when the prompt EXPLICITLY invokes Lightning Types: user says 'Lightning Type', 'CLT', 'Custom Lightning Type', 'Apex-backed type', references '@apexClassType/...', asks to build a widget or card for a named Lightning Type, asks to create a new Lightning Type and widget together, or grounds a widget in a specific Apex class as its schema. DO NOT TRIGGER when the prompt names only a subject, domain, feature, or entity noun. Also DO NOT TRIGGER when: authoring only a Custom Lightning Type (use platform-custom-lightning-type-generate), only an Apex class (use platform-apex-generate), editing an existing widget without any Lightning Type change, or grounding a widget on an object/JSON-based Lightning Type (lightning__objectType with primitives).
What it needs
About 10k tokens when loaded.
What this skill does
Building a Lightning Type With a Widget Coordinate Lightning Type, Apex class, and HXL widget generation across the two paths below. This skill never authors content directly — it loads and invokes leaf skills in dependency order, gates progress on user approval, and runs validation gates before reporting completion. Scope Apex-backed Lightning Types only — root lightning:type of the form @apexClassType/<namespace><ClassName> (outer class). The class itself carries the @AuraEnabled fields that define the payload shape; nested list-element types live as inner classes referenced by List<Inner> fields on the outer class. Object/JSON-based Lightning Types (root lightningobjectType with primitive properties) are out of scope; route those to platform-custom-lightning-type-generate and platform-widget-generate separately. --- Phase Graph Phase Purpose Runs in Output --- --- --- --- 1 — Path selection Pick the path (existing-lightning-type-with-widget · new-lightning-type-with-widget) from the user prompt. All paths path 2 — Lightning Type discovery Local project first; then sf project retrieve --metadata LightningTypeBundle:<name>; ambiguity resolution; in-scope verification. existing-lightning-type-with-widget only lightningTypeSchema (path + SHA-256 + Apex class FQN) 3 — Build plan Print the plan in full; proceed unless the next reply explicitly pushes back. All paths printed plan 4 — Generation Load and invoke leaf skills per path. All paths files written 5 — Validation Run hard gates (block) and warn gates (advisory). All paths gate report 6 — Summary Files, validations, preview readiness, next steps. All paths summary Per-phase pattern: Step What to do --- --- 1. Load skill Invoke the named skill. Even if you remember its content, skills evolve — always load fresh. 2. Execute Follow the loaded skill's workflow. 3. Verify Confirm outputs exist and match the spec. 4. Checkpoint Confirm phase completion before moving on. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/platform-lightning-type-widget-coordinate--163334