salesforce-flow-design
Salesforce Flow architecture decisions, flow type selection, bulk safety validation, and fault handling standards. Use this skill when designing or reviewing Record-Triggered, Screen, Autolaunched, Scheduled, or Platform Event flows to ensure correct type selection, no DML/Get Records in loops, proper fault connectors on all data-changing elements, and appropriate automation density checks before deployment.
Profile →npx skills add github/awesome-copilot --skill salesforce-flow-design --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Salesforce Flow Design and Validation Apply these checks to every Flow you design, build, or review. ## Step 1 — Confirm Flow Is the Right Tool Before designing a Flow, verify that a lighter-weight declarative option cannot solve the problem: | Requirement | Best tool | |---|---| | Calculate a field value with no side effects | Formula field | | Prevent a bad record save with a user message | Validation rule | | Sum or count child records on a parent | Roll-up Summary field | | Complex multi-object logic, callouts, or high volume | Apex (Queueable / Batch) — not Flow | | Everything else | Flow ✓ | If you are building a Flow that could be replaced by a formula field or validation rule, ask the user to confirm the requirement is genuinely more complex. ## Step 2 — Select the Correct Flow Type | Use case | Flow type | Key constraint | |---|---|---| | Update a field on the same record before it is saved | Before-save Record-Triggered | Cannot send emails, make callouts, or change related records | | Create/update related records, emails, callouts | After-save Record-Triggered | Runs after commit — avoid recursion traps | | Guide a user through a multi-step UI process | Screen Flow |
- Step 1 — Confirm Flow Is the Right Tool
- Step 2 — Select the Correct Flow Type
- Step 3 — Bulk Safety Checklist
- DML in Loops — Automatic Fail
- Get Records in Loops — Automatic Fail
- Correct Bulk Pattern
- Transform vs Loop
- Step 4 — Fault Path Requirements
- Elements That Require Fault Connectors
- Fault Handler Pattern
- Step 5 — Automation Density Check
- Step 6 — Screen Flow UX Guidelines
- Step 7 — Deployment Safety
- Quick Reference — Flow Anti-Patterns Summary
What does the salesforce-flow-design skill do?
Salesforce Flow architecture decisions, flow type selection, bulk safety validation, and fault handling standards. Use this skill when designing or reviewing Record-Triggered, Screen, Autolaunched, Scheduled, or Platform Event flows to ensure correct type selection, no DML/Get Records in loops, proper fault connectors on all data-changing elements, and appropriate automation density checks before deployment.
How do I install it?
Run `npx skills add github/awesome-copilot --skill salesforce-flow-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.