agentleFS
jiten-singh-shahijiten-singh-shahi/salesforce-claude-code/.cursor/skills/configure-scc/SKILL.md

configure-scc

Skill15 starsChanged 7 months agoMITView on GitHub

Use when setting up SCC for Salesforce Apex and LWC development. Interactive wizard to install profiles, modules, and customize the harness for your org.

  • Reads credentials
  • Installs packages

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When installing SCC for the first time on a Salesforce project

    line 13
  2. Distinctive:

    When adding new modules or profiles to an existing SCC installation

    line 14
  3. Distinctive:

    When customizing hook behavior or profiles for your team's workflow

    line 15
  4. Distinctive:

    When troubleshooting SCC configuration or missing components

    line 16
  5. Distinctive:

    When setting up SCC for different team members or CI/CD environments

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Configure SCC

Interactive guide for installing and configuring Salesforce Claude Code.

When to Use

  • When installing SCC for the first time on a Salesforce project
  • When adding new modules or profiles to an existing SCC installation
  • When customizing hook behavior or profiles for your team's workflow
  • When troubleshooting SCC configuration or missing components
  • When setting up SCC for different team members or CI/CD environments

Installation

Quick Install

# 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 Details

ProfileIncludes
apexCommon rules + Apex rules, agents, skills
lwcCommon rules + LWC rules, agents, skills
fullAll agents, skills, rules

Diagnostics

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

Hook Configuration

Profiles

# 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

Disable Specific Hooks

export SCC_DISABLED_HOOKS=governor-check,cost-tracker

Package Manager

SCC auto-detects your package manager. Override with:

export CLAUDE_PACKAGE_MANAGER=npm  # or pnpm, yarn, bun

Environment-Specific Configuration

Sandbox / Scratch Org Development

# 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

CI/CD Environments

# 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

Team Setup

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

Troubleshooting

Common Issues

ProblemCauseFix
npx scc-universal install failsNode.js < 20Upgrade: nvm install 20
Hooks not firingSCC not installed in projectRun npx scc-universal doctor to check
Permission denied on hooksScript not executableRun npx scc-universal repair
Skills not loadingWrong install profileRun npx scc-universal install all
sf command not foundSF CLI not installedInstall: npm install -g @salesforce/cli
sf commands fail with errorsSF CLI version too oldUpgrade: npm update -g @salesforce/cli (SCC requires SF CLI v2.x / sf not sfdx)
Hooks slow down sessionToo many hooks enabledSwitch to SCC_HOOK_PROFILE=minimal

Diagnostic Commands

# 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

Upgrading SCC

# 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

Verification

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.