~ / rigs / karkranikhil / sf-ai-toolkit

karkranikhil/sf-ai-toolkit

Make Salesforce DX projects AI-ready with a CLI and VS Code extension that scaffold Cursor/Claude setup, MCP config, diagnostics, and safe deployment guardrails.

↗ GitHub ★ 2 MIT updated 5mo ago project Claude CodeCodex
share on X
ARCHETYPE
Orchestrator
A bench of specialised subagents. The main agent mostly delegates.
CONTEXT TAX · EVERY TURN
~5.3k tokens
Moderate · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details

Copy this rig

# review before running: this installs third-party code
$ npx degit karkranikhil/sf-ai-toolkit/examples/existing-project-after/.claude ./rig-sf-ai-toolkit  # inspect, then merge into .claude/

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ curl -fsSL --create-dirs -o .claude/agents/apex-developer.md https://raw.githubusercontent.com/karkranikhil/sf-ai-toolkit/main/examples/existing-project-after/.claude/agents/apex-developer.md
$ curl -fsSL --create-dirs -o .claude/agents/lwc-developer.md https://raw.githubusercontent.com/karkranikhil/sf-ai-toolkit/main/examples/existing-project-after/.claude/agents/lwc-developer.md
$ curl -fsSL --create-dirs -o .claude/agents/qa-tester.md https://raw.githubusercontent.com/karkranikhil/sf-ai-toolkit/main/examples/existing-project-after/.claude/agents/qa-tester.md
$ curl -fsSL --create-dirs -o .claude/agents/salesforce-architect.md https://raw.githubusercontent.com/karkranikhil/sf-ai-toolkit/main/examples/existing-project-after/.claude/agents/salesforce-architect.md
$ curl -fsSL --create-dirs -o .claude/agents/security-reviewer.md https://raw.githubusercontent.com/karkranikhil/sf-ai-toolkit/main/examples/existing-project-after/.claude/agents/security-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/apex-developer.md https://raw.githubusercontent.com/karkranikhil/sf-ai-toolkit/main/examples/existing-project-before/.claude/agents/apex-developer.md
$ curl -fsSL --create-dirs -o .claude/agents/lwc-developer.md https://raw.githubusercontent.com/karkranikhil/sf-ai-toolkit/main/examples/existing-project-before/.claude/agents/lwc-developer.md
$ curl -fsSL --create-dirs -o .claude/agents/qa-tester.md https://raw.githubusercontent.com/karkranikhil/sf-ai-toolkit/main/examples/existing-project-before/.claude/agents/qa-tester.md
$ curl -fsSL --create-dirs -o .claude/agents/salesforce-architect.md https://raw.githubusercontent.com/karkranikhil/sf-ai-toolkit/main/examples/existing-project-before/.claude/agents/salesforce-architect.md
$ curl -fsSL --create-dirs -o .claude/agents/security-reviewer.md https://raw.githubusercontent.com/karkranikhil/sf-ai-toolkit/main/examples/existing-project-before/.claude/agents/security-reviewer.md

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 7,204 rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(rm -rf *)",
      "Read(**/*.pem)",
      "Bash(rm -rf /)",
      "Bash(git push --force:*)",
      "Bash(sudo *)",
      "Read(.env)",
      "Bash(rm -rf /*)",
      "Read(./.env.*)",
      "Read(~/.aws/**)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(sudo:*)",
      "Bash(git reset --hard*)",
      "Bash(git reset --hard:*)",
      "Read(.env.*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(rm:*)",
      "Bash(git rebase *)",
      "Bash(wget *)",
      "Bash(npm publish:*)",
      "Bash(git commit *)",
      "Bash(gh pr merge *)"
    ]
  }
}

Subagents (10)

apex-developerBuilds and reviews Apex classes, triggers, batch jobs, queueable jobs, scheduled jobs, invocable actions, and Apex tests. Follows Salesforce DX best practices and bulkification patterns.
lwc-developerBuilds and reviews Lightning Web Components — HTML, JavaScript, CSS, Apex integration, wire adapters, events, and Jest tests. Follows LWC best practices and accessibility standards.
qa-testerCreates test strategy, Apex test classes, LWC Jest tests, validation checklists, and regression checklists. Ensures code coverage, edge cases, and security scenarios are covered.
salesforce-architectReviews Salesforce project architecture, metadata structure, data model design, integration patterns, and deployment risk. Use for non-trivial architecture decisions, large feature design, or pre-rele
security-reviewerReviews Salesforce code and configuration for security issues — SOQL injection, CRUD/FLS, sharing violations, exposed secrets, guest user risk, and production change safety.
apex-developerBuilds and reviews Apex classes, triggers, batch jobs, queueable jobs, scheduled jobs, invocable actions, and Apex tests. Follows Salesforce DX best practices and bulkification patterns.
lwc-developerBuilds and reviews Lightning Web Components — HTML, JavaScript, CSS, Apex integration, wire adapters, events, and Jest tests. Follows LWC best practices and accessibility standards.
qa-testerCreates test strategy, Apex test classes, LWC Jest tests, validation checklists, and regression checklists. Ensures code coverage, edge cases, and security scenarios are covered.
salesforce-architectReviews Salesforce project architecture, metadata structure, data model design, integration patterns, and deployment risk. Use for non-trivial architecture decisions, large feature design, or pre-rele
security-reviewerReviews Salesforce code and configuration for security issues — SOQL injection, CRUD/FLS, sharing violations, exposed secrets, guest user risk, and production change safety.

Slash commands (12)

/create-apex/create-lwc/prepare-pr/review-security/validate-deploy/write-tests/create-apex/create-lwc/prepare-pr/review-security/validate-deploy/write-tests

Similar rigs

copied ✓