From a2c26f310d0ca1269ee1ff73edc2243c06048537 Mon Sep 17 00:00:00 2001 From: jluftglidden-tilt <53275453+jluftglidden-tilt@users.noreply.github.com> Date: Thu, 26 Mar 2026 04:54:14 -0700 Subject: [PATCH] @W-21467732 Update react SKILL.md to add an execution note to doc read (#108) Update SKILL.md to add an execution note to doc read Co-authored-by: Hemant Singh Bisht --- skills/generating-experience-react-site/SKILL.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/skills/generating-experience-react-site/SKILL.md b/skills/generating-experience-react-site/SKILL.md index 4ab563d..ab2acec 100644 --- a/skills/generating-experience-react-site/SKILL.md +++ b/skills/generating-experience-react-site/SKILL.md @@ -51,6 +51,17 @@ Use the default templates in the docs below. Values in `{braces}` are resolved p | DigitalExperienceBundle | [configure-metadata-digital-experience-bundle.md](docs/configure-metadata-digital-experience-bundle.md) | | DigitalExperience (sfdc_cms__site) | [configure-metadata-digital-experience.md](docs/configure-metadata-digital-experience.md) | +### Execution Note for Step 3: Load and use the docs +- Agents MUST read the full contents of each docs/*.md file referenced in Step 3 before attempting to populate metadata fields. +- Use your platform's file-read tool (for example, `read_file`) to load these files in full, then perform placeholder substitution for values in `{braces}` using the resolved properties from Step 1. +- Files to load: + - `docs/configure-metadata-network.md` + - `docs/configure-metadata-custom-site.md` + - `docs/configure-metadata-digital-experience-config.md` + - `docs/configure-metadata-digital-experience-bundle.md` + - `docs/configure-metadata-digital-experience.md` +- Read entire file contents, replace placeholders (e.g. `{siteName}`) with the resolved values, then use the expanded templates to populate the metadata XML/JSON content. + ### Step 4: Resolve Additional Configurations Address any extra configurations the user requests. Use the schemas returned by `get_metadata_api_context` in Step 2 to understand each field's purpose, and update only the minimum necessary fields.