feat: add experimental sf-multiframework extension#501
Open
bjwise96 wants to merge 1 commit into
Open
Conversation
|
Thanks for the contribution! Before we can merge this, we need @bjwise96 to sign the Salesforce Inc. Contributor License Agreement. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an experimental
sf-multiframeworkbundled extension for Salesforce Multi-Framework React UI Bundle work.V1 is intentionally skill-first rather than tool-first:
/sf-multiframeworkfor status/checklist/Experience route remindersskills/sf-multiframework/SKILL.mdsf_apex,sf_soql,sf_browser,code_analyzer) instead of introducing a new native LLM tool prematurelyThe extension is based on findings from an end-to-end Community Resilience Grants Multi-Framework demo with:
CustomApplicationExperienceUI Bundle@salesforce/platform-sdkWhy
Multi-Framework work currently falls between generic LWC, Apex, metadata, and browser guidance. The main hard parts are template selection, current generated metadata shape, build artifact hygiene, and Experience Cloud access/security setup. A bundled sf-pi skill gives agents a first-class routing target for this work before they fall back to generic Salesforce skills.
Validation
npm run generate-catalog:checknpm run format:checknpm run check -- --pretty falsenpm test -- extensions/sf-brain/tests/extension-context.test.tsNotes
This PR intentionally does not add an
sf_multiframeworkLLM tool. A future tool could inspect local UI Bundle shape, stale build artifacts, Experience metadata wiring, and package/import drift once the deterministic lifecycle surface is clearer.