* @W-21817314@ Improved lwr and ui bundle site's skill to identify what properties should be updated for when user request for site URL update
Signed-off-by: Daily Dai <lei.dai@salesforce.com>
* fix skill name
Signed-off-by: Daily Dai <lei.dai@salesforce.com>
* fix skill name
Signed-off-by: Daily Dai <lei.dai@salesforce.com>
* move url update into its own doc md file
Signed-off-by: Daily Dai <lei.dai@salesforce.com>
* clarify search_files is an agent tool instead of command line
Signed-off-by: Daily Dai <lei.dai@salesforce.com>
---------
Signed-off-by: Daily Dai <lei.dai@salesforce.com>
* Moving SKILL.md to generating-ui-bundle-site
* Rename configure-metadata-custom-site.md to configure-metadata-custom-site.md
* Rename configure-metadata-digital-experience-bundle.md to configure-metadata-digital-experience-bundle.md
* Moving configure-metadata-digital-experience-config.md to generating-ui-bundle-site
* Moving configure-metadata-digital-experience.md to generating-ui-bundle-site
* Moving configure-metadata-network.md to generating-ui-bundle-site
fix: derive router basename from <base href> at runtime
Add guidance to building-ui-bundle-frontend skill to always derive
the client-side router basename from the document's <base href> tag
instead of hardcoding it.
* 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
* Rename webapplication skills to ui-bundle
Rename all 7 webapplication skill directories and their content to use
the "ui-bundle" / "UIBundle" naming convention, aligning with the
New++ (TDX) naming strategy.
Directory renames:
- deploying-webapplication → deploying-ui-bundle
- generating-webapplication-{features,metadata,ui} → generating-ui-bundle-*
- implementing-webapplication-{agentforce-conversation-client,file-upload} → implementing-ui-bundle-*
- using-webapplication-salesforce-data → using-ui-bundle-salesforce-data
Content updates across all skills:
- Frontmatter name fields
- Prose: "web application" → "UI bundle"
- Metadata refs: WebApplication → UIBundle, webapplications/ → uiBundles/
- CLI: sf webapp → sf ui-bundle
- NPM packages per rename table
- Cross-skill references and generating-experience-react-site refs
* Rename generating-ui-bundle-ui skill to building-ui-bundle-frontend
The "ui-bundle-ui" name was confusing. "building-ui-bundle-frontend"
better conveys that this skill handles the React frontend layer
within a UI bundle.
---------
Co-authored-by: gbockus-sf <76090802+gbockus-sf@users.noreply.github.com>
* W-21672186: Migrate mobile rental app to data providers and design tokens
* Update rental app home screen to use CamaDataService
Replace PortalService with CamaDataService and remove cama_dev namespace for all data providers in the home screen.
---------
Co-authored-by: gbockus-sf <76090802+gbockus-sf@users.noreply.github.com>
* Split generating-webapp-metadata into single-purpose skills
Extract the deployment sequence into a new deploying-webapp skill so each
webapp skill describes exactly one actionable goal. This improves agent
skill selection accuracy by eliminating multi-concern descriptions.
- generating-webapp-metadata: now focused on scaffolding, bundle config, CSP
- deploying-webapp: new skill for the 7-step deployment sequence
* Rename -webapp- skill directories and references to -webapplication-
Rename all 7 webapp skill directories to use the full "webapplication"
entity name. Update frontmatter name fields, cross-skill references,
and descriptive prose. Package names and CLI commands are preserved
as-is since those are actual identifiers.
* Removed prompts folder; no longer needed
* Removed various folders in rules (except experts global rule); no longer needed
* Updated README file, removed lots of extraneous text
* Add instructions to create commerce b2b store from vibes
* update rule and sf commands
* Refactor Commerce B2B skill: rename and flatten directory structure
- Rename skill from create-b2b-commerce-storefront to creating-b2b-commerce-store to better reflect what users actually create (the Store, not the Storefront)
- Flatten directory from skills/commerce/create-b2b-commerce-storefront/ to skills/creating-b2b-commerce-store/ to match repository pattern
- Remove old prompts and rules consolidated into skill
- Remove Commerce prompt and rule entries from manifest.json (consolidated into skill)
fix: use glob pattern in .gitignore to track sample lib/ folders
The lib/ negation rules had incorrect webapp folder names
(appreactsampleb2e/appreactsampleb2x instead of
propertymanagementapp/propertyrentalapp), causing the sample lib/
directories to remain git-ignored. Replaced with a simpler
!samples/**/lib/ glob that is resilient to future name changes.
Made-with: Cursor
W-21745944 make deployment command use --dry-run, add strict guardrails to prevent agent from further editing page
Co-authored-by: Hemant Singh Bisht <hsinghbisht@salesforce.com>
