experience-lds-data-requirements-generate

Generating LDS Data Requirements Run a three-stage analyst workflow — requirements clarification, API name validation, API recommendation — so a downstream developer can implement a Lightning Data Service (LDS) solution without guessing. When to Use A PRD, Figma comment, or user ask mentions Salesforce data but objects/fields/operations are vague ("show customer info", "update the record", "list upcoming gigs"). Before writing any @wire /Apex code for a new data need, or before handing the recommendation to a downstream implementation workflow. You inherited TODOs like // TODO: fetch related records and need to turn them into precise specs. Do NOT use this skill when: The data need is already fully specified (object API name, field API names, operation type, scope). The component does not touch Salesforce data at all (UI-only, external REST, local state). Prerequisites Show more Installs 894 Repository forcedotcom/sf-skills GitHub Stars 832 First Seen Jul 31, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Warn