Overview Version History Q & A Rating & Review
SF ERIO
Elevate Requirements Into Outcomes
SF ERIO turns a normal Salesforce user story into Draft metadata you can review, validate, and deploy — Flows, Apex, LWC, and Experience Cloud LWR assets — without starting from a blank Setup screen.
Analysis and generation run on your machine . You stay in control of what gets written and what gets pushed to the org.
What you get
Story → design — Objects, fields, Flow vs Apex path, and a checklist as you type
Intent Mirrors — Pick the builder shape that matches the story before Generate
Draft metadata — Auto-Layout Flows stay Draft (SF ERIO never activates Flows)
Apex / LWC / Experience when the story needs them
Validate & Deploy — Salesforce CLI dry-run first; deploy only what you check
Update existing Flow — Retrieve an Active Flow and merge generated elements
History — Recent stories and results for quick reload
Engines
Engine
When to use
Rules
Default. Spec patterns + bundled trained assist. Fully offline for coding assist.
Local LLM
Optional on-device 3B/7B model (one-time download). Spec still writes Flow metadata.
Host AI
Optional IDE language model (Cursor / Copilot, etc.) to help refine the story.
Tip: On corporate networks that block Hugging Face, keep Rules — you do not need a Local LLM download to generate.
Requirements
Visual Studio Code 1.85 or later (or Cursor)
An SFDX / Salesforce DX project folder open as the workspace
Salesforce CLI (sf) authenticated to a target org for describe, validate, and deploy
Get started
Open your Salesforce project folder.
Click the SF ERIO icon in the activity bar (opens an editor tab).
Choose a Target org in the header (or Connect / Refresh from Salesforce CLI).
Paste the full user story.
When Intent Mirrors appear, select the shape that fits.
Click Generate and validate .
Files are written under your project’s default package directory. Review Generated components , then Deploy when validation succeeds.
Useful commands
SF ERIO: Generate from Selection — selection in the editor
SF ERIO: Analyze Selection — design only
SF ERIO: Generate from File — explorer context menu on .md / .txt
SF ERIO: Connect Org — sf org login web
How generation works
Analyze the story (objects, path, mirrors, mockup).
Generate Draft Flow / Apex / LWC / Experience files locally.
Validate with a check-only deploy against the selected org.
Deploy selected members when you are ready — still as Draft where Salesforce allows.
You can uncheck components so they stay local-only.
Settings (optional)
Setting
Purpose
salesforceFlow.targetOrg
CLI org alias or username (empty = CLI default)
salesforceFlow.engine
local (Rules), localLlm, or ai (Host AI)
salesforceFlow.languageModelId
Host AI model id (empty = first available)
salesforceFlow.localLlm.size
3b or 7b for optional Local LLM
salesforceFlow.showRevertButtons
Show Revert on Advanced fields
Privacy
Rules — story and metadata stay on your PC; no cloud model call for Spec generation.
Local LLM — model files download once into extension storage; inference stays local.
Host AI — only if you choose it; the story may be sent to the IDE’s language-model provider.
Org credentials use Salesforce CLI auth you already manage.
License
MIT