claude-sfdx-iq is a Claude Code plugin that transforms Claude into an expert Salesforce developer, architect, and admin — all at once
Agent
Part of sfdx-iq
Use this agent to review Apex code (classes, triggers, batch, queueable, schedulable) for best practices, governor limit risks, bulkification, SOQL performance, naming conventions, security, and code quality. Produces a structured review with severity-rated findings.
Agent
Part of sfdx-iq
Use this agent for Salesforce DevOps tasks including deployment strategy, test patterns (TDD, TestDataFactory, mocks), org health analysis, metadata dependency mapping, technical debt identification, and CI/CD pipeline configuration.
Agent
Part of sfdx-iq
Use this agent to analyze Salesforce Flows for best practices including DML optimization, fault path coverage, before-save vs after-save patterns, subflow decomposition, variable naming, and recursion prevention.
Agent
Part of sfdx-iq
Use this agent for Salesforce integration patterns including Named Credentials, REST/SOAP callouts, Platform Events, Change Data Capture, async callout patterns, retry with exponential backoff, and circuit breaker implementation.
Agent
Part of sfdx-iq
Use this agent to review Lightning Web Components for best practices including proper decorator usage, lifecycle hooks, event handling, accessibility, CSS patterns, import conventions, and component composition.
Agent
Part of sfdx-iq
Use this agent to review Salesforce code and configuration for security vulnerabilities including CRUD/FLS enforcement, sharing model compliance, SOQL injection, CSP compliance, Connected App security, and Experience Cloud guest user risks.
Agent
Part of sfdx-iq
Use this agent for Salesforce solution architecture and implementation planning. Covers data model design, integration architecture, scalability planning, packaging strategy, declarative-vs-code decisions, phased implementation roadmaps, and dependency mapping. Best for greenfield projects, major refactors, or complex…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: