Skip to content

forcedotcom/sf-skills / plugins/builder/experience-lwc/skills/experience-lds-data-requirements-generate

experience-lds-data-requirements-generate

Verified

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

references/requirements-analysis.md

View on GitHub
# Requirements Analysis for LDS Data Requirements

## My Job

Analyze Lightning Web Component code to identify and clarify data requirements that need to be resolved before implementing LDS solutions. Focus on parsing natural language requirements, extracting operation types, identifying objects and fields, and determining scope and context.

## What I Look For

- **Ambiguous data requirements**: Comments or TODOs that mention data operations but lack specificity about objects, fields, or operation types.
- **Unclear operation types**: References to data operations without a clear indication of whether it's read, create, update, or delete.
- **Vague object references**: Mentions of data entities that could refer to multiple Salesforce objects or custom objects.
- **Incomplete field specifications**: Generic references like "contact info", "address", or "phone" that could map to multiple API names.
- **Missing scope context**: Data requirements without a clear indication of single vs. multiple records, user-triggered vs. automatic operations.

## What I Ignore

- Code that already has clear, specific LDS implementations.
- Standard Lightning components with proper data binding.
- Non-data-related TODOs and comments.
- Performance optimizations that don't affect requirement clarity.
- TODOs/comments that already acknowledge the need for clarification — these show proper requirement awareness.

## Analysis Framework (Requirements Analysis Mode)

**Operation type analysis**

- Read verbs: "get", "retrieve", "show", "list", "display".
- Create verbs: "create", "add", "new", "insert".
- Update verbs: "update", "edit", "modify", "change".
- Delete verbs: "delete", "remove".
- Flag ambiguous references that could indicate multiple operation types and require explicit confirmation.

**Data entity identification**

- Distinguish between standard Salesforce objects (high confidence) and potential custom objects (requires clarification).
- Detect custom-object patterns through industry-specific terminology or non-standard naming.
- Never assume a custom object API name without explicit confirmation.

**Field specification analysis**

- Map generic field references to specific API names where possible.
- Identify field ambiguity patterns that require clarification (e.g., "phone" → `Phone` vs `MobilePhone` vs `HomePhone`).
- Flag potential custom fields that need org-specific verification.

**Scope and context assessment**

- Determine data access patterns: single record vs. multiple records vs. query-based.
- Assess implementation context: user-triggered actions vs. automatic operations vs. real-time display.
- Consider performance implications and user experience requirements.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall