skills/configure-scc/SKILL.md
Use when setting up SCC for Salesforce Apex and LWC development. Interactive wizard to install profiles, modules, and customize the harness for your org.
npx skillsauth add jiten-singh-shahi/salesforce-claude-code configure-sccInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Interactive guide for installing and configuring Salesforce Claude Code.
# Install globally
npm install -g scc-universal
# Install with a profile
npx scc-universal install all # Everything (all agents, skills, rules)
npx scc-universal install apex # Apex-focused development
npx scc-universal install lwc # LWC-focused development
| Profile | Includes |
|---------|----------|
| apex | Common rules + Apex rules, agents, skills |
| lwc | Common rules + LWC rules, agents, skills |
| full | All agents, skills, rules |
npx scc-universal doctor # Check for missing/drifted files
npx scc-universal status # View installed components
npx scc-universal repair # Restore drifted files
npx scc-universal uninstall # Remove SCC-managed files
# Set hook profile (controls which hooks run)
export SCC_HOOK_PROFILE=minimal # Session start + stop only
export SCC_HOOK_PROFILE=standard # Default — includes quality checks
export SCC_HOOK_PROFILE=strict # All hooks including auto-format
export SCC_DISABLED_HOOKS=governor-check,cost-tracker
SCC auto-detects your package manager. Override with:
export CLAUDE_PACKAGE_MANAGER=npm # or pnpm, yarn, bun
# Set default target org for SF CLI commands
sf config set target-org=my-scratch-org
# Scratch org duration is set via --duration-days flag or scratch org definition file
# sf org create scratch -f config/project-scratch-def.json --duration-days 7
# Minimal hooks for CI (fast, no interactive prompts)
export SCC_HOOK_PROFILE=minimal
# Disable all cost/session tracking in CI
export SCC_DISABLED_HOOKS=cost-tracker,session-start,session-end,evaluate-session
Share SCC configuration across your team by adding to your project's .env.example:
# .env.example — copy to .env and customize
SCC_HOOK_PROFILE=standard
CLAUDE_PACKAGE_MANAGER=npm
| Problem | Cause | Fix |
|---------|-------|-----|
| npx scc-universal install fails | Node.js < 20 | Upgrade: nvm install 20 |
| Hooks not firing | SCC not installed in project | Run npx scc-universal doctor to check |
| Permission denied on hooks | Script not executable | Run npx scc-universal repair |
| Skills not loading | Wrong install profile | Run npx scc-universal install all |
| sf command not found | SF CLI not installed | Install: npm install -g @salesforce/cli |
| sf commands fail with errors | SF CLI version too old | Upgrade: npm update -g @salesforce/cli (SCC requires SF CLI v2.x / sf not sfdx) |
| Hooks slow down session | Too many hooks enabled | Switch to SCC_HOOK_PROFILE=minimal |
# Full diagnostic report
npx scc-universal doctor
# See exactly what's installed
npx scc-universal list-installed
# Preview what WOULD be installed (dry run)
npx scc-universal plan apex
# Check state store
npx scc-universal status
# Reset everything and reinstall
npx scc-universal uninstall && npx scc-universal install all
# Update to latest version
npm install -g scc-universal@latest
# Repair any drifted files after upgrade
npx scc-universal repair
# Verify upgrade
npx scc-universal doctor
npm test # Run all validators
npx scc-universal doctor # Check installation health
sf --version # Verify SF CLI is installed
npx scc-universal status # Confirm installed components
development
Update Salesforce platform reference docs with latest release features and deprecation announcements. Use when SessionStart hook warns docs are outdated or a new Salesforce release has shipped. Do NOT use for Apex or LWC development.
development
Use when syncing documentation after Salesforce Apex code changes. Update README, API docs, and deploy metadata references to match the current org codebase.
development
Use when managing context during long Salesforce Apex development sessions. Suggests manual compaction at logical intervals to preserve deploy and org context across phases.
tools
Visualforce development — pages, controllers, extensions, ViewState, JS Remoting, LWC migration. Use when maintaining VF pages, building PDFs, or planning VF-to-LWC migration. Do NOT use for LWC, Aura, or Flow.