Recommends Claude model tier (haiku, sonnet, opus) for Salesforce tasks based on Apex complexity, deploy risk, and budget. Invoke before tasks where model affects quality or cost.
npx claudepluginhub jiten-singh-shahi/salesforce-claude-code --plugin salesforce-claude-codeThis skill uses the workspace's default tool permissions.
Recommend the best model tier for the current task by complexity and budget.
Routes Claude Code tasks to optimal models (Haiku, Sonnet, Opus) using decision matrices, cost tables, complexity signals, and subagent assignments for cost/quality tradeoffs.
Routes coding tasks to optimal AI model tier by complexity: no LLM for mechanical edits, Haiku for simple refactors, Sonnet for multi-file bugs, Opus for architecture/security. Saves 50-65% API costs.
Recommends Claude models (Haiku for exploration, Sonnet for implementation, Opus for decisions) via routing matrix for task types, subagents, and cost-quality tradeoffs.
Share bugs, ideas, or general feedback.
Recommend the best model tier for the current task by complexity and budget.
/model-route [task-description] [--budget low|med|high]
haiku: deterministic, low-risk mechanical changessonnet: default for implementation and refactorsopus: architecture, deep review, ambiguous requirementsModel names (haiku, sonnet, opus) refer to the current Claude model mapped to that tier in your Claude Code configuration.
Use opus when the task requires deep understanding of Salesforce architecture, security implications, or governor limit analysis across multiple execution paths.
| Task | Why Opus |
|---|---|
| Governor limit audit across trigger/flow/batch chains | Must trace cumulative DML/SOQL across async boundaries, understand order of execution, and reason about worst-case heap/CPU scenarios |
Security review of @RestResource or with sharing/without sharing decisions | Requires nuanced reasoning about record access, CRUD/FLS enforcement, SOQL injection vectors, and org-wide defaults |
| Architecture review for large-scale data model changes | Must evaluate cascade effects on triggers, flows, validation rules, sharing rules, and downstream integrations |
Use haiku when the task is deterministic, well-scoped, and unlikely to have subtle correctness issues.
| Task | Why Haiku |
|---|---|
Formatting LWC components (fix indentation, add missing @api decorators) | Purely mechanical — no logic changes, just style compliance |
| Simple Apex fixes (rename a variable, fix a typo in a label, add a missing null check) | Single-line or few-line changes with obvious correctness |
Adding <meta.xml> boilerplate or updating apiVersion across components | Repetitive, pattern-based edits with no ambiguity |
Use sonnet (default) for standard development work that requires understanding but follows well-known patterns.
| Task | Why Sonnet |
|---|---|
| Code review of an Apex trigger handler or service class | Needs to understand patterns and spot issues, but follows standard review criteria |
Generating Apex test classes with @TestSetup, mocking, and assertions | Requires understanding the class under test, but test generation follows repeatable patterns |
| Implementing a new LWC component with wire adapters and error handling | Standard implementation work — needs context awareness but not deep architectural reasoning |
[task-description] optional free-text--budget low|med|high optional/model-route Review the sharing model for the new Patient__c object hierarchy
/model-route Fix the CSS alignment on the accountDashboard LWC --budget low
/model-route Generate test coverage for OpportunityTriggerHandler
/model-route Audit all SOQL queries in force-app for governor limit risks --budget high