flow-best-practices

Enforce flow design best practices in Salesforce automation.

2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/bhanu91221/claude-sfdx-iq --skill flow-best-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-best-practices
Source: https://github.com/bhanu91221/claude-sfdx-iq/tree/main/skills/flow-best-practices
Command: npx skills add https://github.com/bhanu91221/claude-sfdx-iq --skill flow-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flow design best practices including entry conditions, fault paths, bulkification, and naming conventions.

Core Features & Use Cases

  • Fault-path discipline: ensure every element has a fault path and proper logging.
  • Bulkification patterns: use collection variables and DML outside loops to respect governor limits.
  • Standardized naming: consistent flow and element naming to improve readability and maintenance.
  • Versioning and governance: guidelines for version control, testing, and deployment.

Quick Start

Review your Salesforce flows and apply these best practices to improve reliability and maintainability.

Frequently Asked Questions about flow-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bulkify Salesforce flows to avoid governor limits?

To bulkify Salesforce flows, use collection variables and perform DML operations outside loops. This pattern respects governor limits by processing records in bulk rather than individually.

What are the best practices for fault path design in Salesforce flow?

Fault path design in Salesforce flow requires ensuring every element has a fault path with proper logging. This discipline reduces runtime errors and improves automation reliability by handling exceptions safely.

How do I set naming conventions for Salesforce flow elements?

Naming conventions for Salesforce flow elements involve applying consistent names to flows and components. Standardized naming improves readability, simplifies maintenance, and clarifies variable usage across the automation.

Why do I need entry-condition optimization for record-triggered flows?

Entry-condition optimization for record-triggered flows prevents unnecessary executions by filtering records early. This reduces deployment risk and ensures the flow only runs when specific criteria are met.

Can I apply flow governance and versioning to autolaunched and scheduled flows?

Yes, flow governance and versioning guidelines apply to autolaunched and scheduled flows. These practices ensure consistent version control and testing across all Salesforce automation types to reduce deployment risk.