SKILL.md
Applying LDS Best Practices
Apply the Lightning Data Service guidelines to a Lightning Web Component. Three pillars: data consistency, referential integrity, and UIAPI vs Apex. Focused on the UI API path — GraphQL and upstream data-requirements analysis are handled out-of-band.
When to Use
- Reviewing a component's data layer for LDS compliance (hand-rolled forms, stringly-typed field names, un-synchronized Apex + LDS, Apex overuse).
- Implementing CRUD on standard or custom objects.
- Deciding between
getRecord,getRecords,createRecord,updateRecord,deleteRecord, base record form components, or Apex. - Fixing stale-data bugs after record mutation.
- Adding schema imports (
@salesforce/schema/...) to replace hard-coded field/object names.
Do NOT use this skill for:
- GraphQL query/mutation generation — handled out-of-band today.
- Upstream data-requirements discovery — handled out-of-band today.
- SLDS class / design-token work (use
design-systems-slds-apply). - Accessibility, security, or RTL review — those are separate passes run with their own tooling.