~ / rigs / grzmol / vibe-force

grzmol/vibe-force

Salesforce delivery harness for Claude Code: parallel Apex, LWC and metadata agents, documentation-grounded Salesforce and fflib skills, deterministic hooks, local and post-deploy check gates.

↗ GitHub ★ 2 no license updated 27d ago project Claude Code Claude plugin
share on X
ARCHETYPE
Orchestrator
A bench of specialised subagents. The main agent mostly delegates.
CONTEXT TAX · EVERY TURN
~15.5k tokens
Context hog · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details

Copy this rig

# review before running: this installs third-party code
$ claude mcp add salesforce-dx -- npx -y @salesforce/mcp --orgs ${VF_MCP_ORGS:-DEFAULT_TARGET_ORG} --toolsets ${VF_MCP_TOOLSETS:-core,data,code-analysis,testing} --no-telemetry
$ claude mcp add playwright -- npx -y @playwright/mcp@latest --headless --isolated --browser ${VF_BROWSER:-chrome} --output-dir .vibeforce/state/browser --timeout-navigation 90000 --viewport-size 1440x900
$ npx degit grzmol/vibe-force/agents ./rig-vibe-force/agents
$ npx degit grzmol/vibe-force/commands ./rig-vibe-force/commands
$ npx degit grzmol/vibe-force/skills ./rig-vibe-force/skills
$ npx degit grzmol/vibe-force/hooks ./rig-vibe-force/hooks

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.

$ claude mcp add salesforce-dx -- npx -y @salesforce/mcp --orgs ${VF_MCP_ORGS:-DEFAULT_TARGET_ORG} --toolsets ${VF_MCP_TOOLSETS:-core,data,code-analysis,testing} --no-telemetry
$ claude mcp add playwright -- npx -y @playwright/mcp@latest --headless --isolated --browser ${VF_BROWSER:-chrome} --output-dir .vibeforce/state/browser --timeout-navigation 90000 --viewport-size 1440x900
$ npx degit grzmol/vibe-force/skills/sf-agentforce-development .claude/skills/sf-agentforce-development
$ npx degit grzmol/vibe-force/skills/sf-apex-development .claude/skills/sf-apex-development
$ npx degit grzmol/vibe-force/skills/sf-apex-testing .claude/skills/sf-apex-testing
$ npx degit grzmol/vibe-force/skills/sf-async-apex-patterns .claude/skills/sf-async-apex-patterns
$ npx degit grzmol/vibe-force/skills/sf-cli-operations .claude/skills/sf-cli-operations
$ npx degit grzmol/vibe-force/skills/sf-code-analyzer-quality .claude/skills/sf-code-analyzer-quality
$ npx degit grzmol/vibe-force/skills/sf-data-cloud .claude/skills/sf-data-cloud
$ npx degit grzmol/vibe-force/skills/sf-data-management .claude/skills/sf-data-management
$ npx degit grzmol/vibe-force/skills/sf-debugging-logs .claude/skills/sf-debugging-logs
$ npx degit grzmol/vibe-force/skills/sf-deployment-strategies .claude/skills/sf-deployment-strategies
$ npx degit grzmol/vibe-force/skills/sf-fflib-domain-service-uow .claude/skills/sf-fflib-domain-service-uow
$ npx degit grzmol/vibe-force/skills/sf-fflib-foundations .claude/skills/sf-fflib-foundations
$ npx degit grzmol/vibe-force/skills/sf-fflib-operations .claude/skills/sf-fflib-operations
$ npx degit grzmol/vibe-force/skills/sf-fflib-selector-layer .claude/skills/sf-fflib-selector-layer
$ npx degit grzmol/vibe-force/skills/sf-fflib-testing .claude/skills/sf-fflib-testing
$ npx degit grzmol/vibe-force/skills/sf-flow-automation .claude/skills/sf-flow-automation
$ npx degit grzmol/vibe-force/skills/sf-governor-limits .claude/skills/sf-governor-limits
$ npx degit grzmol/vibe-force/skills/sf-integration-patterns .claude/skills/sf-integration-patterns
$ npx degit grzmol/vibe-force/skills/sf-local-development .claude/skills/sf-local-development
$ npx degit grzmol/vibe-force/skills/sf-lwc-development .claude/skills/sf-lwc-development
$ npx degit grzmol/vibe-force/skills/sf-lwc-jest-testing .claude/skills/sf-lwc-jest-testing
$ npx degit grzmol/vibe-force/skills/sf-minimal-change .claude/skills/sf-minimal-change
$ npx degit grzmol/vibe-force/skills/sf-org-security-audit .claude/skills/sf-org-security-audit
$ npx degit grzmol/vibe-force/skills/sf-packaging-release .claude/skills/sf-packaging-release
$ npx degit grzmol/vibe-force/skills/sf-post-deploy-verification .claude/skills/sf-post-deploy-verification
$ npx degit grzmol/vibe-force/skills/sf-process-builder-migration .claude/skills/sf-process-builder-migration
$ npx degit grzmol/vibe-force/skills/sf-project-structure .claude/skills/sf-project-structure
$ npx degit grzmol/vibe-force/skills/sf-scratch-orgs-sandboxes .claude/skills/sf-scratch-orgs-sandboxes
$ npx degit grzmol/vibe-force/skills/sf-security-model .claude/skills/sf-security-model
$ npx degit grzmol/vibe-force/skills/sf-setup-automation .claude/skills/sf-setup-automation
$ npx degit grzmol/vibe-force/skills/sf-soql-sosl-optimization .claude/skills/sf-soql-sosl-optimization
$ npx degit grzmol/vibe-force/skills/sf-technical-debt-audit .claude/skills/sf-technical-debt-audit
$ npx degit grzmol/vibe-force/skills/sf-ui-test-automation .claude/skills/sf-ui-test-automation
$ npx degit grzmol/vibe-force/skills/sf-workflow-orchestration .claude/skills/sf-workflow-orchestration
$ curl -fsSL --create-dirs -o .claude/agents/sf-apex-engineer.md https://raw.githubusercontent.com/grzmol/vibe-force/main/agents/sf-apex-engineer.md
$ curl -fsSL --create-dirs -o .claude/agents/sf-deploy-engineer.md https://raw.githubusercontent.com/grzmol/vibe-force/main/agents/sf-deploy-engineer.md
$ curl -fsSL --create-dirs -o .claude/agents/sf-integration-engineer.md https://raw.githubusercontent.com/grzmol/vibe-force/main/agents/sf-integration-engineer.md
$ curl -fsSL --create-dirs -o .claude/agents/sf-lwc-engineer.md https://raw.githubusercontent.com/grzmol/vibe-force/main/agents/sf-lwc-engineer.md
$ curl -fsSL --create-dirs -o .claude/agents/sf-metadata-engineer.md https://raw.githubusercontent.com/grzmol/vibe-force/main/agents/sf-metadata-engineer.md
$ curl -fsSL --create-dirs -o .claude/agents/sf-orchestrator.md https://raw.githubusercontent.com/grzmol/vibe-force/main/agents/sf-orchestrator.md
$ curl -fsSL --create-dirs -o .claude/agents/sf-org-verifier.md https://raw.githubusercontent.com/grzmol/vibe-force/main/agents/sf-org-verifier.md
$ curl -fsSL --create-dirs -o .claude/agents/sf-quality-gate.md https://raw.githubusercontent.com/grzmol/vibe-force/main/agents/sf-quality-gate.md
$ curl -fsSL --create-dirs -o .claude/agents/sf-scout.md https://raw.githubusercontent.com/grzmol/vibe-force/main/agents/sf-scout.md
$ curl -fsSL --create-dirs -o .claude/agents/sf-security-reviewer.md https://raw.githubusercontent.com/grzmol/vibe-force/main/agents/sf-security-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/sf-technical-architect.md https://raw.githubusercontent.com/grzmol/vibe-force/main/agents/sf-technical-architect.md
$ curl -fsSL --create-dirs -o .claude/agents/sf-test-engineer.md https://raw.githubusercontent.com/grzmol/vibe-force/main/agents/sf-test-engineer.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 *)"
    ]
  }
}

