forcedotcom/sf-skills / plugins/builder/experience-lwc/skills/experience-lwc-design-generate
experience-lwc-design-generate
VerifiedUse 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).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.6 KB |
| references/figma-to-prd-blueprint.md | markdown | 2.7 KB |
| references/prd-analysis-template.md | markdown | 617 B |
| scripts/check-component-name.shexecutable | script | 2.2 KB |
| scripts/detect-project-tools.shexecutable | script | 2.4 KB |
scripts/detect-project-tools.sh
View on GitHub#!/usr/bin/env bash
# Reports which of the Phase-4 lint/format/compile tools are configured
# in the target project. Emits one `<tool>=yes|no` line per checked tool
# on stdout so the caller can gate each Phase-4 substep deterministically
# instead of parsing prose.
#
# Detected tools:
# eslint — .eslintrc.* / eslint.config.* / package.json `eslintConfig`
# prettier — .prettierrc* / prettier.config.* / package.json `prettier`
# cursor-rules — .cursor/rules/ or .cursorrules
# lwc-compiler — sfdx-project.json or @lwc/compiler in package.json dependencies
#
# Usage:
# <skill_dir>/scripts/detect-project-tools.sh [<projectRoot>]
#
# `<projectRoot>` defaults to the current working directory.
#
# Exit codes:
# 0 — detection completed (output on stdout is authoritative)
# 2 — usage error
set -euo pipefail
if [ "$#" -gt 1 ]; then
echo "usage: $0 [<projectRoot>]" >&2
exit 2
fi
root="${1:-.}"
if [ ! -d "$root" ]; then
echo "detect-project-tools: project root \`$root\` does not exist" >&2
exit 2
fi
python3 - "$root" <<'PY'
import json
import os
import sys
from pathlib import Path
root = Path(sys.argv[1]).resolve()
def has_any(patterns):
for p in patterns:
# Interpret `*` as a shell-style glob relative to `root`.
matches = list(root.glob(p))
if matches:
return True
return False
def has_pkg_key(key):
pkg = root / "package.json"
if not pkg.is_file():
return False
try:
data = json.loads(pkg.read_text(encoding="utf-8"))
except Exception:
return False
if key in data:
return True
deps = {}
for section in ("dependencies", "devDependencies", "peerDependencies"):
d = data.get(section) or {}
if isinstance(d, dict):
deps.update(d)
return key in deps
def yn(cond):
return "yes" if cond else "no"
eslint = has_any([
".eslintrc",
".eslintrc.*",
"eslint.config.*",
]) or has_pkg_key("eslintConfig")
prettier = has_any([
".prettierrc",
".prettierrc.*",
"prettier.config.*",
]) or has_pkg_key("prettier")
cursor_rules = has_any([
".cursor/rules",
".cursorrules",
])
lwc_compiler = has_any([
"sfdx-project.json",
]) or has_pkg_key("@lwc/compiler")
print(f"eslint={yn(eslint)}")
print(f"prettier={yn(prettier)}")
print(f"cursor-rules={yn(cursor_rules)}")
print(f"lwc-compiler={yn(lwc_compiler)}")
PY
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |