@W-19758448 Create PWA-Kit MCP Rules to guide the agent into optimal tool use

[patricksullivansf]

Description

Features:

• cursor specific tool usage guidance and post tool usage instructions
• generic AGENTS.md alternative
• semi-automatic installation and update via prompt. e.g. “Install the Agent MCP Tool Usage Guidelines”
• Site test URL default is removed and prompting enforced
• tools prefixed with "b2c_" to reduce bad effects from tool name collision

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

• (change1)

How to Test-Drive This PR

Follow the steps in the PWA-Kit readme for local development and deployment. Then try prompts like the following:

• "Install the Agent MCP Tool Usage Guidelines" with and without a pre-existing rule file. On cursor and other IDEs.
• "i want to test my app performance"
• "make a component CatViewer that shows a static image of a cat"

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[cc-prodsec]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[shauryemahajanSF]

While we're renaming these, what do you think about having "sample" in these tool names. I feel like it would be clearer if they were just create_component and create_page.

[knhage]

@patricksullivansf I agree with @shauryemahajanSF's suggestion. I suggested removing "sample" in the last round of tool name updates that @sneh171196 did. The reason for my opposition for including the word "sample" is that we aren't creating a complete sample. For example, the component created still needs the user to add property values to it for it work. Using the word "sample" is misleading because it would make people believe that they're getting the full working sample while it is not.
By the way, why is your version not showing the latest updates that Sneha did? Is this the latest branch?

[wei-liu-sf]

yeah seems that @patricksullivansf is not on the latest develop

[patricksullivansf]

I see what you mean. _sample_ is now removed tool names in this PR.

[shauryemahajanSF]

Do we want to consider prefixing these with pwa_ instead of b2c_ , since its more precise.

[knhage]

Wouldn't it be necessary to add the Salesforce company name before b2c_? What if another company also creates an MCP server with the same b2c_ prefix? So for example, it could be sfb2c_.