MCP servers (2)

serversourceest. tokens
@salesforce/mcp · "salesforce-dx" npm 2.5k
Playwright MCP · "playwright" npm 7.5k

Skills (34)

Subagents (12)

sf-apex-engineer
model: sonnet
Implements Apex classes, triggers, trigger handlers, and their unit tests. Use for wave-1 work under classes/ and triggers/ when a story needs server-side logic, bulkification, user-mode data access,
sf-deploy-engineer
model: sonnet
Runs wave-3 Salesforce deployments - validate first, then quick-deploy the recorded job id. Use for manifest and destructive-change handling, test-level selection, and rollback planning. Refuses produ
sf-integration-engineer
model: sonnet
Implements outbound and inbound Salesforce integration metadata and integration Apex - Named and External Credentials, External Services, platform event channels, callout services, and event publisher
sf-lwc-engineer
model: sonnet
Implements Lightning Web Components, Aura bundles, static resources, and their Jest specs. Use for wave-1 UI work under lwc/ when a story needs a new component, wire adapters, Apex-backed UI, or a cli
sf-metadata-engineer
model: sonnet
Implements declarative Salesforce metadata - custom objects and fields, permission sets, Flows, layouts, FlexiPages, labels, and settings. Use for wave-1 work that changes the data model, access grant
sf-orchestrator
model: opus
Plans and sequences multi-agent Salesforce delivery for a story or change request. Use when work spans Apex, LWC, metadata, or integrations and needs wave scheduling, a cross-slice contract, gate aggr
sf-org-verifier
model: sonnet
Verifies a Salesforce change in the live org after deployment - smoke probes, data and limit queries, log capture, and diagnostics collection. Use in wave 4 to confirm the story actually works in the
sf-quality-gate
model: sonnet
Runs the local Salesforce quality gate - formatting, ESLint, Code Analyzer, and Jest - then triages every finding to an owner with a concrete fix. Use in wave 2 before any deployment. Read-only by def
sf-scout
model: haiku
Read-only wave-0 reconnaissance for a Salesforce change. Use before any edit to map impacted metadata, the dependency graph between Apex, LWC, objects and Flows, existing test coverage, and the risk l
sf-security-reviewer
model: sonnet
Read-only Salesforce security review of CRUD and FLS enforcement, sharing, SOQL injection, secret handling, and over-broad permission grants. Use in wave 2 before deployment, or whenever Apex, LWC, or
sf-technical-architect
model: opus
Read-only wave-0 architecture decisions for a Salesforce change - data model and sharing design, declarative versus Apex, integration and identity topology, environment and release strategy, volumetri
sf-test-engineer
model: sonnet
Owns Salesforce test coverage - Apex test classes and LWC Jest specs. Use in wave 2 to close coverage gaps and run the local test gate, and in wave 4 to run Apex tests against the deployed org.

Slash commands (11)

/vf-check/vf-deploy/vf-init/vf-migrate-process/vf-migrate-workflow/vf-org/vf-review/vf-setup/vf-story/vf-verify/vf-xml

Similar rigs

copied ✓