Skip to content

forcedotcom/sf-skills / plugins/builder/experience-react/skills/experience-ui-bundle-2gp-deploy

experience-ui-bundle-2gp-deploy

Verified

MUST activate when the user wants to package, distribute, or install/upgrade/uninstall/promote a UI Bundle as a Salesforce second-generation (2GP) package (project may contain uiBundles/ or sfdx-project.json for packaging tasks; install/upgrade tasks may lack local bundle files). Handles making a bundle packageable, choosing managed/unlocked flavor, creating package/version with sf package, installing/upgrading in another org, and debugging failures. TRIGGER on packaging, 2GP, managed package, unlocked package, AppExchange, package version, sf package, sf package install, sf package upgrade, install a package, upgrade a package, cross-org distribution. DO NOT TRIGGER for plain source deploy to one org (use experience-ui-bundle-deploy) or scaffolding a new bundle (use experience-ui-bundle-project-generate). Apply piecemeal — do ONLY the part asked.

scripts/find-bundle-package-dir.sh

View on GitHub
#!/usr/bin/env bash
# Resolve the package directory that actually owns a UI Bundle.
#
# Given a bundle name, walk sfdx-project.json's `packageDirectories` array and
# print the `path` of the entry whose tree contains `uiBundles/<bundle-name>/`
# on disk. This is what the skill's `<packageDir>` token substitutes to.
#
# Why this exists: `packageDirectories[0]` is only correct when the project
# has a single package directory. Multi-package projects can put the bundle
# under any entry, so writing metadata (CustomApplication, PermissionSet) into
# `[0]` blindly can land it *outside* the package being versioned, and the
# installed package will then be missing the intended wiring.
#
# Usage: scripts/find-bundle-package-dir.sh <bundleName> [project-dir]
#   project-dir defaults to the current directory.
#
# Exit 0: prints the matching `path` (no trailing slash) on stdout.
# Exit 1: no sfdx-project.json / malformed / no entry contains the bundle.
set -euo pipefail

if [[ $# -lt 1 ]]; then
  echo "find-bundle-package-dir: usage: $0 <bundleName> [project-dir]" >&2
  exit 1
fi

bundle="$1"
project_dir="${2:-.}"
project_file="$project_dir/sfdx-project.json"

if [[ ! -f "$project_file" ]]; then
  echo "find-bundle-package-dir: no sfdx-project.json in '$project_dir'" >&2
  exit 1
fi

# Match anywhere under each packageDir tree, not just the fixed
# force-app/main/default layout — the bundle may live under any depth.
# Read paths one-at-a-time (portable to bash 3.2 on macOS).
found=""
while IFS= read -r raw; do
  [[ -z "$raw" ]] && continue
  path="${raw%/}"
  if [[ -d "$project_dir/$path" ]] && find "$project_dir/$path" -type d -path "*/uiBundles/$bundle" -print -quit 2>/dev/null | grep -q .; then
    found="$path"
    break
  fi
done < <(jq -r '.packageDirectories[]?.path // empty' "$project_file")

if [[ -z "$found" ]]; then
  echo "find-bundle-package-dir: no packageDirectories entry contains 'uiBundles/$bundle' — check the bundle name and sfdx-project.json paths" >&2
  exit 1
fi

echo "$found"
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall