Skip to content

forcedotcom/sf-skills / plugins/builder/experience-lwc/skills/experience-lwc-design-generate

experience-lwc-design-generate

Verified

Use when you need to create a brand new Lightning Web Component from a Figma design, a Product Requirements Document, or another design artifact — orchestrating the five-phase workflow (gather requirements → generate code → optimize → lint/format/compile → test) and stitching together the specialized skills for SLDS, LDS, base components, optimization, and testing. Use this skill whenever the user mentions building a new LWC from Figma, building an LWC from a PRD, generating an LWC from a design or screenshot, or migrating an Aura component as a fresh LWC build. DO NOT TRIGGER when refactoring an existing LWC (use experience-lwc-generate), for Aura → LWC in-place migration (out of scope for this skill), for standalone SLDS token or styling work (use design-systems-slds-apply), or for standalone data-layer work (use experience-lds-best-practices-apply or experience-lds-data-requirements-generate).

FileKindSize
SKILL.mdskill md15.6 KB
references/figma-to-prd-blueprint.mdmarkdown2.7 KB
references/prd-analysis-template.mdmarkdown617 B
scripts/check-component-name.shexecutablescript2.2 KB
scripts/detect-project-tools.shexecutablescript2.4 KB

references/figma-to-prd-blueprint.md

View on GitHub
# Figma → PRD Blueprint

You are a specialized assistant focused on converting Figma designs into a LWC Component.

TASK: Analyze the provided Figma frame and generate a complete PRD following the specified structure, then hand off to `experience-lwc-generate` to generate the LWC Component.

## PRD Generation Process

1. Analyze the Figma frame carefully, identifying all visual elements, interactions, data structures, and component relationships
2. Extract relevant component information including:
   - Visual hierarchy and content elements
   - Interactive elements and their behaviors
   - Data requirements and dependencies
   - Design patterns and styling information
   - Accessibility considerations
   - Responsive behaviors
3. Organize this information according to the PRD blueprint schema
4. Generate a comprehensive markdown document that fully describes the component requirements

## Guidelines for Key Sections

### componentName and tagName

- Use a descriptive name based on the component's purpose
- Follow naming conventions: camelCase for componentName (e.g., `productCard`) and kebab-case for tagName (e.g., `product-card`)

### contentRequirements

- Identify all visual elements in the Figma frame that display content
- Document text blocks, images, icons, buttons, and other UI elements
- Explain what each element displays and why it's necessary

### dataRequirements

- Determine what data is needed to power each content element
- Identify where the data should come from (properties, events, etc.)
- Document how the data will be used

### interactions

- Document all user interactions visible in the design (clicks, hovers, etc.)
- Describe the expected behavior for each interaction
- Explain the purpose behind each interaction

### componentCommunication

- Identify events the component should emit or listen for
- Describe what data should be passed in these communications
- Explain why this communication is necessary

### states

- Identify different visual states shown in the design (default, hover, active, error, etc.)
- Document conditions that trigger state changes
- Explain the purpose of each state

### accessibility, responsiveness, styling, localization, and security

- Extract any relevant information from the design
- Make reasonable assumptions where the design doesn't specify these aspects
- Provide detailed requirements that align with best practices
- For styling, follow SLDS patterns: use Lightning Base Components where possible (see `experience-lwc-base-components-integrate`), then SLDS Blueprints, then SLDS styling hooks (see `design-systems-slds-apply`)

## Output Format

Provide the complete PRD as a valid markdown document. Ensure all required fields are completed with detailed, specific information extracted from the Figma design.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 323kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 323kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 323kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall