Agent skill · product strategy · github
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.
Why this skill is useful
Provides specific architectural patterns and validation standards for Salesforce Flow design that the AI wouldn't reliably generate on its own.
What it needs
Requires salesforce account access. About 5k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
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 Cannot be triggered by a record event automatically Reusable background logic called from another Flow Autolaunched (Subflow) Input/output variables define the contract Logic invoked from Apex @InvocableMethod Autolaunched (Invocable) Must declare input/output variables Time-based batch processing Scheduled Flow Runs in batch context — respect governor limits Respond to events (Platform Events / CDC) Platform Event–Triggered Runs asynchronously — eventual consistency Decision rule: choose before-save when you only need to change the triggering record's own fields. Move to after-save the moment you need to touch related records, send emails, or make callouts. Step 3 — Bulk Safety Checklist These patterns are governor limit failures at scale. Check for all of them before the Flow is activated. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/salesforce-flow-design