Scaffolds the explaining-batch-data-transform skill directory and delivers
the full, production-grade SKILL.md body. 194 lines.
Directory layout established (skills/explaining-batch-data-transform/):
- SKILL.md — the entry point this commit adds
- scripts/ — parser lands in commit 2
- references/, assets/ — reference docs + samples land in commit 3
- tests/ — unit tests + fixtures land in commit 4
SKILL.md frontmatter:
- name, description, tier, and owner fields matching the library's CI
validator schema.
- Description covers the full production surface: "Explain, audit, and
trace Salesforce Data Cloud Batch Data Transform (BDT) JSON — sources,
sinks, stages, lineage, field traces, formulas, multi-definition
payloads, and dual input shapes (editor export + Connect API)."
SKILL.md body (12 sections):
1. When to use this skill
2. Inputs you accept (editor export, Connect API single-definition,
Connect API multi-definition payloads)
3. Mode A — structural survey (summary / sources / outputs / stages)
4. Mode B — per-node explanation (nodes / node)
5. Mode C — lineage + field trace
6. Mode D — formulas and windows
7. Question routing table (user phrasing -> CLI subcommand)
8. Multi-definition payload handling (--definition flag semantics)
9. Troubleshooting (malformed JSON, unknown node refs, broken upstream)
10. Non-goals as explicit "Do not" directives (no execution, no schema
inference beyond what the JSON states, no speculation about runtime)
11. References + sample BDTs index
12. Exit-code + error-class contract surfaced from bdt_analyze.py
Structure passes the repo's skill-validator (npm run validate:skills):
single top-level H1, required sections present, frontmatter schema
aligned, no broken internal links.
@W-22196528@
* feat: add SLDS applying and auditing quality skills
Two new skills for SLDS v2 compliance:
- applying-slds: guides artifact selection, styling hooks, utilities, icons
- auditing-slds-quality: scored quality audit with linter + static analysis
Made-with: Cursor
* refactor: rename auditing-slds-quality skill to validating-slds
Renames the skill directory and updates all references in
applying-slds/SKILL.md and applying-slds/checklists.md.
Made-with: Cursor
* fix: improve accuracy and add manual review gate across SLDS skills
Correct hook families, badge modifiers, and severity levels; add a
manual review gate to validating-slds so automated grades alone cannot
declare production readiness; make analyze-quality.cjs portable with
explicit --hooks-index flag; remove dead parseYaml code; add version
field to all three skill frontmatters.
Made-with: Cursor
* chore: retrigger CI
Made-with: Cursor
* fix: quote YAML descriptions and improve color hook disambiguation
- Quote description frontmatter in all three skills for valid YAML
(inner double quotes now escaped)
- Strengthen Step 4 directive: MUST read color-hooks guide before
choosing a hook — linter suggestions are unranked
- Add surface vs surface-container disambiguation table
- Add accent hook context table and state progression
- Add standalone-component exception for surface classification
- Add modal background example to examples.md
- Remove redundant brand-button example (covered by new context table)
Made-with: Cursor
feat: replace agentforce-development skill with three specialized skills
Replace the monolithic agentforce-development skill with three focused skills:
- developing-agentforce: For creating and authoring Agentforce agents
- observing-agentforce: For monitoring and debugging agents
- testing-agentforce: For validating agent behavior
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
chore: sync React B2E (1.120.6) & B2X (1.120.6) samples with lockfiles and gitignore
Add package-lock.json generation for uiBundle directories and .gitignore
writing to the sync scripts so they persist across syncs.
Co-authored-by: gbockus-sf <76090802+gbockus-sf@users.noreply.github.com>
* fix: trigger ui-bundle skill for React application prompts
Add React-specific trigger language to building-ui-bundle-app description
so prompts like "I want to build a react application" activate the
ui-bundle orchestrator even without existing project files.
* fix: correct stale related-skill reference
Rename generating-experience-react-site to generating-ui-bundle-site
in building-ui-bundle-app related-skills to match the actual skill name.
* fix: tighten skill descriptions to reduce false triggers
- generating-ui-bundle-metadata: remove generic triggers (metadata, new app,
meta XML, configuration), update command to sf template generate ui-bundle,
add --template reactbasic flag
- building-ui-bundle-app: reframe as orchestrator for multi-skill ui-bundle
work, distinguish from generating-lightning-app
* fix: improve ui-bundle skill descriptions to reduce false triggers and improve activation
- Add MUST activate + file-pattern triggers to all 9 ui-bundle skills
- Remove overly specific examples that waste context tokens
- Scope features skill to authentication and search only
- Add boundary language between orchestrator and frontend skills
- Update metadata skill to use sf template generate ui-bundle --template reactbasic
* fix: standardize uiBundles/*/src/ directory trigger across all ui-bundle skills
* fix: remove React references from skill descriptions for framework agnosticism
* fix: standardize uiBundles/*/src/ trigger in agentforce and data skills
* fix: add 'Use this skill when' trigger context to all ui-bundle skill descriptions
* fix: require mobile-responsive UI in building-ui-bundle-frontend skill
* fix(using-ui-bundle-salesforce-data): condense reference into skill
also adds, operation types, script section type and mix instructions as comments in the examples. it also adds a section to avoid the llm being eager to show progress on ui-scaffold
* fix: workaround llm being eager to scaffold ui
* fix: delete testing with sf cli
* fix: add summary table for workflow steps
---------
Co-authored-by: Hemant Singh Bisht <hsinghbisht@salesforce.com>
@W-21861732 fix: convert native mobile rental tenant app README from RTF to Markdown
The README was accidentally saved in RTF format, causing rendering
issues. Stripped RTF formatting and restored plain Markdown.
Co-authored-by: gbockus-sf <76090802+gbockus-sf@users.noreply.github.com>
* @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
