* fix: trigger ui-bundle skill for React application prompts
Add React-specific trigger language to building-ui-bundle-app description
so prompts like "I want to build a react application" activate the
ui-bundle orchestrator even without existing project files.
* fix: correct stale related-skill reference
Rename generating-experience-react-site to generating-ui-bundle-site
in building-ui-bundle-app related-skills to match the actual skill name.
* fix: tighten skill descriptions to reduce false triggers
- generating-ui-bundle-metadata: remove generic triggers (metadata, new app,
meta XML, configuration), update command to sf template generate ui-bundle,
add --template reactbasic flag
- building-ui-bundle-app: reframe as orchestrator for multi-skill ui-bundle
work, distinguish from generating-lightning-app
* fix: improve ui-bundle skill descriptions to reduce false triggers and improve activation
- Add MUST activate + file-pattern triggers to all 9 ui-bundle skills
- Remove overly specific examples that waste context tokens
- Scope features skill to authentication and search only
- Add boundary language between orchestrator and frontend skills
- Update metadata skill to use sf template generate ui-bundle --template reactbasic
* fix: standardize uiBundles/*/src/ directory trigger across all ui-bundle skills
* fix: remove React references from skill descriptions for framework agnosticism
* fix: standardize uiBundles/*/src/ trigger in agentforce and data skills
* fix: add 'Use this skill when' trigger context to all ui-bundle skill descriptions
* fix: require mobile-responsive UI in building-ui-bundle-frontend skill
* Add building-ui-bundle-app orchestration skill
New orchestration skill that coordinates all UI bundle skills in proper
dependency order to build complete React applications on Salesforce.
Follows the generating-lightning-app pattern with explicit skill load
calls for each phase: scaffolding → features → data access → UI →
integrations → deployment → experience site.
* Clean up building-ui-bundle-app skill @W-21338965@
- Remove Skill Registry section (redundant with Dependency Graph + Execution Workflow)
- Remove "Skill to load" lines from Dependency Graph phases (duplicated in per-phase execution steps)
- Remove Best Practices 2 & 3 (duplicated in Execution Workflow and Phase 2 description)
- Fix SKILL LOAD ORDER numbering: flat 1-8 → 5a/5b to match phase numbering in Dependency Graph
- Clarify GraphQL schema re-fetch in Phase 6 is a post-deployment remote schema fetch
- Add parallel execution guidance to Phase 5 execution block
* Make Phase 2 (Features) optional @W-21338965@
* Address review feedback: use non-LWC terminology instead of React-specific
Co-authored-by: dme722
* Fix building-ui-bundle-app skill: remove special chars, align with actual skills
- Replace non-ASCII characters (arrows, circled numbers, checkmarks, em dashes)
that cause silent failures in Cline
- Fix incorrect skill name generating-ui-bundle-ui -> building-ui-bundle-frontend
- Align phase diagrams with actual skill workflows (add missing steps for
scaffolding npm install, features search-first flow, data validation step,
deployment final build and full post-deploy config)
- Fix Phase 4 diagram to match building-ui-bundle-frontend task categories
Made-with: Cursor
