@W-21582128@: Introduce Skill to Construct a Salesforce Experience React Site

[MadMagyar92]

References: Contributing guide · Skill authoring guide · Agent Skills spec

What changed

• Added a new Skill for Experience React Sites
• Renamed the existing Experience Sites Skill to reflect the use-case for Experience LWR Sites

Why

• Provides a way for Salesforce customers to seamlessly create and modify metadata for a Salesforce Experience React Site through Agentforce Vibes or any other editor with LLM Agent capabilities.

Notes

Needed for TDX.

---

Skills

Manual checklist

Description quality

• Describes what the skill does and the expected output
• Includes relevant Salesforce domain keywords (Apex, LWC, SOQL, metadata types, etc.)
• Trigger phrases are specific enough for Vibes to select this skill reliably

Instructions

• Clear goal statement
• Step-by-step workflow
• Validation rules for generated output
• Defined output / artifact

Context efficiency

• Core instructions are concise — supporting material lives in templates/, examples/, or docs/ subdirectories
• No unnecessary background explanation in the body

Automated checks

Enforced by CI (npm run validate:skills) per the Agent Skills spec:

• Directory is one level deep, named in kebab-case (max 64 chars), contains SKILL.md
• Frontmatter name matches directory name; description is present, ≥ 20 words, ≤ 1024 characters, and includes trigger language
• Body is non-empty and under 500 lines
• Name uses gerund form ⚠ (warning — does not block merge)

[MadMagyar92]

This change is also present in @scottmo 's PR: #27

[MadMagyar92]

This change is also present in @scottmo 's PR: #27

[hsinghbisht-sfdc]

Please follow the recommended naming recommendation for skills

Just to follow consistent pattern which we are about to do for all other existing type is generating* i.e. generating-experience-lwr-site

[MadMagyar92]

We delegate each metadata file template to a doc as reference. In the future, these could be made a part of an sf generate command. However, since these is no such command at this time, using these sub files.

[MadMagyar92]

I need to:

1. change this get_metadata_api_context call to either get_metadata_type_context or get_metadata_type_fields
2. move this to Step 3

[MadMagyar92]

This needs to use either get_metadata_type_fields and/or get_metadata_type_fields_properties to determine the field purposes for additional configurations. Maybe this could use some of the output from Step 3

[MadMagyar92]

@hsinghbisht-sfdc The Expert for this Skill was already present in 260/patch (not main), so it wasn't copied over. Adding it now as part of this PR.