Salesforce Flow Design

Catches the mistakes that blow up in production after a deployment. Before you activate any Salesforce Flow, this walks through bulk safety (DML in loops, SOQL in loops), fault connectors on every element that can fail, flow type selection, and automation density checks to avoid triggering conflicts. The bulk pattern guidance is especially useful because that's what kills most flows at scale. Also includes a decision tree for when to just use a formula field instead of overengineering it. If you're building or reviewing flows regularly, the anti-pattern table alone is worth keeping open.

skills.sh installs: 839
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill salesforce-flow-design --agent claude-code

Installs into .claude/skills of the current project.

Files

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.