domains / families / software-engineering / experience-lds-data-requirements-generate

experience-lds-data-requirements-generate

authentic

Use when a Lightning Web Component data need is described in ambiguous natural language — turn \"get contact info\" or \"show account data\" into a clear, PRD-ready data-requirements spec. TRIGGER when the user says \"define data requirements for this LWC\", \"turn this PRD data section into validated object/field names\", \"recommend GraphQL vs UIAPI for this data need\", \"validate these Salesforce API names\", or \"spec out the LDS adapter for this component\", or references LWC bundle files (`.js`, `.js-meta.xml`) whose data layer is not yet specified. DO NOT TRIGGER when the data layer is already fully specified, when authoring the actual query or adapter code from a known spec, or when implementing an LWC end-to-end (use experience-lwc-generate).

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.
• 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).

When not to use

• data layer is already fully specified
• authoring the actual query or adapter code from a known spec
• implementing an LWC end-to-end
• component does not touch Salesforce data at all

Skill page

Source