kris/afv-library
1
0
Fork 0
mirror of https://github.com/forcedotcom/afv-library.git synced 2026-08-07 16:04:41 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge branch 'main' into experience-lwr-site

Browse Source
This commit is contained in:
Scott Mo 2026-03-13 10:03:04 -05:00 committed by GitHub
commit 015aba9161
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
rules/a4v-expert-global-rule.md
View File

@ -8,7 +8,7 @@ Enforce: **skill load → API context → file generation** for all Salesforce m
1. **Never write** without both: metadata type skill loaded AND `get_metadata_api_context` called for that type
2. **One type at a time** - complete full cycle before next type
3. **One type per API call** - no batching
4. **No cross-type content** in files
4. **Child types need own context** - if adding any child metadata inside a parent metadata's file, load skill and call `get_metadata_api_context` for each child type (e.g. CustomField inside CustomObject) separately; don't rely on the parent's schema for creating child metadata
5. **Max one clarifying question** before starting
## Workflow
@ -51,9 +51,9 @@ Enforce: **skill load → API context → file generation** for all Salesforce m
### 3. Deploy Verification
```bash
sf project deploy start --dry-run -d "<path>" --target-org <alias> --test-level NoTestRun --wait 10 --json
sf project deploy start --dry-run -d "force-app/main/default" --target-org <alias> --test-level NoTestRun --wait 10 --json
```
On failure: attempt to fix the errors and re-run, retrying up to a maximum of 5 times until it succeeds.
On failure: attempt to fix the errors and re-run, retrying up to a maximum of 3 times until it succeeds.
## Anti-Patterns

4
skills/salesforce-flow/SKILL.md
View File

@ -1,6 +1,6 @@
---
name: salesforce-flow
description: Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen, Autolaunched, Record-Triggered (before/after-save), Scheduled, or Platform Event-Triggered Flows. Also trigger for flow-like requests such as "when a record is created", "trigger daily at", "send an email when", "update the field when", "automate", "workflow", or "flow XML/metadata". This is the only skill for Salesforce Flow generation.
description: Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen, Autolaunched, Record-Triggered (before/after-save), Scheduled. Also trigger for flow-like requests such as "when a record is created", "trigger daily at", "send an email when", "update the field when", "automate", "workflow", or "flow XML/metadata". This is the only skill for Salesforce Flow generation.
---
## Goal
@ -21,7 +21,7 @@ Use this skill when you need to:
# Flow Metadata Specification
## Overview
Salesforce Flows are powerful automation tools that enable complex business process automation without code. Flows can collect and process data through interactive screens, execute logic and calculations, manipulate records, call external services, and trigger based on various events. Flow types include Screen Flows (user-guided), Autolaunched Flows (background processing), Record-Triggered Flows (database events), Scheduled Flows (time-based), and Platform Event-Triggered Flows (event-driven).
Salesforce Flows are powerful automation tools that enable complex business process automation without code. Flows can collect and process data through interactive screens, execute logic and calculations, manipulate records, call external services, and trigger based on various events. Flow types include Screen Flows (user-guided), Autolaunched Flows (background processing), Record-Triggered Flows (database events) and Scheduled Flows (time-based).
## Purpose
- Automate complex business processes with declarative logic and branching